The best mistake gets a pizza
summary
Company growth from 4 to over 30 people prompts a practical fix: a weekly mistake of the week where team members name one error, the group discusses and votes, and the best gets a pizza — the ritual increases sharing and learning and “works well” in practice. The strategy pairs five concrete moves (flatten hierarchy, show vulnerability selectively, run team reflections, listen to junior voices, build psychological safety) with an accountability vs safety matrix; cited evidence (Google studies) shows this learning zone reduces repeat failures.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:48Why I talk about mistakes
- 11:33Fear of mistakes
- 13:19Five ways to safety
- 20:03Accountability vs safety
- 22:11Mistake of the week
- 23:58Q&A
related talks
22mFumbling Forward: Embracing Mistakes in Agile Teams
34mDebug Your Team and Maximize Its Potential
20m"I'm Here by Mistake"
41mBuilding Trust in Teams
31mWe All Make Mistakes: Learning from Gaffes in the Ruby Community
49mBuilding Trust in Teams
37mFixing the mistakes we -all- make as developers, leaders and teams
32mBetter: Fearless Feedback for Software Teams