Enterprise agile transformations do not stall because the organisation forgot to buy a framework logo. They stall on funding, organisational design, and culture — the boring machinery that decides whether teams can actually change how work is chosen and paid for.
Why they stall (it is not the missing scaled-agile badge)
The usual autopsy is wrong. Leadership bought training, stood up tribes or release trains, and hired coaches. Six months later, the annual budget still locks scope in January, architecture still sits in a committee that meets monthly, and middle managers are still rewarded for utilisation and local headcount. The logo was never the constraint.
Three stall points dominate. Funding: project-shaped money that punishes learning. Organisational design: silos that own fragments of a customer journey. Culture: fear of visible failure, so every increment is a performance. Miss those and you have agile theatre — stand-ups in a waterfall body.
Start with the outcome you want in the business, not with the operating model you admired at a conference. Faster cycle time to a paying customer? Fewer handoffs in a value stream? The ability to stop funding a bad bet in six weeks instead of sixteen months? Write that. Then ask which of funding, structure, or behaviour makes it impossible today.
How to start without boiling the ocean
Pick a thin slice of the organisation where the pain is real and the sponsor can actually move money and reporting lines. A 'transformation of everything by December' is a novel. A value stream with a named owner, a funding experiment, and permission to change the measures is a start.
Sequence the constraints. If funding still requires a 40-page business case for every slice of learning, coaching the stand-up will not save you. If the org chart still splits 'the people who talk to customers' from 'the people who build,' your squads will re-create the silo in Slack. Do not start with the easiest ritual. Start with the constraint that makes the rituals fake.
Be honest about what will not change yet. A regulated core may stay predictive while a digital channel iterates. That is a hybrid strategy, not a failure of nerve. Announcing 'we are now Agile' while the core stays untouched is how you create two cultures and one shared budget argument.
A coalition, not a hero coach
Transformations led only by a PMO or only by a coaching vendor die when the vendor leaves. You need a sponsor who can change incentives, a finance partner who can change how money is released, and operational leaders who will own the new measures. The agile coach is necessary and not sufficient. Treat them as such.
Write a transformation strategy as decisions, not as a journey metaphor. What we will stop funding. What we will measure instead of utilisation. Which design authority we will retire. Which value streams we will stand up first. Which policies we will rewrite. A journey map with no decisions is a mural.
Expect the middle of the organisation to feel attacked. Their job was to hold the old system together. If you do not give them a role in the new one — product ownership, value-stream leadership, coaching — they will wait you out. Waiting you out is a rational strategy. Plan for it.
Summary & next steps
Stall points are funding, organisational design, and culture — not a missing framework brand. Start with a business outcome, a thin slice, and the constraint that makes rituals fake. Build a coalition that can move money and incentives.
Next: operating models — structuring around value streams rather than around the silos that made the last transformation a re-org with stand-ups.