The math nobody wants to do
Here is a scene you might recognize. Three project managers walk into a room, each proudly announces their plan, and each one quietly assumes Priya from the data team is fully available. Priya, meanwhile, is one person with one calendar and a strong opinion about lunch.
Add up the promises and Priya is booked at 140 percent. On paper, everything is fine. In real life, something slips. Usually it slips late, quietly, and right before a deadline.
This is the heart of resource management. It is not about spreadsheets full of color. It is about telling the truth about how much work your people can actually do.
Start with real capacity, not wishful capacity
Most teams plan against a fantasy version of themselves. Forty hours a week, every week, all hands on deck, no vacations, no meetings, no support tickets.
That person does not exist.
There is no universal utilization number that works for every team, but planning project work at around 60 to 70 percent of paid hours can be a reasonable starting point for people who also carry meetings, support, administration, and unplanned work. A dedicated project team may have more usable time. A manager, specialist, or support-heavy role may have far less.
The important part is to calculate it once, honestly. Either start with paid hours and subtract time off, recurring meetings, support work, and other standing obligations, or use a percentage that already accounts for those things. Do not do both and accidentally subtract the same time twice.
What remains is the capacity you can actually commit. Everything promised beyond that number depends on overtime, luck, or other work quietly slipping somewhere else.
Plan by role before you plan by name
When you assign every future task to a specific person too early, you create a fragile plan. One resignation, extended absence, or shifting priority and the whole thing wobbles.
Instead, begin by planning capacity by role. You need two designers, one and a half analysts, and a slice of a security reviewer. Now you can see the shape of the demand without arguing immediately about who specifically does what.
This also makes over-allocation visible in a fairer way. It stops being "Priya is drowning" and becomes "we have promised three analysts of work and we have one and a half analysts." That is a portfolio problem, not a Priya problem, and it belongs on a leadership table.
Role planning is the starting point, though, not the finish line. Before committing dates, validate the plan against named specialists and scarce skills. Ten available analysts do not solve a project that needs the one person who understands the billing platform. Plan by role first, then check whether the specific people you depend on are actually available.
Make contention visible across projects
The reason resource conflicts hide is that each project plans in its own little bubble. Every plan looks healthy on its own. The pain only shows up when you stack them.
So stack them. Look at all active and upcoming work against the same pool of people. This is where you catch the double-booked specialist, the overloaded role, and the month where everything lands at once.
When you find a conflict, you have five basic moves:
- Move or sequence the work so the peaks do not overlap.
- Defer or stop lower-priority work.
- Add capacity by hiring, borrowing, or contracting, which usually takes time.
- Reduce scope and deliberately do less.
- Accept the risk, say it out loud, and write it down.
That last one matters. Every over-allocation is a decision, even when nobody admits to making it. If leadership does not choose what changes, the plan chooses for you, and it usually chooses poorly.
Protect a buffer on purpose
Healthy resource plans leave slack. Not because people are lazy, but because reality arrives uninvited. A sick day, an urgent escalation, a production issue, or a task that was harder than anyone guessed.
If your team is booked to the last minute, you have no room to absorb surprises, and surprises are the only thing you can truly count on. A deliberate buffer is not wasted time. It is the shock absorber that keeps small bumps from becoming missed dates.
The right buffer will vary by team. Stable, repeatable work may need less. Teams dealing with support, production incidents, shifting priorities, or uncertain delivery work will need more. The point is not to pick a perfect percentage. It is to leave room on purpose instead of pretending uncertainty does not exist.
Revisit it like it is alive
Capacity is not a document you write once and frame on the wall. People join, leave, get sick, and change roles. Priorities shift. Estimates change. New work arrives.
Review capacity against demand at least monthly, and more often when staffing or priorities change quickly. The goal is to see the crunch while you still have choices, not after every date has already been promised.
You can absolutely do all of this in a spreadsheet, and plenty of great teams start there. It just gets heavy fast once you are juggling shared people, scarce skills, changing dates, and competing projects across the same portfolio.
Perspective shows capacity by role and by person across the portfolio. It exposes resource contention early and helps teams sequence work with a deliberate safety buffer, so an overbooked Priya shows up before the deadline does, not after.
Start small. Pick your scarcest role, add up everything you have promised it, and compare that demand with the capacity you actually have. That one honest check can change the whole conversation.