Organisations have a finite capacity for change. The problem is that most don’t manage it that way.
New priorities get added. Old ones hang around. Every function has a perfectly reasonable case for why its programme matters. Senior sponsors protect pet projects. Frontline teams are expected to absorb everything.
Before long, the organisation has more ‘priorities’ than it has people, money, attention or delivery capacity.
The result usually isn’t spectacular failure. It’s slower delivery, constant context-switching, tired teams, duplicated effort and lots of projects moving just enough to avoid being stopped.
Why stopping work is so difficult
Stopping something sounds simple until there’s a sponsor, a budget, a team and six months of effort attached to it.
People naturally become invested in the work they’ve started. Cancelling it can feel like admitting they were wrong, losing status, giving up budget or letting a team down.
There’s also a structural problem. The cost of doing too much is spread across the organisation. One project may look perfectly healthy in isolation while still consuming people and attention that would create more value somewhere else.
That’s why organisations can end up with dozens of individually sensible initiatives creating a collectively impossible workload.
And governance doesn’t always help. A lot of portfolio forums are very good at receiving updates, reviewing RAG statuses and approving new work. Far fewer have the confidence — or authority — to stop something that is still delivering broadly to plan.
But a project can be well run and still be the wrong thing to continue.
Good prioritisation means making trade-offs
If something genuinely new becomes a priority, something else has to give.
That doesn’t necessarily mean cancelling work every time. It could mean pausing it, reducing scope, sequencing it later or deliberately protecting another part of the organisation from yet another change.
The important thing is making the trade-off explicit. Otherwise ‘priority’ gradually becomes shorthand for: please do this as well.
That isn’t prioritisation. It’s accumulation.
If nothing moves, the new priority is an addition—not a priority.
What helps
A few practical disciplines make prioritisation more than an annual planning exercise.
- Make new work compete with existing work. Every new priority should trigger a simple question: what are we stopping, pausing or deferring to make room for this?
- Give portfolio governance real authority. A portfolio board that can approve work but cannot stop it is mostly an expensive reporting meeting.
- Make opportunity cost visible. Show which people, specialist skills and leadership attention each initiative consumes — and which other priorities are delayed as a result.
- Review the portfolio as a whole. A project can be healthy in isolation while the combination of initiatives remains strategically incoherent or impossible to deliver.
- Sequence change. Frontline teams experience new systems, processes, restructures, training and expectations landing on top of the day job — not a portfolio dashboard.
- Treat stopping as leadership, not failure. ‘We started this for good reasons, circumstances have changed, and something else now matters more’ is a mature decision.
- Prioritise outcomes, not functions. Leaders need to make trade-offs based on what matters most overall, not which department has the strongest sponsor.
Fewer things, done properly
Most organisations probably don’t need another transformation initiative. They need clearer choices about the ones they already have.
Good leadership isn’t just about deciding what starts. It’s also about stopping the wrong work.