The illusion stack.

Programmes rarely fail loudly. They deliver. Milestones close, the system goes live, the steering pack turns green, and the organisation quietly carries on doing what it did before, at higher cost.

What produces that outcome is not incompetence. It is four separate habits, each defensible in isolation, that stack on top of one another until nobody can see the value gap underneath.

One — the programme factory

Output becomes the measure. Sprints completed, documents approved, modules configured, decisions logged. The programme reports velocity because velocity is measurable, and stops reporting whether any of it moved a number the business cares about.

The tell is simple. Ask what the programme delivered last quarter and you get a list. Ask what changed as a result and the room goes quiet.

Two — as-is replication, at scale

The business says it wants transformation. Then every workshop starts with how we do it today, every gap becomes a customisation, and every exception survives because someone in the room can name a case where it mattered.

What gets built is the current operating model, re-platformed. It is more expensive to run than what it replaced, because the old process now has a licence fee attached.

If the operating model does not change, the system is just a more expensive way to do the same work.

Three — benefits theatre

The business case carried a number. That number got the funding approved, and then stopped being anyone's job. The sponsor moved roles, the benefit was never written into a line manager's objectives, and the measurement baseline was never taken.

By the time anyone asks whether the benefit landed, the honest answer is that nobody can tell. That is not a measurement failure. It is an ownership failure, and it was decided at the business case, not at the end.

Four — success at go-live

Go-live is treated as the finish line. The programme demobilises, the vendor's best people roll off, the hypercare window closes on a date chosen by the plan rather than by adoption, and the organisation is left holding a system it has not yet learned to run.

Value shows up in the eighteen months after go-live. That is exactly the window in which most programmes have stopped looking.

How the stack holds

Each illusion protects the next. The programme factory produces enough visible output that nobody questions whether the operating model changed. As-is replication guarantees the benefits case cannot land. Benefits theatre means nobody is accountable when it doesn't. And treating go-live as success closes the programme before the evidence arrives.

Breaking it does not require a new methodology. It requires four things named before kickoff: what changes in how the business runs, who owns each benefit by name, what evidence will be accepted as proof, and what conditions would cause you to stop. If those four cannot be answered in a room, the stack is already assembling.