Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency (2001), a DeMarco solo work published by Broadway Books, extends the peopleware-thesis from individual working conditions to the organizational structures that enable or prevent adaptation, learning, and sustainable performance. It is the second most important work in DeMarco's output after peopleware and represents his most sustained engagement with organizational theory.
The central argument
DeMarco defines slack-concept as the degree of freedom required for an organization to effect change. The pursuit of maximum efficiency — eliminating all slack from processes, schedules, and utilization — sounds rational but is, he argues, systematically destructive. An organization at 100% utilization has no capacity to respond to the unexpected, to improve its processes, to allow workers to develop skills, or to do the extended concentrated work that produces genuinely valuable output.
The efficiency argument relies on a conceptual error: treating organizations as production systems where throughput is the primary variable. In a factory producing identical widgets, maximum utilization is genuinely efficient. In a knowledge organization where the work is novel and the workers' cognitive state directly affects output quality, maximum utilization destroys the conditions that make good work possible.
The flow connection
The flow-and-interruption-cost argument from peopleware reappears here at the organizational level. A developer working in a fully loaded schedule — every hour allocated, every task tracked, every interruption demanded by a manager anxious about visibility — cannot achieve the extended concentration that mihaly-csikszentmihalyi's flow research identifies as the condition of best performance. The organizational structure that pursues maximum utilization is, in this sense, optimizing against the very outcome it claims to want.
DeMarco describes the subjective experience of working in a slack-free organization as "hurry sickness" — a state of perpetual busyness that produces the appearance of productivity while preventing the deep work that constitutes actual productivity. This connects directly to the spanish-theory-of-management critique in peopleware: the belief that value can be extracted through pressure rather than created through conditions.
Organizational learning
The book's most original contribution beyond peopleware is the analysis of organizational learning. Organizations learn by reflecting on what they've done — identifying patterns, recognizing mistakes, experimenting with improvements. This reflection requires time and mental bandwidth that fully loaded organizations do not have. The result is the organizational-learning-disability: organizations repeat the same failures because they never had the slack to understand why they failed.
This argument anticipates the lean software movement's emphasis on kaizen (continuous improvement) and the Agile principle that teams need retrospectives built into their process. You cannot improve a process you are too busy to examine.
Risk and change
Slack addresses risk management directly, anticipating themes that DeMarco and timothy-lister would develop in waltzing-with-bears. An organization with no slack cannot absorb unexpected events — a key dependency failing, a requirement changing, a team member leaving. The organizations most at risk of catastrophic project failure are precisely those operating with the tightest margins, because they have no buffer capacity to absorb variance.
Position in the intellectual arc
Slack belongs to what might be called the organizational-dynamics-era of DeMarco's work — the period following peopleware in which he extends its individual-level insights to organizational structure and management philosophy. Together, peopleware (individual conditions) and Slack (organizational structure) constitute his complete argument about the preconditions for valuable knowledge work. The 2003 waltzing-with-bears continues this arc with a specific focus on risk management.
The book was well received in the software and Agile communities and remains a standard reference in discussions of capacity planning, utilization targets, and the hidden costs of busy organizations.