Why Programs Stall

Why programs stall

Not for the reason anyone budgets for.

---

The pattern

A pilot works. Somebody demos it. It gets funded.

Then it does not scale, and the post-mortem blames the model.

The model was rarely the problem.

What actually happened, in order

1 · Nobody owned the outcome. An agent was deployed by whoever had budget. The KPI it was supposed to move belonged to someone who was informed rather than accountable. → Who owns what, on a Tuesday

2 · There was no inventory. Six months later nobody could say how many agents were running, what they could reach, or who to call. → What each agent can reach, and the tier that says so

3 · The first incident arrived before the process did. The escalation path was designed during the incident, which is the most expensive time to design anything. → The governance each level of autonomy requires, decided in advance

4 · The evidence did not exist. Asked whether it was working, the honest answer was an impression. Asked to prove it, there was a demo. → The three drifts, and the check that runs every morning

5 · The budget conversation came, and it lost. Not because the value was absent, but because nobody could put a number on it against a baseline. → Value realisation, and the conversation with the CFO

The uncomfortable part

Every one of those is an operating model failure, and every one of them is predictable months in advance.

They are also the five things nobody is assigned to prevent, because they sit between the team that builds and the function that governs.

That gap is what a Center of Excellence is for.

Not a review board. Not a standards committee.

The function that owns the questions nobody else is paid to ask.

_{Back to Home · The framework spine}