Team capacity · Workload management
Your Team Is at Capacity. Find Out Where the Capacity Is Going.
A full workload can leave important work untouched. Find out what is consuming the capacity before deciding what to add.
Work keeps arriving. Deadlines don't move. The team can't take on anything else, and the manager absorbs the overflow at night or on weekends.
More people or a later deadline may be the right answer. Neither should be the automatic response.
Before asking the team to absorb more, find out what it is already carrying.
"At capacity" describes the symptom
- Necessary work exceeds what the available people can reasonably complete.
- Too many projects compete for the same people, leaving each one waiting.
- Decisions and approvals run through one overloaded manager or specialist.
- Missing information, changing requirements, or unclear acceptance criteria send work back.
- Meetings and status reporting consume hours counted as delivery time.
- Interruptions, switching, and accumulated decisions may make active work slower or less reliable.
- Work that no longer matters stays open because nobody has stopped it.
High utilization, slipping deadlines, and a growing backlog can appear under any of these conditions.
Hiring can relieve a genuine shortage of people, including a scarce specialist. It won't settle a conflict over which priority should go first.
Start with what the team should stop carrying
In Melody Wilding's HBR example, a legal chief's overflow work after three acquisitions displaces the strategy he was hired to lead.
The people doing the work can point to burdens a portfolio report misses: a review that adds nothing, a meeting that has outlived its purpose, or a small request that creates hours of follow-up.
Ask the team what should be paused, reduced, or stopped:
- What work would we choose not to start today?
- What is waiting for a decision?
- What keeps coming back for clarification or revision?
- Which work depends on one particular person?
- What meetings and reports continue because nobody has stopped them?
- What new demand entered without anything else leaving?
A team can identify the trade-offs. Leadership has to settle priority conflicts that sit beyond the team's authority. Otherwise people are left guessing which commitment is safest to disappoint.
Trace one important result through the work
A workload discussion can turn into competing impressions: a staffing shortage, weak execution, or a difficult stakeholder. Trace one result to give those explanations a record to answer to.
Choose one important result that is late, partly delivered, or launched but underused. State what the shortfall means for a customer delivery, revenue, or other work that still matters. The value at stake should justify the effort of investigating.
Confirm that the result is still worth pursuing, leadership has chosen it as a priority, and the required skills, information, authority, and funding are available. Check whether an outside dependency controls progress and whether a known, workable standard has stopped being followed.
If those checks leave the cause unresolved, reconstruct the work from the expected result to its current position. Record:
- The main work steps and handoffs
- When active work started and stopped
- Where the item waited and for how long
- Which decisions or approvals were required
- What came back, changed, or had to be done again
- Which other priorities competed for the same people or decisions
Separate hands-on work from elapsed time. A result can take months without requiring months of labor. If most of the elapsed time was waiting, establish what held it there.
Waiting time delays the result. It doesn't, by itself, prove there are staff hours to recover. The people involved may be fully occupied on other work.
Look at the active stretches too. Where work slowed, contained errors, or needed repeated checking, record what else the people doing it were carrying.
Compare the team workload record with those dates to check what else was happening.
Two routes to check
ES checks two explanations separately. Either, both, or neither may account for the result.
The work path itself. Approval queues, incomplete handoffs, conflicting priorities, and repeated reviews can hold up work. The item waits for a decision, returns for a missing input, or loses its turn to another priority. Dates, handoff records, and revision histories help establish what happened.
The conditions people work under. Interruptions, switching, accumulated decisions, and little time to recover may make existing judgment, focus, and communication less reliable. Investigate this when the work is active but slows down, contains more errors, or needs repeated checking. A full calendar alone does not establish the cause.
The routes can reinforce each other. A queue can add chasing and switching. If that added demand makes active work less reliable, corrections and repeated checks can create more waiting.
A work-path finding stands on its own. An item waiting for approval establishes a delay; it does not show whether the approver's judgment or focus has deteriorated.
For a possible capacity effect, compare performance with a level the team previously sustained. Check whether errors cluster under identifiable demands and affect several people sharing those conditions. Then test whether changing the conditions improves both the operating result and the associated error pattern. Better flow alone does not isolate a capacity effect; the route itself or another change may explain the improvement.
Match the response to the constraint
| What the evidence shows | What to consider |
|---|---|
| Necessary demand consistently exceeds available working capacity | Add people or outside help, reduce scope, or change the timeline. |
| Too many priorities share the same people | Stop, defer, or sequence work before starting more. |
| Work waits for one decision-maker | Clarify decision rights, delegate within defined limits, or create an escalation rule. |
| Missing inputs or late acceptance criteria cause repeated corrections | Set the required inputs and acceptance criteria earlier. |
| A clear, workable standard is understood but no longer followed or reinforced | Restore ownership, training, review, and feedback. Check that people have what they need to meet the standard. |
| A specialist queue creates the delay | Sequence demand, improve intake, or add another specialist. |
| Errors cluster under interruptions and switching, after comparable work was previously handled reliably | Test fewer parallel assignments or protected work periods. Track completion and errors. |
| An outside dependency controls the next move | Renegotiate the dependency, find a workable alternative, or revise the date to reflect it. |
Name what the added people would do and which workload gap or queue they would relieve.
Do not turn the manager into the overflow system
A manager can become the overflow system: taking back difficult assignments, attending every review, and finishing their own work after everyone else signs off.
The cost shows up in displaced strategy work and decisions squeezed between meetings. If assignments still return to the manager for every decision, that person can become both the rescue route and the bottleneck.
Delegating a task while keeping all its decisions can leave the work waiting at the same desk.
Check whether too many projects are creating the shortage
Five projects can each look adequately staffed while all five depend on the same finance reviewer, technical specialist, or executive sponsor.
Across the portfolio, that shared person may have more demand than they can handle. New work keeps starting, status meetings multiply, and people switch between unfinished priorities.
Before approving another start, ask which current result must finish first and what will stop when the new work enters. The cost of running too many projects at once sits across the portfolio, even when each project plan looks sound.
When does a team really need more people?
A sustained shortage of time or required expertise can justify hiring or outside help. Show which necessary work is affected, what is missing, and what added help should change. Use resource capacity planning to make that gap visible.
The staffing request should connect the proposed role to the work that must finish. Count the hours people can sustain; routine nights and weekends are evidence to examine, not spare capacity to build into the plan.
For any change, record the starting position, name an owner, choose a measure, and agree when to review it. Check whether the result improved without shifting the delay or rework elsewhere. Record other changes, such as lower demand or extra staffing, that could explain the result.
Start with one result worth investigating
If an important result is falling short and the explanations still conflict, the Stalled Priority Snapshot investigates that one result.
It reconstructs the route, separates working time from waiting and rework, and checks competing explanations. The written finding identifies what the evidence supports, what could change the conclusion, and the next decision or test.
If your team can establish the cause, make the change, and check the result, an internal correction may be enough.
Projects stall, results fall short, and problems keep coming back. Trace what happened, test the explanations against the evidence, and decide what’s worth changing. 
