Why Capacity Planning Across Projects Goes Wrong — and How to Fix It
When you run more than one project at a time, the hardest resource to manage is rarely money — it is people's time. Capacity planning is the discipline of matching the work you have committed to against the hours your people can actually deliver. It sounds like arithmetic, yet it is where many portfolios quietly fall apart: deadlines slip, the same engineer is promised to three teams, and everyone blames the schedule rather than the planning behind it. The shift to remote and hybrid work has only made the strain harder to see, because you can no longer glance across the room and tell who is drowning. These are the mistakes that cause most of the damage, and what to do instead.
The mistakes that compound
Planning at 100% utilization. Treating every working hour as available work is the original sin. Meetings, email, support questions, and sick days are real. Plan to roughly 70–80% of nominal capacity for delivery work, and you stop building schedules that fail on day one.
Counting heads instead of skills. Five 'available' people do not help if only one can do the specialized task on the critical path. Capacity is constrained by your scarcest skill, not your total headcount.
Ignoring the part-timers and the shared experts. The senior person split across four projects is usually the real bottleneck, yet they are often left off the plan because no single project 'owns' them. Model shared people explicitly or they will be over-committed by default.
Planning once and never updating. A capacity plan built in January and never touched is fiction by March. Scope changes, people leave, priorities shift. The plan has to be a living view, not a one-time spreadsheet.
Confusing demand with priority. Every sponsor believes their project is urgent. Without an agreed ranking, capacity gets allocated by whoever shouts loudest, not by what matters most to the organization.
What to do instead
Start by getting demand and supply onto the same page — literally. List the committed work across all projects, the skills each piece needs, and the timeframe. Then list your people, their realistic available hours, and what they can actually do. The gaps will be obvious, and uncomfortable, which is the point. A plan that hides the conflict is worse than no plan.
Forecast in ranges, not false precision: 'this needs 3–4 weeks of a senior analyst in Q3' beats a single fabricated number.
Maintain a prioritized portfolio so that when capacity is short, you cut or defer the lowest-value work deliberately, not by accident.
Protect a buffer for the unplanned — incidents, rework, and the urgent request that always arrives — instead of pretending it won't.
Review capacity on a fixed cadence, and make reallocation decisions in that forum, not in hallway negotiations.
Make the trade-offs visible
The real value of capacity planning is not a perfect schedule — it is an honest conversation. When you can show a sponsor that saying yes to their request means a named, prioritized project slips, the decision becomes a shared one made with eyes open. That is far healthier than silently overloading people and discovering the damage at the deadline. With distributed teams, that visibility matters even more: the plan becomes the shared picture that replaces the cues you used to read in person.
Good capacity planning will not give you more hours in the week. What it does is stop you from promising hours you never had, so the commitments you make are ones you can keep.
If competing projects are stretching the same people thin, XNM's program & project delivery advisory can help you build a realistic capacity view and the prioritization to back it up.