Practice knowledge base
Workload Audits / Capacity Planning
Regular workload and capacity audits help identify chronic overload and redistribute work before it leads to exhaustion.
Documentation sections
What it is
This is a management process where leaders align the volume of tasks with the actual availability of individuals and teams. It considers current commitments, urgent requests, vacations, support tasks, and hidden work. This practice helps limit work-in-progress and enables prioritization decisions before overload becomes the norm.
When it helps
- Teams consistently take on more tasks than they can complete without overtime.
- Individuals frequently work evenings, weekends, or during their vacation.
- Deadlines shift, but new tasks continue to be added without reprioritization.
- Leaders are unaware of who lacks available capacity for new commitments.
- The same team members consistently become bottlenecks in projects.
How to start
- 1 Compile a list of active tasks, commitments, and regular hidden work for each team.
- 2 Estimate the available capacity of individuals, considering meetings, support, vacations, and existing commitments.
- 3 Identify tasks that can be paused, postponed, or reassigned to another owner.
- 4 Establish a limit for simultaneous work for the team and define who approves new urgent requests.
- 5 Conduct a brief weekly workload review and document decisions in a shared list.
Expected effect
Leaders gain a more accurate picture of available capacity and identify overload earlier. Teams find it easier to protect work boundaries, prioritize tasks, and avoid having too many unfinished tasks simultaneously.
Common pitfalls
- Calculating capacity solely based on the calendar, without accounting for support, meetings, context switching, and administrative tasks.
- Using workload audits as a means to further burden individuals, rather than as a basis for prioritizing work.
- Collecting data only once and not revisiting it when new urgent requests arise.
- Not empowering leaders to stop or postpone tasks when clear overload is present.
Further reading
- Book: Donald G. Reinertsen, The Principles of Product Development Flow
- Book: Gene Kim, Kevin Behr, George Spafford, The Phoenix Project
- Book: Eliyahu M. Goldratt, Critical Chain
- Research: Christina Maslach, Michael P. Leiter, work overload and burnout
- Documentation: Kanban Guide, Work in Progress limits
FAQ
Who should own this practice?
Typically, the owner is at the department head or operational manager level. They collect data from teams, help resolve priority conflicts, and ensure that new commitments are not accepted without a capacity check.
Can we start without a complex planning system?
Yes. For the first step, a simple spreadsheet or board is sufficient: active tasks, owners, approximate workload, deadlines, and decision status. The key is not precise forecasting, but a regular discussion about what already exceeds available capacity.
How do we know if the practice is working?
Observe if there are fewer tasks initiated without an owner and a place in the plan. Additionally, check if teams discuss overload before deadlines are missed and if solutions emerge: to postpone, remove, reassign, or clarify priority.
What if teams resist capacity estimation?
Explain that the goal is not to control every minute, but to protect against constant overload. Start with broad ranges and prioritization decisions; do not demand detailed time tracking without clear benefits for the team.