Slack is spare capacity — time, resources, or optionality — that is not committed to the current plan. It absorbs shock, allows reallocation when priorities change, and reduces the cost of being wrong. Systems run at 100% utilisation are brittle: any delay or failure propagates immediately. Systems with slack can absorb a missed deadline, a sick team member, or a surprise demand without breaking. The trade-off is explicit: slack costs resources in the normal case (idle time, unused capacity) and pays off when the unexpected happens. The question is how much slack is optimal — enough to be resilient, not so much that the system is lazy or wasteful.
Tom DeMarco argued in Slack (2001) that organisations that eliminate all slack lose the ability to change direction, innovate, or handle crisis. Efficiency maximisation can minimise resilience. The same applies to personal capacity: a calendar with no buffer means one overrun destroys the day; a project plan with no contingency means one slip cascades. The strategic implication: treat slack as a design choice, not waste. Name the risks you're hedging (demand spike, key person out, priority change) and hold enough slack to absorb them. Revisit when the environment changes.
Slack has a dark side: too much slack can enable procrastination (Parkinson's Law — work expands to fill time) or hide inefficiency. The discipline is to hold slack where the cost of failure is high and to use it when needed — not to fill it with low-value work by default.
Section 2
How to See It
Slack shows up wherever there is uncommitted capacity. Look for: buffer time in schedules, spare inventory, idle capacity, or unallocated budget. When someone says "we have a little room" or "we can absorb that," slack is in play. The diagnostic: is the spare capacity intentional (resilience) or accidental (waste)?
Business
You're seeing Slack when a team keeps 20% of capacity unallocated to projects so they can respond to urgent requests or fix production issues without dropping planned work. The slack costs utilisation in the short run; it pays when something breaks or a big opportunity appears. The same logic applies to cash: a runway buffer is slack for when revenue slips or a chance to acquire appears.
Technology
You're seeing Slack when a service runs at 60% CPU so that a traffic spike doesn't push it to 100% and cause latency or failure. The spare capacity is slack. Auto-scaling can provide slack on demand, but it has limits (cold start, quota); some slack is often held in reserve. The cost is unused capacity; the benefit is headroom for spikes and deploys.
Investing
You're seeing Slack when a portfolio holds cash or short-duration bonds instead of being fully invested. The slack is optionality: ability to buy when assets are cheap or to meet liabilities without forced sales. The cost is foregone return in rising markets; the benefit is survival and opportunity in drawdowns.
Markets
You're seeing Slack when a market maker or liquidity provider holds inventory or quotes wider than minimum spread to absorb order flow without moving price too much. The slack is capacity to trade without moving the market. When everyone runs with no slack, small shocks cause large moves.
Section 3
How to Use It
Decision filter
"Hold slack where the cost of being wrong or surprised is high. Size it to the risks you care about: demand variance, key person, priority change. Don't eliminate all slack in the name of efficiency; don't hold so much that the system never feels pressure. Revisit when risks change."
As a founder
Keep slack in critical paths: runway (cash), key person coverage, and capacity for the unexpected. Allocate most capacity to execution but reserve some for rework, opportunity, and crisis. The mistake: running so lean that one slip or one resignation breaks the plan. The second mistake: filling all slack with low-priority work so there's no room when something important appears. Name the slack (e.g. "20% unallocated for urgent") and protect it.
As an investor
Assess whether the company has slack. Companies that are maxed out on people, cash, and capacity have no margin for error — one bad quarter or one lost deal can force desperate choices. Companies with intentional slack (runway, bench, optionality) can absorb shock and pivot. The risk is too much slack and no discipline — burning cash on low-return options.
As a decision-maker
Use slack when you're making commitments under uncertainty. Add buffer to timelines, hold reserve capacity, or keep options open until the last responsible moment. When the cost of being wrong is high, buy slack. When the cost is low, run tighter. Revisit: is the slack still aligned to the risks we face?
Common misapplication: Treating all slack as waste. Eliminating buffer to maximise utilisation can maximise fragility. The fix: distinguish slack that hedges real risk from slack that is just unmanaged capacity.
Second misapplication: Letting slack become a dumping ground. Unallocated time gets filled with low-value work. Reserve slack for its purpose — rework, opportunity, crisis — and don't default to filling it with "whatever's left."
Buffett keeps slack in the form of cash and capacity to deploy. Berkshire holds large cash balances so that when opportunities or crises appear, he can act without selling existing holdings at bad prices. The slack is optionality; the cost is foregone return in normal times. His discipline: "We never want to be forced to sell." Slack is the design that makes that possible.
Netflix built slack into culture and systems: "adequate performance gets a generous severance" so that the team has room for stars; freedom and responsibility so that people have slack to innovate. The company also holds content and tech slack — capacity to pivot and experiment — rather than maxing out on a single strategy. Slack enables adaptation in a fast-changing industry.
Section 6
Visual Explanation
Slack: uncommitted capacity that absorbs shock and allows reallocation. Too little → brittle; too much → waste or complacency.
Section 7
Connected Models
Slack connects to margin of safety, resilience, and buffers. The models below either formalise it (Margin of Safety, Buffer), implement it (Redundancy), or warn about misuse (Parkinson's Law).
Reinforces
Margin of Safety (Systems)
Margin of safety is buffer against failure. Slack is a form of margin: spare capacity so that when demand exceeds plan or something fails, the system doesn't break. The two align: margin can be slack in time, capacity, or capital.
Reinforces
[Resilience](/mental-models/resilience)
Resilience is the ability to absorb disruption and recover. Slack contributes: uncommitted capacity absorbs shock so the system can keep functioning or reallocate. Resilience can also come from redundancy and flexibility; slack is one lever.
Leads-to
Buffer
Buffer is reserved capacity — often time or inventory — for variance. Slack and buffer are closely related; buffer is the concrete form of slack in schedules and supply chains.
Reinforces
Redundancy
Redundancy is duplicate capacity for when the primary fails. Slack can include redundant capacity that isn't normally used. The difference: redundancy is for failure of a component; slack is for variance and reallocation. Both provide headroom.
Tension
Section 8
One Key Quote
"The purpose of slack is to allow the organization to change. Without slack, there is no ability to respond to change."
— Tom DeMarco, Slack (2001)
Slack is not waste; it's the capacity to adapt. Organisations that eliminate it for efficiency lose the ability to reallocate, innovate, or absorb shock. The discipline is to hold enough slack for the change you expect — and the change you don't.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Slack is a design choice. Decide where you need buffer: runway, key person, capacity for the unexpected. Size it to the risks you care about. Don't let "efficiency" eliminate all slack; one crisis will show the cost. Don't hold slack everywhere — that's just low discipline. Name it and protect it.
Revisit when the world changes. Slack that was right for last year's volatility may be too much or too little now. When risks go up, add slack. When the environment is stable and the cost of slack is high, trim. Make it explicit.
Use slack for its purpose. When something urgent appears or a priority shifts, use the slack — that's what it's for. If you never use it because you're afraid to "waste" it, you're not getting the benefit. If you fill it with low-value work by default, you've lost the buffer.
Section 10
Summary
Slack is spare capacity — time, resources, or optionality — that absorbs shock and allows reallocation. It costs resources in the normal case and pays off when the unexpected happens. Hold slack where the cost of failure or surprise is high; size it to the risks you face. Don't eliminate all slack for efficiency; don't let it become unmanaged waste.
Work expands to fill time. The caution: slack can be consumed by low-value work if not protected. Design slack with intent.
Theory of Constraints
The constraint limits throughput. Optimising the constraint can mean reducing slack elsewhere to feed it. But the system as a whole may need slack to handle variance and change. The tension: slack away from the constraint is "waste" from a throughput view but may be necessary for resilience.
Tension
Parkinson's Law
Parkinson's Law: work expands to fill the time available. Slack can be filled with low-value work if not protected. The tension: slack is valuable when used for shock and opportunity; it's waste when it just gets filled. Design slack with a purpose and protect it.
