From Hero to Zero practical guide to destroy your best employees
summary
Satirical how-to that lists concrete sabotage tactics: use micromanagement and company-wide spyware, make Teams the only chat, set ringtones to “Somebody’s Watching Me,” and personally approve every PR so pipelines stall. Kill innovation by enforcing rigid tech choices (move Python teams to Jenkins/Groovy, hire Java experts then demand Python), ban code deletion—never remove code, only comment it—and weaponize metrics (inflate story points, misuse cycle time, create expedite lanes). Ignore or neglect contributions, scapegoat failures, and normalize overtime to provoke burnout.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:50The villain in this story
- 3:54Why heroes are the problem
- 5:37Seven tactics to destroy best employees
- 6:41Tactic one: Micromanagement
- 9:08Tactic two: Stupid rules
- 10:53Tactic three: Stop innovation
- 12:17Tactic four: Sabotage communication
- 14:04Tactic five: Unpredictable decisions
- 15:50Tactic six: Scapegoating
- 17:11Tactic seven: Unrealistic pressure
- 20:17Tactic eight: Unhealthy competition
- 22:46Tactic nine: Toxic metrics
- 24:10Tactic ten: Burnout
- 27:17Summary and call to action
- 29:46Q&A
related talks
28mFrom Hero to Zero: a guide to destroy your best employees
15mHow to Keep Your Job, Whatever It Takes
21mEliminating Hero Culture on our Engineering Teams
17mEliminating hero culture in software engineering teams
22mSoyez Villains, Sabotage Your Transformation - Arkham Management School
05mBreaking Hero Behaviour
05m5 ways to burnout your engineers
05mHow to Destroy a DevOps Engineer