Capacity planning compares proposed work with realistically available capability while acknowledging uncertainty, operational duties, learning, leave, and coordination. Use the team's own historical evidence where relevant, plan ranges rather than false precision, and make priority or scope tradeoffs when demand exceeds capacity. Overtime should not be the hidden assumption that makes every plan appear feasible.
Who this is for: Managers planning project and operational work for teams with variable demand, dependencies, support duties, or changing availability.
- Start with real availability, skills, operational obligations, and dependencies rather than nominal headcount.
- Estimate uncertain work in ranges and calibrate planning assumptions from the team's own delivery and demand evidence.
- When demand exceeds capacity, change priority, scope, timing, staffing, or service expectations visibly instead of relying on sustained overload.
Define usable capacity
Begin with the people and skills actually available during the planning period, including known leave, onboarding, support rotations, required meetings, maintenance, and other committed work. Headcount alone says little about who can perform a specialized task or which obligations already consume attention. Respect privacy and use formal workforce processes where required.
Distinguish planned project work from operational demand that arrives unpredictably. Use the team's own history to understand normal variation where past conditions remain relevant. Historical data informs a range; it does not guarantee the future. New systems, incidents, staffing changes, and unfamiliar work can make earlier patterns less applicable.
Size work without false precision
Break proposals into outcomes and meaningful components, then identify uncertainty, dependencies, review effort, and specialist constraints. Use ranges or relative comparisons when the evidence does not support precise duration. Ask what would make the work larger or smaller and which early investigation could narrow a consequential unknown.
Do not apply a universal utilization threshold or rigid capacity formula. Teams differ in demand volatility, role mix, service obligations, and cost of interruption. Calibrate assumptions from their own data and operating needs. Preserve room for ordinary coordination and responsible response rather than treating every unassigned moment as wasted capacity.
Make tradeoffs explicit
Compare the proposed portfolio with available capability by skill and dependency, not only a total effort number. Identify the constraint and present choices: defer lower-priority work, reduce scope, change sequencing, adjust service expectations, add qualified capacity, or accept a clearly owned risk. Each choice has consequences that sponsors should see.
Do not ask the team to 'stretch' as the unrecorded answer to every mismatch. Short exceptional effort may sometimes occur under appropriate policy, but sustained overload is not a planning resource. Managers should escalate the demand-capacity conflict and document which commitment changes. Avoid implying that resilience training repairs an impossible portfolio.
Review flow and wellbeing signals
Track incoming work, completion, blocked time, interruptions, rework, service obligations, and changed availability at a level useful for decisions. Also invite direct discussion of workload and recovery without diagnosing health. No single metric establishes safe capacity. Combine operating evidence with employee input and organizational wellbeing processes.
Replan when assumptions fail instead of demanding that the original forecast remain true. Explain what changed, which work moves, and who decides. After the period, compare assumptions with outcomes and update the team's planning range. Keep the method simple enough to maintain; elaborate calculations cannot compensate for unwillingness to make priorities.
Replan a service and project portfolio
A platform team is asked to deliver a migration while support demand and specialist availability remain uncertain.
- Map available skills, known leave, service ownership, existing commitments, dependencies, and observed variation in incoming support work.
- Estimate migration components in ranges, label assumptions, and identify the specialist review that constrains several tasks.
- Present scope, sequence, timing, and support-service tradeoffs instead of assuming extra hours will absorb the mismatch.
- Choose a plan, monitor the team's own demand and flow evidence, and replan when a stated assumption changes.
Capacity and tradeoff board
Use this board to expose assumptions and decisions, not to produce a universal formula for how fully a team should be allocated.
- Available capability: people, relevant skills, leave, onboarding, policy constraints, operations, maintenance, and committed work.
- Demand: proposed outcomes, ranges, uncertainty, interruptions, dependencies, reviews, and specialist constraints.
- Choices: priority, scope, sequence, timing, service level, added capacity, risk owner, and sponsor decision.
- Review: actual demand and flow, changed availability, workload discussion, failed assumptions, replanning, and learned calibration.
Common mistakes
- Planning from nominal headcount while ignoring operations, leave, coordination, and scarce skills.
- Applying a universal utilization target as though every team's demand and risk were identical.
- Using sustained extra hours as the hidden buffer that allows leaders to avoid changing priorities.
Try one
A sponsor adds urgent work but says all existing deadlines must remain. How should the manager respond?
A strong answer shows available capability, current commitments, uncertainty, and the specific constraint, then presents consequences and choices involving priority, scope, sequence, timing, service expectations, or qualified capacity. The manager asks the authorized sponsor to make or confirm the tradeoff and records it. They do not silently plan around sustained overtime or claim a formula proves the team can absorb everything.
Sources
- Atlassian capacity planning playA team exercise for comparing available capacity with proposed work and surfacing tradeoffs.
- CIPD employee wellbeing factsheetProfessional guidance on the organizational and managerial conditions that support employee wellbeing.