Cover of Slack

Slack

Getting Past Burnout, Busywork, and the Myth of Total Efficiency

by Tom DeMarco · first published 2002

55mentions
24recommended by
40HN commenters
2008–2026first – last mentioned

60% recommend38% neutral3% critical

Why HN recommends it

Argues that running people at full utilization kills adaptability and innovation, and that spare capacity pays off. Suited to managers and engineers dealing with burnout, busywork, and over-optimized teams.

Summarised by Claude from recommending comments

Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Mentions per year

70 2007: 0 mentions2008: 2 mentions2009: 1 mention2010: 0 mentions2011: 4 mentions2012: 4 mentions2013: 3 mentions2014: 2 mentions2015: 3 mentions2016: 2 mentions2017: 1 mention2018: 1 mention2019: 3 mentions2020: 5 mentions2021: 5 mentions2022: 7 mentions2023: 1 mention2024: 3 mentions2025: 2 mentions2026: 2 mentions200720172026

What Hacker News says

  • fmajid · Sep 5, 2022 · Recommends

    …metrics from your project management tools is like looking for your lost keys under the streetlamp because that's where the light is brightest. It is also important to recognize the importance of keeping slack in a system and not over-optimizing it, as explained in Tom DeMarco's excellent book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency.

    on “Useful engineering metrics and why velocity is not one of them” ↗
  • geofft · Dec 10, 2014 · Recommends

    …be profitable when one resource is unavailable, then have more resources. This is as true of hard drives and fire exits as it is of employees. Expanding on a point by brational, see Tom Demarco's book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. It makes the argument that if your goal is long-term profitability, you must have some excess capacity in human resources at all times.…

    on “Travis CI: From Open to Minimum Vacation Policy” ↗
  • mindcrime · Aug 2, 2012 · Recommends

    He didn't - IIRC - talk about "20% time" specifically, but Tom DeMarco wrote a whole book about the importance of "slack" time at work. One point he makes is that if everyone is too busy doing the routine stuff 100% of the time, then the firm can't adapt quickly, because nobody has time to learn anything new, do exploratory…

    on “Today is Goof Off at Work Day” ↗
  • aytekin · Sep 5, 2011 · Recommends

    "Slack" is also a great read: http://www.amazon.com/Slack-Getting-Burnout-Busywork-Efficie...

    on “3 books every development manager should read” ↗
  • diego · Dec 27, 2011 · Recommends

    * Thinking Fast, Slow by Daniel Kahneman * Steve Jobs, by Walter Isaacson * Slack, by Tom DeMarco (also re-read Peopleware). Both of these books are fundamental to anyone developing software within an organization. * Delivering Happiness, by Tony Hsieh. It's not fantastic but it's…

    on “Ask HN: Best book you read in 2011” ↗
  • saidajigumi · Dec 1, 2014 · Recommends

    …point of the article. It is definitively not about programming abilities, or speed of these abilities. Many authors have hit TFA's points from different angles. For example, Tom Demarco's excellent Slack[1] introduces uses of "efficiency" (what speed is the organization moving at?) versus "effectiveness" (is the organization moving in the right direction?). DeMarco uses these to illustrate that many…

    on “The Case for Slow Programming” ↗
  • curtis · Nov 26, 2016 · Recommends

    This seems like an opportune time to mention "Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency" by Tom DeMarco (DeMarco is better known as one of the co-authors of Peopleware). https://www.amazon.com/Slack-Getting-Burnout-Busywork-Effici...…

    on “Ask HN: What causes an amazing company culture flourish? What kills it?” ↗
  • bena · May 6, 2022 · Recommends

    The article can be summed with with a link to the book it itself links: https://www.amazon.com/Slack-Getting-Burnout-Busywork-Effici...

    on “Efficiency is the enemy? (2021)” ↗
  • saidajigumi · Nov 27, 2022 · Recommends

    Having worked at a company that did a four-day week, I'll chime in that it was both amazing and eye opening. I say that as someone who had read Tom DeMarco's now-classic book Slack[1] long ago, after a lot of up-close and personal with the antipatterns described therein. Intellectually, I expected something(??) good but the reality was even more suprising. With a four-day work week,…

    on “A hundred UK companies sign up for four-day week with no loss of pay” ↗
  • Blackstrat · Mar 31, 2023 · Recommends

    …writing code everyday and wasn't going to follow at practice that I myself had hated. This process worked great until I worked for a PMP-driven company, where projects routinely crashed and burned. Slack by Tom DeMarco should be required reading for all PMPs and their managers.

    on “Why are developers expected to estimate tasks at all?” ↗
  • vonnik · Jan 13, 2025 · Recommends

    relevant: Slack, by Tom DeMarco https://www.amazon.com/Slack-Getting-Burnout-Busywork-Effici...

    on “The Tsunami of Burnout Few See” ↗
  • hoop · Jun 6, 2015 · Recommends

    …basically the entire book. In this same category I could also recommend "The Great Jackass Fallacy" by Harry Levinson[5]. Now on the wall between people management and engineering/project management is "Slack" by Tom DeMarco[6], which is about how organizations and managers tend to run their staff at 100% capacity. As the book points out, however, this is a good way to not only burn people out, but it also…

    on “Ask HN: Reading for first time managers” ↗
  • pdfernhout · Mar 25, 2019 · Recommends

    …developers: https://github.com/pdfernhout/High-Performance-Organizations... It includes, among other things, a link to the Khan Academy Engineering Management Reading List. See especially the first book on the list about a need for "slack" (free time, not the software) called "Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency" by Tom DeMarco". The summary: "There is a tradeoff between efficiency (meeting previous…

    on “Interviews with developers who became managers” ↗
  • praptak · Jan 4, 2012 · Recommends

    There's a whole book that goes much deeper into this subject: "Slack" by deMarco (of "The Mythical Man Month" fame. Edit: Crap, it was "Peopleware", thanks for pointing it out) It describes some negative effects of 100% utilization efforts. The funniest one is that the…

    on “The Myth of 100% Utilization” ↗
  • prakash · May 1, 2008 · Recommends

    Tom DeMarco's books are awesome. Slack really opened my mind, instead of optimizing every waking hour, I used a "structured procrastination" approach in getting things done.

    on “Be smarter at work, slack off” ↗

Keyboard shortcuts

/
Focus search
j / k
Next / previous book
Enter
Open focused book
Esc
Close / go back
g h
Go to Home
g t
Go to Top all-time
g m
Go to Most recommended
g r
Go to Rising
g f
Go to For You
?
Show this help