Measuring transformation when the benefits are indirect
The things worth doing are often the hardest to attribute. That is not a reason to measure the wrong things instead.
Transformation programmes face an awkward measurement problem. The benefits are real, diffuse and slow, while the costs are precise, concentrated and immediate. Under pressure to demonstrate value, programmes reach for whatever can be counted — systems migrated, processes digitised, users onboarded — and those numbers steadily displace the outcomes they were meant to represent.
The consequence is a programme that reports well and delivers ambiguously, until the year the reporting stops being believed.
The attribution trap
The standard demand is a direct causal line from investment to financial outcome. For most transformation work no such line exists, because the effect is enabling rather than causal: the platform did not increase revenue, it removed a constraint that had prevented three teams from doing things that eventually did.
Insisting on direct attribution in this environment produces one of two failures. Programmes either claim credit they cannot defend, which erodes trust permanently, or they retreat to activity metrics, which measure motion rather than progress.
Measuring what can honestly be measured
- Cycle time for work that matters — how long from a decision to it being live for customers. It is measurable, it responds to transformation, and the business understands it.
- Removed constraints, stated concretely. “We can now release weekly instead of quarterly” is a defensible claim; “we improved agility” is not.
- Cost of change: the effort required to make a typical modification, tracked over time. Rising numbers reveal problems that output metrics conceal.
- Leading indicators agreed in advance, with the causal argument written down before the results arrive, so that the interpretation cannot be retrofitted.
- Counterfactual honesty. Some benefits are genuinely unattributable, and saying so plainly buys more credibility than an inflated claim survives.
The conversation to have at the outset
The most useful moment in a transformation programme is the one at the start where sponsors agree what evidence would count. Not targets — evidence. What would we expect to see in eighteen months if this is working, and what would we expect to see if it is not?
Programmes that answer that question honestly at the beginning tend to survive their second year, because the answer arrives as expected rather than as an argument. Those that defer it end up negotiating their own success criteria retrospectively, which nobody in the room ever quite believes.
Let's build the system your business will run on next.
Tell us where it hurts. We'll bring the architects, engineers, and delivery model to fix it — and scale it.