Why Frameworks Fail

Most failed transformations leave behind a familiar archaeological layer.

New role names. New ceremonies. New terminology. Possibly a shiny maturity model. Often a slide deck explaining the chosen framework with grave sincerity.

What they do not leave behind is better delivery.

Cycle times do not materially improve. WIP is still too high. Decisions still climb a hierarchy before anything important can happen. Teams still own output while someone else owns the real trade-offs.

So the post-mortem begins: perhaps the framework was wrong.

Usually, that is not the problem.

Frameworks fail because structures survive them

Most frameworks are not installed into a neutral system. They are installed into an existing power structure.

Capital still flows the old way. Decision rights still sit where they sat before. Incentives still reward predictability theater, local optimisation, and executive comfort. Accountability still breaks in the same places. The organisation keeps its old operating model and layers new language on top of it.

Then it acts surprised when nothing measurable changes.

The ceremony trap

This is the easiest version to spot.

Teams adopt the visible parts first: standups, retrospectives, sprint reviews, planning rituals, board shapes, role names. Those changes are easy to announce and easy to audit.

What does not change is how strategy turns into work, who can say no, how budgets are assigned, how teams are formed, and who gets to decide whether a trade-off is acceptable.

In other words, process changes while control stays put.

That arrangement can keep a transformation alive on paper for years. It just cannot produce the outcomes people were promised.

The framework fog

This is the more sophisticated version.

The organisation has coaches. It has a transformation office. It has chosen SAFe, LeSS, Spotify, or a custom hybrid with enough branded nouns to feel proprietary. Everybody can explain the model. Very few people can point to the measurable outcome that changed because of it.

That is framework fog. The organisation is now discussing the map more than the terrain.

Frameworks are useful to the extent that they help people make better structural decisions. They are not useful when they become a way to postpone those decisions.

The reforms that actually matter

If you want different delivery outcomes, the hard variables are not mysterious.

How is capital allocated? Who decides what gets started? How many dependencies are teams forced to navigate before they can act? Are teams built around outcomes or around resource pools? Can the people closest to the work make meaningful trade-offs, or are they still serving a chain of approvals dressed up as agility?

Those questions are less marketable than a framework rollout. They are also where results come from.

The organisations that improve usually change some combination of portfolio governance, team topology, accountability design, and leadership operating rhythm. They reduce the distance between decision and action. They make trade-offs visible. They stop measuring transformation by activity and start measuring it by delivery behaviour.

That is reform. Everything else is mostly choreography.

Why leaders prefer frameworks anyway

Because frameworks feel safer than structural change.

A framework gives the leadership team something to buy, explain, and govern. Structural reform asks them to touch the places where their own authority, habits, and incentives live. One of those options is administratively convenient. The other is politically real.

So organisations often choose the one that lets them appear serious without redistributing much power.

Then they declare the framework disappointing.

The better use of a framework

A framework can still be useful. It just needs to be demoted from saviour to aid.

Use it as a language for discussing trade-offs. Use it as a prompt to inspect whether your system has the conditions the framework assumes. Use it to clarify what would have to change in portfolio governance, decision rights, and team design for the ideas to work.

Do not use it as a substitute for that work.

A framework can guide reform. It cannot do the reform for you.

If your organisation has tried several frameworks and the outcomes remain flat, the next diagnosis should not be "we chose the wrong one."

It should be "what did we refuse to change while installing them?"