The Capacity Plan: Why Teams Overcommit and How to Stop

Every team in every company has the same disease, and it has the same cause. The disease is overcommitment: too much work, too few people, everyone drowning. The cause is that capacity is treated as a feeling instead of a number. Teams promise what they cannot deliver because nobody has ever sat down and calculated what they actually can deliver.

The capacity plan is that calculation. It is not a project management ceremony, it is the simple act of comparing the work you are asked to do against the work you can actually do, before you say yes. Teams that do this consistently stop overcommitting. Teams that refuse to do it will keep drowning, and blaming themselves for it.

1. Capacity Is Not Effort

The first confusion is between capacity and effort. Effort is how hard people work. Capacity is how much work can be done in a given time. A team can run at maximum effort and still have zero capacity for new work, because every hour is already spent. Adding effort, working longer, working harder, does not create capacity. It only delays the collapse.

This is why the phrase "we just need to work harder" is so dangerous. It ignores the arithmetic. If the team has forty hours a week each and forty-five hours of work each, the solution is not more effort, it is less work or more people. The capacity plan makes this visible, and visible problems are solvable.

2. The Real Numbers

The capacity calculation is simple arithmetic, and it starts with reality. A person works five days a week, but not all of it is productive work. Meetings take a third of it. Admin takes a slice. Unplanned firefighting takes another. The industry-standard planning number for a knowledge worker is around sixty to seventy percent of nominal time, and even that is optimistic for most teams.

Multiply the real percentage by the number of people, subtract the work already committed, and you have the actual capacity for new work. The number is always smaller than the team's reputation, and that is exactly the point. The plan does not invent capacity, it discovers it. And discovering it before the commitment is infinitely cheaper than discovering it after.

3. The Maintenance Tax

Every system has a maintenance burden, and most plans forget it. The software that needs fixing, the customers who need support, the processes that need running, the debt that keeps accumulating, all of it consumes capacity without appearing on any roadmap. It is the tax you pay for having a business at all.

The capacity plan must include the tax, explicitly, or the plan is fiction. The practical rule is to reserve a fixed percentage of every person's time for unplanned work, and to treat that reserve as sacred. When the reserve gets consumed by emergencies, the next month's plan gets smaller, not the promises bigger. The teams that survive are the ones that budget for the unexpected.

4. The Commitment Ladder

Overcommitment rarely happens in one dramatic moment. It happens in small increments: a quick favour here, a small request there, a "can you also" that nobody wants to refuse. Each increment is tiny. The sum is catastrophic. The ladder of small commitments is how teams end up promising twice their capacity.

The defence is a single question at every request: what is this going to take off the plan. The question forces the trade-off into the open. The answer is either "nothing, we have slack" or "this, which means that moves". There is no third option, and the third option, "we will just manage", is the lie that builds the ladder.

5. Say No to the Work, Not to the Person

The hardest part of capacity management is the word no, and the skill is separating the work from the person. "No, we cannot take this on" is not the same as "no, I do not value you". The request is being declined, not the relationship. Most people cannot hear this distinction, so the manager has to say it explicitly and often.

The professional form of no comes with options. "We cannot do this by Friday, but we can do it by the end of the month, or we can do half of it this week." The options turn the refusal into a negotiation about what matters most, which is exactly where the conversation should be. The stakeholder gets something real, and the team keeps its capacity.

6. The Plan Is a Promise

A capacity plan is not a forecast that can be quietly missed. It is a promise to the people on the team and to the people waiting for the work. When the plan is broken, trust is broken, and trust is the only thing that makes future plans possible. The team that consistently delivers what it promises becomes the team that gets the good work.

The flip side is that the plan must be honest to be a promise. An honest plan says "we can do three of these five things well, or all five badly, choose". The dishonest plan says "we will do all five" and delivers three badly. The first conversation is uncomfortable. The second conversation, the one where you explain why the promises were broken, is far more uncomfortable. Choose the first.

7. The Monthly Recalibration

Capacity is not a constant. People leave, priorities shift, emergencies happen, and the plan that was right in January is fiction by March. The answer is not to abandon planning, it is to recalibrate it on a fixed rhythm. Once a month, sit down with the numbers, compare the plan to reality, and rebuild it.

The recalibration is where the learning happens. What did we underestimate, what did we overestimate, what did we forget to include. Each cycle makes the next plan better. The teams that plan monthly are not more bureaucratic than the teams that plan yearly. They are more honest, and honesty is the only thing that makes a plan worth having.

8. Capacity Is a Culture

In the end, capacity management is not a spreadsheet, it is a culture. The culture where it is normal to say "we do not have room for that", where the plan is a promise, where the maintenance tax is budgeted, where effort is not confused with output. That culture is rare, and it is the reason some teams are consistently great.

The culture starts with one honest conversation about the numbers, and it is maintained by repeating the conversation every month. The team that knows its capacity, protects it, and communicates it becomes the team that stakeholders trust. And trust, not effort, is the real currency of delivery.

Tags

#management #operations