Why Execution Breaks Down Before Projects Even Start

Some execution problems begin before delivery starts. When too many projects are approved, too many are started together, and capacity is treated as an assumption rather than a constraint, even capable teams can struggle to deliver.

If you’re dealing with constant firefighting, bottlenecks, pressure to start more work and too little available capacity, the problem may be bigger than individual project performance.

Leadership may have committed to more work than the organisation can realistically support.

That is where capacity planning and sequencing matter: they help turn approved work into a deliverable portfolio rather than leaving teams to resolve conflicting commitments during execution.

Why Plans Fail Before They Even Begin

Some plans are set up to fail before delivery begins, when too many projects are approved and there’s no structured way to turn those approvals into a realistic, achievable delivery plan.

Under pressure to say yes, leadership commits to more work than the organisation can reasonably absorb. Strategy and ambition may be perfectly credible, but if they are not reconciled with the organisation’s actual capacity, optimism fills the gaps and the portfolio still looks fine on paper.

What follows is predictable:

• Teams are spread across too many initiatives and forced into constant task-switching.
• Critical resource bottlenecks emerge almost immediately.
• Progress slows, deadlines slip, budgets spiral, and confidence erodes.

This isn’t an execution failure. It’s a planning failure that was locked in before delivery even started.

Fix It Upstream: Capacity Planning and Sequencing

If you want execution to improve, you have to fix planning upstream. That means getting two decisions right: what the organisation can realistically support and when that work should start.

1. Capacity Planning: Stop Planning for 100% Utilisation

Capacity planning is about ensuring your portfolio is deliverable with the resources you actually have, not the resources you hope will appear. And capacity is broader than headcount and budget: scarce skills, operational dependencies, governance or infrastructure can become the constraint that determines what the organisation can really support.

One of the most common mistakes is planning for 100% utilisation. On paper it looks efficient. In practice, it is a recipe for congestion.

At full utilisation, every surprise has to go somewhere. Priorities get switched, handoffs queue up, and urgent work pushes something else aside.

The pattern is familiar. A motorway at full capacity does not move faster. It turns into a traffic jam. Push utilisation too far and flow collapses.

As a practical rule of thumb, planning for around 80–85% utilisation leaves room for unexpected work. PMI describes a similar 80% resource-availability assumption; the right target depends on the team and how capacity has been calculated. More fundamentally, spare capacity around a bottleneck is not necessarily waste: keeping every resource busy can work against the flow of the portfolio.

The implication is uncomfortable but unavoidable. You cannot do everything at once. You have to choose which projects matter most and shape the portfolio so it fits within real capacity constraints.

That means testing different combinations of projects against the resources that actually constrain delivery. A portfolio can look feasible in aggregate while five worthwhile initiatives are all fighting for the same scarce team or downstream bottleneck. Spare capacity elsewhere does not help if the work cannot actually use it. The question is not simply “Which projects matter most?” It is “Which combination can we actually support?”

2. Sequencing: Don’t Start Everything at Once

Even when the right projects are selected, execution still breaks down if they all start at the same time.

A familiar scenario plays out. A new financial year begins, executives want momentum, and every approved initiative is launched together. The result is not progress. It is gridlock.

Shared resource pools are immediately overwhelmed. Teams juggle multiple priorities, progress slows, and the organisation wonders why nothing ever finishes.

The fix is not more pressure. It is better sequencing. Stagger start dates, smooth demand, and let constrained teams finish work before piling more onto them.

Starting fewer things together does not mean doing less. It means giving work a better chance to move.

Some delivery problems are therefore created before delivery even begins. When capacity and start-date decisions ignore how shared teams actually work, project managers inherit conflicts they cannot resolve through better scheduling alone.

Capacity Planning Is Not Detailed Project Planning

Capacity planning is not about defining individual tasks or mapping out every step of a project in advance. It is about understanding resource demand at the team level early enough to make sensible portfolio decisions. And that demand is not limited to the projects visible in the portfolio: smaller and informal work still consumes the same finite capacity.

Estimates do not need to be perfect. You need enough detail to see whether the portfolio has a fighting chance of fitting before you commit to it. More detail is not automatically better either: Mike Hannan describes one organisation that planned around senior architects it believed were the bottleneck, only to discover that the real constraint sat somewhere else.

At the portfolio level, the question is simpler and more important: which projects should be delivered, and in what order, to maximise value without overloading teams?

In practice, this means:

• Using rough, team-level estimates to create a high-level portfolio view.
• Moving into detailed project planning only once a project is approved and sequenced.
• Feeding changes from delivery back into the portfolio view to keep capacity assumptions realistic.

This feedback loop is where most organisations struggle. Portfolio plans quickly become outdated, and replanning feels too slow or painful to repeat regularly. As a result, decisions are often made using stale information.

Making capacity planning work is also an organisational challenge, not just an estimating exercise. An apparent resource shortage can actually begin upstream in portfolio load, priorities or planning, before anyone gets to detailed resource assignment.

Keep the Portfolio Current

Capacity planning and sequencing are not one-off exercises. The portfolio changes, so the answer has to be revisited.

• Better sequencing helps constrained teams finish work and release capacity.
• Updated capacity views make it safer to commit to new work.
• When priorities, estimates or available capacity change, the portfolio can be tested again.

When this loop is in place, leadership gains something that is usually missing: real control over portfolio performance, without relying on optimism or constant firefighting.

The Takeaway: Resource Chaos Is Optional

Teams that keep rescuing overloaded portfolios can become very good at firefighting. But firefighting is not a capability. It is a symptom.

Commit too much, start it all together, and ignore real capacity, and the result is predictable: firefighting. The teams did not create the conflict. The portfolio did.

• Capacity planning prevents overcommitment before it happens.
• Sequencing controls when approved work actually starts.
• Regular portfolio updates keep decisions grounded in reality as plans evolve.

Together, these disciplines replace reactive firefighting with deliberate control, allowing teams to focus on delivery rather than damage limitation.

Leadership gains visibility into trade-offs, control over constrained resources, and confidence that delivery plans are achievable.

That is the difference between a portfolio that constantly feels out of control and one that can adapt without breaking.

The Next Step: Review What the Organisation Can Commit To

If approved work already exceeds the capacity available, pushing delivery teams harder will not settle which commitments should take precedence.

Leadership may need to reconsider what starts now, what is phased, what waits or gives way, and what changes in work already underway. The question is not only whether each project matters, but which combination the organisation can realistically support.

In a 30-minute Decision Review, we can work through the choice you are facing, the funding and capacity constraints around it, and what would need to change for a different answer to make sense.

The conversation is confidential, has no fee and requires no preparation. You do not need confirmed sponsorship or sensitive portfolio data to start. It is not a software demo, and the Review stands on its own whether or not a further engagement follows.

Start with a Decision Review →

💚 I hope you found this article useful. If you’d like to hear from us when we publish new articles, see the ways to stay in touch just below ↓