IT value management connects technology spending to an outcome someone in the business owns. Start with a measurable problem, compare realistic alternatives and follow the result after implementation. A persuasive proposal makes its assumptions easy to inspect.
Define the problem and the baseline
Write the decision in one sentence: “Should we change the support workflow to reduce time spent handling repeat requests?” Identify the affected users, current volume, elapsed delays, error rates and staff effort. Measure a representative period and record how the figures were collected.
Compare at least the current approach and a credible improvement. Sometimes a process change, better training or improved data addresses the problem before a major system purchase. Include the work needed to keep the current approach running; a baseline has costs and risks too.
Separate the result from the proposed product. “Deploy a new portal” describes a delivery milestone. “Reduce repeated requests while maintaining resolution quality” describes a business outcome. Name the manager who can change the workflow and verify that outcome.
Compare full costs and distinct benefits
On a narrow screen, swipe the table or focus it and use the arrow keys.
| Category | Include | How to check it |
|---|---|---|
| Initial work | Configuration, integration, data cleanup, migration, training and staff time. | Obtain a scoped estimate and identify what it excludes. |
| Continuing cost | Licenses, support, administration, usage charges and ongoing training. | Use the same time horizon and user/usage assumptions for each option. |
| Transition and exit | Parallel operation, contract changes, export and decommissioning. | Ask who does each task and how it is priced. |
| Cash benefit | An identifiable reduction in spending or additional net contribution. | Name the budget or revenue measure and the owner who confirms it. |
| Capacity benefit | Time released for other useful work. | Measure hours and specify how the team will use them. |
| Risk and service outcome | Reliability, quality, compliance needs or customer experience. | Use relevant evidence and explicit tradeoffs; explain uncertainty. |
Count each benefit once. If staff use time released to handle more work, record that capacity change. If overtime spending also falls, count only the independently demonstrated reduction and explain how it relates to those hours. A salary rate multiplied by time does not by itself create spendable savings.
The UK Treasury's Green Book is an authoritative public-sector appraisal reference for comparing options, costs, benefits and risks. Its government rules and social-value perspective have their own scope; use a method and time horizon appropriate to your organization's decision.
Work through adoption and value
On a narrow screen, swipe the table or focus it and use the arrow keys.
| Adoption | Hours released / month | Annual capacity value | Value less first-year cost |
|---|---|---|---|
| 40% | 24 | $11,520 | −$1,680 |
| 60% | 36 | $17,280 | $4,080 |
| 80% | 48 | $23,040 | $9,840 |
The example assumes a full year of steady use, no ramp-up, unchanged request volume and quality, and no additional savings or revenue. A real proposal should vary these assumptions and include failed or partial adoption. For multi-year cash flows, account for timing and use the organization's approved discounting method instead of treating all years as equivalent.
Make a decision that can be revisited
List the assumptions that would change the decision: eligible workload, time saved, adoption, operating cost and implementation effort. Assign an evidence source and a confidence level to each. If uncertainty dominates the result, a small reversible pilot with a decision date can be more useful than a detailed forecast built on guesses.
Set go, revise and stop criteria before the pilot. For example, observe whether the new process helps the intended users, preserves answer quality and produces enough usable capacity to justify its continuing cost. Explain any important outcome that is difficult to monetize rather than assigning it an invented dollar figure.
Use the business-case worksheet and checked example to record the comparison. It includes the inputs, formulas, assumptions and blank benefit-owner fields so the analysis can be reviewed without this page open.
Track benefits after launch
Save the approved baseline and forecast. Give each benefit an owner, data source, review date and definition of success. Compare observed results with both the expected improvement and changes in workload or staffing that could explain the difference.
If adoption is low, inspect where users abandon the workflow and whether the new process adds steps. If the measured time saving is small, review a sample of real cases. If quality deteriorates, include rework and escalation effort before claiming a gain.
Record the resulting decision: adjust the process, change the tool, continue the pilot, expand it or stop. This closes the loop between buying technology and learning what it contributes.