Transformation must ultimately connect to measurable business value
Every transformation programme should carry a number it is accountable to. Not a proxy, not an activity metric. A figure a finance partner will put their name against.
Transformation programmes fail in a characteristic way. They do not collapse; they drift. Twelve months in, the deck is full of progress, the team is busy, the milestones are broadly met, and no one can say what changed in the business. By month eighteen the programme is defended on the grounds that stopping would waste what has been spent.
The mechanism is almost always the same: the programme was funded against activity rather than outcome, and nobody noticed at the time because the activity was real.
Proxies are how it starts
Nobody sets out to fund activity. It happens because the honest number is hard to get and a proxy is available. Migrations completed. Platforms decommissioned. Adoption percentage. Story points. Each is measurable, each is defensible in a steering meeting, and none of them is the thing the business is buying.
A proxy is acceptable only when the chain from proxy to money is written down and someone in finance has agreed with it. If that chain cannot be written down in three lines, it does not exist.
What accountability looks like in practice
- One number per programme, named at funding, owned by a person rather than a committee.
- A finance partner who agrees the number is real and will report it in their own numbers.
- A baseline captured before anything changes. Retrofitting a baseline is how programmes launder their results.
- A stated date by which the number should move, and an agreement about what happens if it has not.
That last one is the test. A programme that has never agreed what failure looks like has not really been funded; it has been permitted.
What a programme is actually funded against
Activity
- Migrations completed, platforms decommissioned
- Adoption percentage, story points
- Measurable, defensible, and not what the business is buying
Outcome
- One number, named at funding, owned by a person
- A finance partner who will report it in their own numbers
- A baseline captured before anything changes
The objection, and the answer
The standard objection is that some work is foundational and its value cannot be attributed cleanly. This is sometimes true and mostly used as cover. Platform work, tooling, and data foundations genuinely do pay out through other programmes rather than directly.
The answer is not to exempt that work from accountability. It is to name the programmes it is enabling and attribute a share of their numbers to it. If no such programme exists yet, that is worth knowing early. It usually means the foundational work is ahead of any actual demand.
A transformation that cannot be traced to the P&L is not necessarily worthless. But it is unfunded, and it will be cancelled by someone who never understood it.
None of this is about being hard-nosed. Programmes with a real number attached are easier to defend, easier to staff, and considerably easier to finish, because everyone involved can tell when they are done.
Enterprise Technology Executive
Anurag Kumar Mishra
I lead large-scale transformation across telecom and enterprise technology, connecting technology strategy, operating models and capital allocation to measurable business outcomes.
LinkedIn