Capacity Planning
Capacity planning is the process of determining how much work a team can realistically take on within a given period, based on available people, skills, and time. It prevents the chronic overcommitment that leads to missed deadlines, burnout, and quality erosion.
Also known as: resource planning, workload planning, team capacity, bandwidth planning
Why It Matters
Most teams chronically overcommit. They plan as if every person has 40 hours of productive project time per week, ignoring meetings, interruptions, administrative tasks, and context switching. Asana's Anatomy of Work research found that 60% of knowledge workers' time goes to "work about work" (communication, searching for information, status updates) rather than skilled, strategic work. This means teams have far less capacity than they assume, and planning without accounting for this gap produces commitments that were unrealistic from the start.
How It Works
Effective capacity planning starts with honest measurement of available time. For most knowledge work teams, a realistic capacity factor is 60-70% of total hours (after subtracting meetings, email, administrative work, and context-switching costs). From there, the team estimates effort for each work item and selects a set of commitments that fits within available capacity, with a buffer for unexpected work.
Inputs to Capacity Planning
- Available people: who is on the team this period, accounting for PTO, shared resources, and part-time allocations
- Available hours: total hours minus recurring meetings, administrative obligations, and support rotations
- Capacity factor: the percentage of "available" hours that translate to focused project work (typically 60-70%)
- Buffer: reserved capacity for unplanned work, production issues, and urgent requests (typically 10-20%)
- Skill constraints: certain work requires specific expertise, limiting who can do it regardless of total headcount
The Overcommitment Trap
When teams plan without realistic capacity data, they fall into a predictable cycle: overcommit, under-deliver, work overtime to close the gap, burn out, and repeat. Each cycle erodes trust (stakeholders stop believing timelines), quality (corners get cut under pressure), and morale (the team feels perpetually behind). Breaking this cycle requires the discipline to plan based on demonstrated capacity rather than aspirational targets.
Connection to Other Practices
Capacity planning is the foundation that makes sprint planning honest and WIP limits enforceable. Without it, teams set commitments based on what stakeholders want rather than what the team can deliver. It also connects directly to sustainable pace: a team that plans within its actual capacity can maintain consistent output without burning out.
Related Concepts
WIP Limits (Work in Progress Limits)
WIP limits are explicit caps on the number of tasks or projects a person or team can have in progress at the same time. They prevent overcommitment, reduce context switching, and force prioritization by making it structurally impossible to start new work until current work is completed.
Burnout
Burnout is a syndrome resulting from chronic workplace stress that has not been successfully managed. The WHO classifies it by three dimensions: energy depletion or exhaustion, increased mental distance or cynicism toward one's job, and reduced professional efficacy.
Sprint Planning
Sprint planning is a time-boxed session where a team selects and commits to a specific set of work for a defined period, typically one to two weeks. It forces explicit prioritization by requiring the team to decide both what they will deliver and what they will not attempt in that cycle.
Priority Framework
A priority framework is a shared, explicit method for deciding what work matters most when everything feels urgent. It replaces subjective judgment calls with consistent criteria that the whole team can apply.
Further Reading

Sustainable Pace Is a System, Not a Mindset
Burnout is not a willpower failure. Sustainable pace requires system-level design: load limits, recovery protocols, and

A Two-Question Priority Filter for Weeks When Everything Competes
When every task feels equally urgent, the problem is rarely volume. It is the absence of a shared filter. A two-question