The slack concept is DeMarco's central argument in slack (2001): organizational slack — unallocated time, capacity, and attention — is not waste to be eliminated but a necessary precondition for organizational health, adaptability, and innovation. Organizations that are optimized for 100% utilization become brittle, unable to adapt, and paradoxically less efficient over the medium and long term.
The Core Argument
DeMarco defines slack as "the degree of freedom required to effect change." This is not a vague appeal to work-life balance or a critique of hard work. It is a structural argument about what happens to systems that have no unused capacity.
A fully loaded organization:
The result is an organization that is efficient at steady-state execution of known work — and fragile to everything else: changed requirements, market shifts, technical surprises, and the ordinary unpredictability of complex projects.
Efficiency vs. Adaptability
DeMarco frames the core tension as efficiency versus adaptability. These are in genuine conflict: the optimizations that increase steady-state efficiency (full utilization, no spare capacity, tight scheduling) are the same optimizations that destroy adaptability. An organization cannot have maximum efficiency and maximum adaptability simultaneously.
This is not a novel economic insight — it maps onto the queueing-theory observation that systems at high utilization exhibit non-linear increases in queue length and response time — but DeMarco articulates it in organizational terms that management practitioners can apply. The optimal utilization for an adaptable organization is not 100%. It is some lower figure that preserves the ability to respond to the unexpected.
How Slack is Eliminated
DeMarco describes the process by which organizations systematically eliminate slack, often without recognizing what they are doing:
1. Pressure to eliminate "idle" time. Managers trained to see unallocated time as waste apply continuous pressure to fill it. 2. Measurement systems that reward utilization. Reporting systems that track billable hours, story points completed, or tasks closed incentivize maximum output and penalize unallocated time. 3. The spanish-theory-of-management. The belief that value can only be extracted, not created, produces pressure for longer hours and tighter scheduling as the primary response to any performance gap. 4. Risk aversion about visible idleness. Individuals and teams learn that being visibly unoccupied is politically dangerous, leading to manufactured busyness.
The cumulative effect is an organization where the organizational-learning-disability takes hold: there is no time to reflect on what went wrong, no capacity to experiment with improvements, no slack to invest in the learning that would make the next project go better.
Slack and Manager Time
One of DeMarco's more pointed observations is that eliminating slack from managers has particularly severe consequences. Managers at 100% utilization become pure schedulers and status reporters — they have no capacity for mentoring, strategic thinking, relationship-building, or dealing with the unexpected. Since management capacity is the organizational resource most needed for change and adaptation, eliminating managerial slack is especially destructive.
The argument is that a manager operating at 80% of apparent maximum busyness is more valuable than the same manager at 100%, because the 20% slack is where the actual management value — judgment, learning, relationship — gets created.
Connection to Risk and Innovation
DeMarco connects slack to risk-management-as-risk-embracement in waltzing-with-bears: organizations without slack cannot genuinely manage risk because they cannot set aside capacity to deal with risks that materialize. Risk management requires reserved capacity, and reserved capacity requires slack.
The innovation connection is parallel: new ideas require experimentation, experimentation requires unallocated time, and unallocated time requires organizational slack. Organizations that have eliminated slack are not innovative organizations, whatever their culture posters claim.
The Lean Tension
The slack argument is in explicit tension with lean manufacturing's emphasis on waste elimination and just-in-time production. DeMarco acknowledges this tension and argues that it reflects a genuine difference between manufacturing (where variation can be reduced to very low levels and WIP truly is waste) and knowledge work (where variation is irreducible and unplanned work is the norm). The lean case for zero slack depends on highly predictable work — exactly the condition that does not obtain in software development.
This makes slack an important counterweight in the software management literature to the uncritical application of lean manufacturing principles to knowledge work contexts.