Improvement Capacity Planning is the practice of matching the amount of active improvement work with the people, time, leadership attention, and specialist support actually available to complete it.
The objective is not to reduce ambition.
The objective is to prevent an organization from starting more improvement than it can finish.
Distinguish opportunity from capacity
Organizations usually have more improvement opportunities than available capacity.
Improvement Backlog provides a controlled queue for accepted opportunities that are not yet active.
Capacity planning determines how much of that backlog can move into execution without overloading the system.
Define the capacity that improvement consumes
Improvement work may require time from:
- project leaders;
- process owners;
- operators;
- engineers;
- maintenance;
- quality;
- finance;
- sponsors.
A project may have a dedicated leader but still fail because required support functions are already overloaded.
Capacity should therefore be viewed across the complete project system.
Account for operational workload
Improvement work competes with:
- production;
- customer issues;
- maintenance;
- launches;
- audits;
- training;
- daily management.
Improvement Portfolio Management helps govern the active set of projects, but the portfolio should reflect real operating constraints.
A portfolio that assumes everyone has unlimited improvement time is not a realistic plan.
Limit work in progress
Starting fewer projects can increase the rate at which projects finish.
When too many projects run simultaneously, common effects include:
- delayed decisions;
- slow analysis;
- weak follow-up;
- repeated rescheduling;
- sponsor attention spread too thin.
The organization should establish practical limits for active work.
Estimate demand by project type
Not every improvement requires the same effort.
A local PDCA may require several hours.
A cross-functional DMAIC project may require months of coordination.
Improvement Project Charter can help define project scope, ownership, target, and expected effort before significant capacity is committed.
Use simple size classes if precise effort estimates are not reliable.
Protect critical specialist capacity
Some resources become recurring constraints.
Examples include:
- controls engineering;
- data analysis;
- maintenance planning;
- quality engineering;
- IT.
If every project depends on the same specialist, that role can become the bottleneck for the improvement system.
Theory of Constraints provides useful thinking for managing scarce capability as a system constraint.
Reserve capacity for emerging problems
Do not allocate 100% of available improvement capacity to planned projects.
Organizations need room for:
- customer issues;
- safety problems;
- major breakdowns;
- unexpected strategic priorities.
A fully loaded portfolio becomes unstable as soon as an important unplanned problem appears.
Review capacity as priorities change
Capacity planning should be revisited when:
- major projects start or close;
- staffing changes;
- operating demand changes;
- specialist availability changes;
- new urgent work appears.
The correct response may be to stop or defer lower-priority work rather than simply add more.
Common mistakes
Treating every accepted idea as immediately active, estimating only project-leader time, ignoring specialist constraints, scheduling improvement at 100% utilization, allowing sponsor attention to become overloaded, and measuring success by projects started instead of projects completed are common mistakes.
Practical sequence
- identify active and queued improvement work.
- estimate required roles and effort.
- assess available capacity.
- identify scarce specialist resources.
- limit active work in progress.
- prioritize the highest-value work.
- reserve capacity for important unplanned problems.
- defer work that cannot be supported.
- review capacity when conditions change.
- measure completion and benefit, not project starts.
The practical lesson
Improvement Capacity Planning protects execution.
A strong improvement system controls how much work enters the system so important projects receive enough attention to finish and sustain results.