Developments in Practice VII: Developing and Delivering the IT Value Proposition
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
In spite of many years of effort, we are still not able to articulate and deliver IT value accurately. Unfortunately, "silver bullet thinking" still predominates (i.e., plug in technology and deliver bottom line impact) in organizations today. IT value is a multi-layered concept, far more complex than it first appears. To examine this complex concept and how it is understood in IT organizations, the authors convened a focus group of practicing IT managers from a number of different industries. This paper, using the inputs from the focus group, explores how organizations are attempting to determine and develop effective IT value propositions. It describes the three components of this proposition: identification of potential value, effective conversion, and realizing value. The paper then derives a number of principles of delivering IT value. We conclude that there is no single agreed-on notion of business value. Therefore, it is important to make sure that both business and IT managers work to a common value goal whether traditional cost reduction, process efficiencies, new business capabilities, improved communication, or any other objectives. We also suggest that technology is being used as a catalyst to drive many different types of organizational transformation and strategy. Therefore, IT value can no longer be viewed in isolation from the other parts of business, namely people and information.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.003 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it