Tensions in Practice: Current utilization in tension with spare capacity¶
Capacity in one planning window
Filling every slot can make a plan look efficient. It also leaves no uncommitted room when unexpected work arrives. Spare capacity has a cost, and it helps only if it is still available when needed. Compare six slots, eight slots with two protected, and eight slots whose extra room is already committed. Try normal work and two larger loads to see what the reserve absorbs and where it runs out. All tasks and numbers are invented for illustration.
Use resources for current work
Avoid carrying capacity without purpose and make useful current commitments.
Preserve deployable reserve
Keep room for unexpected work without displacing the core plan.
Why these aims pull against each other
A reserve carries a resource cost but loses its protective role when every part of it is committed. Its useful size depends on uncertainty, consequences and whether it can actually be deployed.
Choose an arrangement to see what changes and what remains difficult.
Invented tasks, equal-sized slots, one window. Other commitments cannot be paused here. Unaccommodated work remains outside the capacity boundary.
What this choice protects
What it costs
When it fits
Compare the arrangements
Six slots
Provide six interchangeable slots for the usual six required tasks.
- What it protects
- The illustrative plan carries fewer capacity resources and accommodates its usual work.
- What it costs
- An eight-task load leaves two tasks outside this window; a ten-task load leaves four.
- When it fits
- Assume equal-sized tasks and a fixed window with no overtime, outsourcing or rescheduling. These simplifying rules are not staffing advice.
Illustration note: The slot counts and results are invented arithmetic illustrating the source tension, not a measured operating policy.
Eight, two protected
Provide eight slots while leaving two uncommitted under the usual six-task load.
- What it protects
- The reserve accommodates two extra required tasks without displacing the normal six.
- What it costs
- Two additional slots must be maintained during normal demand. A ten-task load still leaves two outside the window.
- When it fits
- The reserve must be usable for the arriving task, with suitable skills, equipment and timing. Its count alone cannot establish readiness.
Illustration note: The model demonstrates a finite margin, not an optimal reserve ratio or a guarantee of resilience.
Eight, all committed
Use two slots for other tasks that cannot be paused during this window; only six slots remain available for the displayed required work.
- What it protects
- Two additional selected tasks can be completed under normal demand, if those tasks have value.
- What it costs
- The extra capacity is no longer reserve: eight required tasks leave two outside this window, and ten leave four.
- When it fits
- The two other commitments are explicitly non-preemptible here. If they can be paused promptly at acceptable cost, they may instead be a valid use of recoverable reserve.
Illustration note: This arrangement illustrates deployment discipline. It does not classify all learning work or other commitments as waste.
What this illustration does—and does not—establish
System Slack supplies the tension, conditional sizing and deployment discipline. The six/eight-slot plans and six/eight/ten-task scenarios are editorial toy models. Bottleneck is linked as a related source with a different mechanism, not as something this figure proves.
- All numbers are illustrative. One equal-sized task uses one interchangeable slot for the displayed window; no real utilization target or sizing recommendation is implied.
- Tasks outside the boundary are not accommodated in this window. They are not necessarily failed, lost permanently or impossible to reschedule.
- Other commitments must remain visually distinct from the displayed required tasks. A supposedly spare resource may lack the skill or timing the arriving work needs.
- Bottleneck: Local optimization is wasted off the bottleneck, but slack is also what absorbs variation concerns protective slack in a dependent flow. This single-pool arithmetic does not model arrivals, stage starvation, queues or throughput recovery.
- Current utilization and economic efficiency are different measures. More reserve is not always better.
Source entries
System Slack
Efficiency versus resilience supplies the utilization/resilience tension; Sizing slack to uncertainty makes sizing conditional on uncertainty; Slack deployment discipline requires purposeful deployment.
T1: Efficiency versus resilience
- T1: Efficiency versus resilience. Short-term efficiency drives high utilization; resilience requires maintained slack. In stable environments, efficiency dominates; under uncertainty or during transformation, resilience proves more valuable. Mature practice consciously sizes utilization based on uncertainty profile, not as universal optimization to maximum efficiency.
T3: Sizing slack to uncertainty
- T3: Sizing slack to uncertainty. Too little slack creates fragility; too much slack creates stagnation and inefficiency. Optimal slack level depends on uncertainty magnitude and consequence of system failure. Mature practice uses scenario analysis to identify disruptions that should be absorbable, then sizes slack to enable absorption without operation shutdown.
T4: Slack deployment discipline
- T4: Slack deployment discipline. Slack available for crisis response or learning is valuable; slack that dissipates into non-strategic work is waste. Mature practice requires clarity about how slack will be deployed (crisis response protocols, learning investment governance, opportunity-response decision rules) and disciplines deployment rather than allowing slack to drift into unmotivated low-value work.
Slack is not an unlimited buffer
- Not unlimited buffers. Slack carries cost (resources tied up not immediately productive); mature practice sizes slack appropriate to uncertainty and opportunity-cost. Excessive slack is wasteful; insufficient slack is fragile. The right level is context-dependent.
Bottleneck
Local optimization is wasted off the bottleneck, but slack is also what absorbs variation describes a related but narrower mechanism: spare capacity around a limiting stage can protect flow under variation without raising its normal capacity ceiling. The toy single-pool figure does not demonstrate that stage-by-stage mechanism.
T2: Protective slack around a bottleneck
T2: Local optimization is wasted off the bottleneck, but slack is also what absorbs variation. The prime teaches that improving non-bottleneck elements yields no throughput gain, which can be read as "non-bottleneck capacity is wasteful." Yet that idle slack is frequently what allows the system to absorb variability — demand spikes, breakdowns, batch arrivals — without the constraint starving or the system seizing. Stripping all slack from non-bottleneck stages to maximize their efficiency can destabilize the very flow the bottleneck governs. The structural insight ("don't optimize off the constraint") sits in tension with the operational reality that protective slack around the constraint is itself valuable.