The absorption ceiling nobody scores
Every transformation business case assumes the organisation can absorb what is being handed to it. Almost none of them test that assumption, because testing it requires looking outside the programme, and a programme is by definition scoped to itself.
The draw is cumulative. The reporting is not.
A finance transformation, an ERP replacement and an AI pilot can each be green. Each is measuring its own delivery against its own plan. None of them is measuring the same forty managers being asked to carry all three, because no single programme owns that population.
This is why absorption failures surface late. Nothing in the reporting structure is designed to see them, so the first visible signal is usually a delivery date slipping for reasons nobody can name.
What a reading actually looks like
On the composite case we use throughout, absorption reads 2.4 against a gate threshold of 3.75, while governance reads 3.9 and strategic coherence 3.3. The programme is not weak everywhere. It is weak in one specific place, and that place is the one determining whether anything else lands.
The action path opens with HR-6 rather than anything strategic, which surprises people. It is the correct sequence. A stronger value hypothesis delivered into an organisation with no remaining capacity gets you to the problem faster, not past it.
Priority comes from the gap
A low score on something the current stage does not yet require is not urgent. A middling score on something the next gate depends on usually is. This is why the platform sequences on the gap against a required level rather than on the score itself, and why the worst-looking number is not always the first thing to fix.
A programme that has produced every planned deliverable and cannot evidence its threshold conditions does not advance.
The uncomfortable version of this argument is that absorption capacity is usually the binding constraint and is almost never on the risk register, because the risk register was written by people scoped to one programme.
Shadow workflows are quietly holding your adoption numbers up
Go-live does not eliminate the parallel process. It drives it underground, where it keeps the numbers looking healthy while the transformation quietly fails to land.
Nobody can prove it worked, and that was decided at the start
The inability to demonstrate return is not a reporting failure discovered at the end. It is a design decision taken in the first ninety days, when the value case was written in a form that could never be tested.
Your governance was accurate once, on the day it was written
Governance does not fail loudly. It is correct at publication and degrades from that moment, while the document keeps looking authoritative because documents always do.
Start with the free diagnostic
Ten questions, an indicative readiness band, and one prescribed next step. Returned on screen, no call required.
See what it measures