For years, when a project stalled, the first question was always about money. Did we have enough budget. Did the business case hold up. Did finance sign off.
That is not the question anymore.
Ask any PMO leader, program director, or engagement manager what actually derails their work in 2026 and you will hear a different answer. It is not the budget line. It is capacity. Do we have the people, the time, and the bandwidth to actually do the work we already approved.
Portfolio management researcher Albert Ponsteen put it plainly: the real bottleneck has shifted. It used to be the budget. Now it is limited resource capacity. That single shift changes how leaders should be thinking about risk, planning, and their own role.
Why This Matters More Than It Sounds
Budget problems are visible. They show up in a spreadsheet, get escalated, and get solved with a decision. Capacity problems are quieter. They show up as slipped timelines, burned-out teams, and projects that technically stay "on track" while everyone involved is stretched past what is sustainable.
That quiet quality is what makes capacity dangerous. Nobody declares a capacity crisis in a steering committee meeting. It just erodes delivery, one overcommitted week at a time, until the team hits a wall or people start leaving.
If you are leading a PMO, a customer success org, or an engagement management team, you have felt this. You have watched a resourcing plan look perfectly fine on paper and completely fall apart in execution, because the plan counted hours and not people. If we're honest, even if it did count people, it wouldn't count them accurately. Likely it included working through lunches, multitasking during important meetings, long hours and weekends, and, even worse, whoever put that resource plan together probably thought that was all worth the payout.
The Change Management Piece Nobody Budgets For
Here is where it gets more interesting. Organizations with strong change management practices hit their project objectives 88 percent of the time. Without it, the failure rate jumps to 60 percent.
That is not a small gap. That is the difference between a program that delivers and one that quietly becomes shelfware.
And yet change management is still treated as optional. It is the first thing cut when a timeline gets squeezed, because it does not feel like "real work" the way a technical deliverable does. But change management is capacity too. It takes people, time, and attention, just like every other line item in a project plan. When leaders leave it out of the resourcing conversation, they are not saving capacity. They are borrowing against it and hoping nobody notices until launch, when the new system sits unused because nobody actually got the team ready to work differently.
What This Means for How You Lead
If capacity is the real constraint, the job changes. You are no longer just managing scope, schedule, and budget. You are managing people's actual bandwidth to absorb change, and that has to be planned for as deliberately as any other resource.
A few shifts worth making:
Treat resources as people, not hours. A resourcing plan that only tracks hours available misses the fact that a person juggling three projects has less real capacity than the math suggests. Context switching has a cost. Account for it.
Budget time for change, not just for build. If your project plan does not include time and people dedicated to helping the organization adopt what you are building, you have not actually planned the project. You have planned half of it.
Say no earlier. Weak executive alignment and unclear prioritization both eat capacity fast, because teams end up doing work that gets deprioritized or reversed later. Protecting capacity means protecting the team's time from work that was never going to matter.
Make capacity visible. Budget gets a line in every report. Capacity rarely does. If your team's real bandwidth is not part of your regular reporting, you are managing blind on the one constraint that is actually driving your outcomes.
The Takeaway
Budget will always matter. But it is no longer the thing most likely to sink your project. Capacity is. The leaders who see that shift early, and who start planning for people's real bandwidth instead of theoretical hours, are the ones who will keep delivering while everyone else wonders why a well-funded project still fell apart.
An unexpected outcome of changing your approach is that people work harder for you! They appreciate the boundaries you set; they recognize what you are putting forth to protect their energy; they want to do well for you.
The question worth asking in your next planning session is not "do we have the budget." It is "do we actually have the people, and have we protected their time to do this well."
Let's get out there and Make It Real!
If this resonated, share it with a leader in your network who wants to try a new approach.
Add comment
Comments