demarco's 2001 book extends the argument of peopleware from the individual programmer's environment to the organizational conditions that enable or prevent flow, adaptation, and sustainable performance. The central claim is that the pursuit of maximum efficiency — eliminating all "slack" from processes and schedules — systematically destroys the organizational capacity for learning, change, and the kind of concentrated work that flow requires.
The slack argument
DeMarco defines slack as the degree of freedom required to effect change. In a fully optimized system, every resource is utilized at maximum capacity at all times: no worker has spare time, no project has schedule buffer, no team has capacity to take on unexpected work. This sounds like efficiency but is, DeMarco argues, the enemy of adaptation. Organizations with no slack cannot respond to change, cannot experiment with process improvement, cannot allow workers to achieve the extended absorption that produces their best work.
The connection to flow-state is explicit: DeMarco describes the mental overhead of a worker who is simultaneously fully booked, constantly interrupted, and held accountable for every minute of their time. Under these conditions, the challenge-skill-balance that produces flow is impossible to achieve — challenges are arbitrary (imposed by schedule pressure) rather than intrinsic to the work, and the worker's attention is perpetually fragmented across competing demands. The result is not high performance but what DeMarco calls "hurry sickness" — an appearance of activity without the concentrated engagement that produces real output.
Organizational learning and flow
Slack also addresses organizational learning, which requires downtime and reflection that efficiency-maximized organizations cannot afford. DeMarco draws on Donald Schon's work on reflective practice and anticipates the lean/Agile argument that improvement requires capacity — teams operating at 100% utilization cannot stop to identify and address systemic problems. The connection to flow is that learning and skill development — the activities that allow challenge-skill balance to be maintained as complexity grows — require the same protected time and mental space as flow work itself.
Relationship to Peopleware and the software lineage
Where peopleware focused primarily on the physical and social environment (quiet space, uninterrupted time, team cohesion), Slack focuses on organizational structure and management philosophy. Together, they constitute DeMarco's complete argument about the conditions for knowledge worker flow: you need both the environmental conditions that allow individual absorption (Peopleware) and the organizational structure that provides enough time and freedom for that absorption to occur at all (Slack).
newport's deep-work-newport (2016) cites both works as precursors and makes the same argument in the context of the contemporary attention economy — social media and smartphone proliferation having made the problem DeMarco diagnosed in 2001 substantially more severe. The throughline is consistent: the organizational and technological forces that maximize apparent activity minimize actual deep work, and the correction requires deliberate structural intervention.
Position in the lineage
Slack belongs to the software-bridge-1987-2001 era and marks the end point of DeMarco's primary contribution to the flow lineage. It extends the individual-level flow argument of Peopleware into a systemic organizational critique, anticipating lean thinking about WIP limits, capacity utilization, and the cost of context switching. The book was well received in the software community and remains cited in Agile and lean-software discussions as one of the foundational arguments for why high-utilization, always-busy organizational cultures produce worse software outcomes.