Eliminating Hero Culture on our Engineering Teams
summary
Argues that hero culture creates single points of failure, technical debt and stalled careers, with some employees routinely pulling 60+ hours and losing PTO; prescribes concrete fixes: make mandatory documentation, run weekly knowledge transfers and require pair programming plus onboarding with a technical lead, incremental policy changes and review criteria that reward mentorship; reports these practices offload work, spread knowledge and reduce burnout when applied gradually.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:03What is hero culture
- 3:31Signs of hero culture
- 6:42Consequences of hero culture
- 9:37Solutions to hero culture
- 14:29Policies and processes to change
- 18:17Key takeaways and conclusion
related talks
17mEliminating hero culture in software engineering teams
19mFireside Chat with Quintessence Anx
26mPrevent Heroism: How to Work Today Reduce Work Tomorrow
05m5 ways to burnout your engineers
05mBreaking Hero Behaviour
28mFrom Hero to Zero: a guide to destroy your best employees
36mFrom Hero to Zero practical guide to destroy your best employees
42mA Quality Hero Complex