12 min · 12 chaptersNarrated in your voice
Original summary · AI-drafted, human-published · added by Library
What it's about
DeMarco and Lister argue that software projects fail far more often for sociological reasons than technical ones: bad workspaces, thoughtless management, and disrespect for concentration destroy productivity long before any compiler does. Drawing on consulting work and their own field research, they contend that the central job of management is not to extract more work from people but to build conditions where good teams can form and function. The book reoriented a generation of technical managers away from tools and toward people.
Reading plan
Pick a finish date and Genius lays out the days — the plan shows today's target and keeps you honest.
Read together
Start a circle and share the code — everyone sees everyone's honest place in the book. Accountability, not leaderboards.
Who it's for
- A software engineering manager who suspects the open floor plan is quietly wrecking output - A team lead trying to understand why some teams gel and others never do - An executive who wants to cut office costs without diagnosing why productivity keeps sliding
What’s inside
- 1The High-Tech Illusion1 min
Most software project failures trace back to sociological causes, not technical ones, even though managers instinctively reach for technical fixes.
- 2The Coding War Games1 min
Physical workspace conditions predict a programmer's performance far more strongly than experience, salary, or which company they work for.
- 3Flow and the Cost of Interruption1 min
Knowledge work depends on sustained, uninterrupted concentration, and most corporate offices are structured in ways that make that concentration nearly impossible to sustain.
- 4The Furniture Police and the Open Office1 min
Cutting office space and privacy to save on real estate costs almost always destroys far more value in lost concentration than it saves in rent.
- 5People Are Not Interchangeable Parts1 min
Treating technical staff as fungible resources, in the manner of a factory workforce, ignores the real economics of expertise, fit, and institutional memory.
- 6Jelled Teams1 min
A team's output is not the sum of its members' individual capabilities; it emerges from group chemistry that management can enable but cannot manufacture directly.
- 7Teamicide1 min
A specific, avoidable set of ordinary management habits reliably kills team cohesion, even when the manager has no intention of doing so.
- 8The Deadline Myth1 min
Compressing schedules through pressure and mandatory overtime does not produce faster delivery; it produces worse quality and, often, slower delivery.
- 9Real Team Building Versus Team Building Theater1 min
Genuine team cohesion grows out of shared meaningful work and organically formed rituals, not out of contrived corporate exercises designed to manufacture bonding.
About Tom DeMarco and Timothy Lister
Tom DeMarco and Timothy Lister were longtime software engineering consultants and principals of the Atlantic Systems Guild. DeMarco was known for pioneering structured systems analysis; Lister spent decades studying why real-world projects succeeded or failed. Together they ran large-scale field studies of programmer productivity that became the empirical backbone of this book.
What readers say
Read next
The Culture MapErin MeyerSummary15 min
Empire of PainPatrick Radden KeefeSummary13 min
Who Moved My Cheese?Spencer JohnsonSummary13 min
The Power LawSebastian MallabySummary13 min
Delivering HappinessTony HsiehSummary10 min
The Big ShortMichael LewisSummary14 min