In short
- Boards ask the same 7 questions of every major technology investment.
- Milestones aren’t outcomes – show movement against a baseline.
- Every material benefit needs a named business owner who has accepted it.
- Use the self-assessment to find the gaps before your board does.
Technology now accounts for a growing share of most organisations’ investment, and boards are less willing than they once were to take its value on trust. When spend rises and benefits remain hard to see, the questions get sharper.
They are also remarkably consistent. Whether the investment is an ERP replacement, a data platform, a cloud migration or an AI programme, boards tend to ask the same 7 things. This report sets out each question, why it gets asked, what a weak answer sounds like, and what a strong one needs – followed by a short self-assessment you can use on your own most significant investment.
Why boards are asking harder questions about technology value
3 shifts have changed the conversation.
Technology costs have moved after go-live. Subscription licensing, cloud consumption and usage-based AI pricing mean a growing share of cost arrives after delivery – and grows with use. A business case that focused on build cost tells only part of the story.
Investments are harder to separate. Most major benefits now depend on technology, process, data, workforce and supplier changes landing together. When value is lost, it’s usually in the gaps between them, which no single programme report shows.
Boards have been disappointed before. Many have approved investments that delivered on time and on budget and then failed to change performance. They have learnt to look past delivery status to the evidence of value.
“Approved investments fail to create value far more often than they fail to deliver.”
The 7 questions
1. What did we expect this to deliver – and who said so?
Why it’s asked. Business cases are written to win approval. Boards know that, and want to understand how much of the original promise was evidence and how much was ambition.
A weak answer points to the business case and repeats its headline figure.
A strong answer separates the benefits that were evidenced from those that were assumed, names who made each assumption, and says which of them still hold.
2. What has it delivered so far, against what baseline?
Why it’s asked. Milestones are not outcomes. A programme can be on time, on budget and still not improving anything.
A weak answer reports delivery progress: phases complete, systems live, users onboarded.
A strong answer shows movement in a business measure against a baseline taken before the change began. If no baseline exists, it says so – and proposes how to establish one now.
3. Who owns the benefit – by name?
Why it’s asked. Benefits that belong to “the business” belong to nobody.
A weak answer names the programme director or the CIO.
A strong answer names a business leader for each material benefit – someone with the authority to change the work that produces it – and shows they have accepted it.
4. What is it costing to run, not just to build?
Why it’s asked. Boards increasingly find that the cost of a technology investment arrives after go-live, in licences, support, cloud consumption and the internal team needed to look after it.
A weak answer gives the capital cost and the original run-cost estimate.
A strong answer shows current and forecast total cost of ownership, including consumption-based costs that grow with use, and how they compare with the original case.
5. What would happen if we stopped?
Why it’s asked. It’s the question that tests whether value is real. Sunk cost makes it uncomfortable; boards ask it anyway.
A weak answer explains why stopping is impossible.
A strong answer sets out the options honestly – continue, change, pause or stop – with the cost and consequence of each. Being willing to have this conversation is itself a sign of a well-governed investment.
6. What are we assuming that we haven’t tested?
Why it’s asked. Every investment rests on assumptions about adoption, data quality, supplier performance and the organisation’s capacity to change. The dangerous ones are those nobody has written down.
A weak answer refers to the risk register.
A strong answer lists the handful of assumptions the value depends on most, shows which have been tested and which haven’t, and explains how the untested ones will be checked.
7. What would make us change course – and who decides?
Why it’s asked. Boards want to know the organisation would notice if the investment stopped working, and that someone has the authority to act.
A weak answer describes the governance structure.
A strong answer names the measures that act as early warnings, the thresholds that would trigger a decision, and the person or forum that would take it.
A WEAK ANSWER
Describes activity, structure and delivery status.
A STRONG ANSWER
Shows evidence, owners, thresholds and options.
Self-assessment: score your investment
Take your most significant technology investment and try to answer each question with evidence rather than assertion. Score each one:
| Score | Meaning |
|---|---|
| 2 | We can answer with evidence today |
| 1 | We could answer, but the evidence is partial or out of date |
| 0 | We could not answer this with confidence |
12–14: well served. Your board is getting what it needs. Keep the evidence current and the owners engaged.
7–11: exposed. The investment may be sound, but confidence will erode under scrutiny. Fix the gaps before the board finds them – usually starting with baselines and benefit ownership.
0–6: value at risk. Value is probably leaking somewhere you can’t see. It’s worth finding out where, quickly, and being prepared to change course.
How to close the gaps
Most organisations that score below 12 have the same few gaps. In our experience, 4 actions close most of them.
1. Re-baseline what’s measurable now. Even mid-programme, you can establish a credible baseline for the measures that matter and track movement from here.
2. Put a business name against every material benefit. Ask each owner to accept it explicitly. Some will push back – which tells you something useful about the benefit.
3. Build a total cost of ownership view. Bring licence, consumption, support and internal costs into one forward-looking picture and compare it honestly with the original case.
4. Agree triggers and options in advance. Decide what evidence would prompt a change of course, and who would take the decision, before you need to.
Common questions
What questions should a board ask about technology investment?
The core 7: what was expected and who said so; what has been delivered against a baseline; who owns each benefit; what it costs to run; what would happen if it stopped; which assumptions are untested; and what would trigger a change of course.
How do you measure the value of a technology investment?
Track business measures – cost, cycle time, quality, revenue, risk – against a baseline taken before the change, alongside total cost of ownership. Delivery milestones show progress, not value.
Who should own the benefits of a technology programme?
A named business leader with authority over the work that produces each benefit, not the programme team or the CIO. Ownership should be explicitly accepted.
What is value leakage in technology investment?
The gap between the value an investment was expected to create and what it actually delivers – usually lost in the connections between technology, process, workforce, data and suppliers rather than in any one of them.
What this looks like in practice
For a regulated water utility, a short architecture assurance review of a major digital programme prioritised 3 enterprise risks that reshaped the next 12 months of investment sequencing. It grew into a longer relationship providing independent assurance as the programme matured. Read the case study →
