Practice : Capacity and WIP Management
Purpose and Strategic Importance
Capacity and WIP (Work In Progress) Management is the leadership practice of actively managing how much work is in flight at any time relative to available capacity — and taking responsibility for protecting teams from overload. When WIP exceeds capacity, everything slows down, quality degrades, and the experience of doing the work deteriorates. Leaders who add work without regard for capacity create exactly this condition.
Most overload in organisations is not caused by laziness or poor execution — it is caused by leaders who have not made hard choices about prioritisation. Managing capacity is an act of leadership discipline: saying no to less important work so that more important work can be done well.
Description of the Practice
- Leaders maintain visibility of team capacity and current WIP at all times.
- Before adding work, leaders assess the impact on existing commitments and make the trade-off explicit.
- WIP limits are established per team or workflow state, and leaders protect them.
- Leaders challenge requests for additional capacity rather than automatically absorbing them.
- Capacity planning is forward-looking, not just reactive to current overload.
How to Practise It (Playbook)
1. Getting Started
- Create a simple view of what the team is currently working on and what is in progress simultaneously.
- Count the work items in flight: if it exceeds the team's realistic capacity, name the overload explicitly.
- Before accepting a new request, ask: "What do we stop, pause, or deprioritise to take this on?"
- Protect the team from the next commitment until current work is complete or explicitly deprioritised.
2. Scaling and Maturing
- Introduce WIP limits per workflow stage: explicit rules about maximum in-progress items that trigger a conversation before being exceeded.
- Review capacity at the start of each planning cycle: expected capacity, known demands, and the trade-offs required.
- Make capacity trade-offs visible to stakeholders — overload is often invisible to those requesting work.
- Track the relationship between WIP level and delivery lead time: this usually demonstrates the cost of overload directly.
3. Team Behaviours to Encourage
- Teams complete work before starting new work — "finish what we started" as a cultural norm.
- Individuals flag capacity overload proactively rather than silently accepting an unsustainable load.
- Leaders are asked before new work is committed — the team does not absorb demands without leadership awareness.
- The team tracks WIP as a health metric alongside output metrics.
4. Watch Out For…
- Leaders who commit the team to new work without reviewing current capacity.
- WIP limits that exist on a board but are consistently ignored without consequence.
- Teams that say yes to everything and trust the leader to protect them — but the leader does not.
- Treating all work as equally urgent, which makes prioritisation impossible.
5. Signals of Success
- Delivery lead time decreases as WIP is controlled — work flows faster with less in progress.
- Team members feel more focused and less context-switched.
- Trade-off conversations happen before commitments are made, not after teams are overloaded.
- Stakeholder expectations are set accurately because capacity constraints are visible and communicated.
- The team reports feeling in control of their work rather than overwhelmed by it.