Fixing the mistakes we -all- make as developers, leaders and teams
summary
Claims that communication beats lone rockstar coding for team success, backed by concrete practices: identify primitive vs ambassador brain triggers (fight/flight floods chemicals and takes ~20 minutes to clear), use scheduled Hot Topic conversation sessions, apply the step in/step out (from Crucial Conversations) and “repeat what you heard” loop, name feelings, sandwich ideas with acknowledgment and gratitude, use breathing to calm the ventral vagus nerve, and appoint a moderator; these tools aim to reduce escalation and restore productive discussion.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:25Introducing ourselves
- 1:28Disclaimer
- 3:03Our brains
- 6:08Primitives
- 8:25Triggers
- 10:48Communicating well
- 12:02Listening to understand
- 13:15The impact
- 14:16Hot Topic conversations
- 15:14Be deliberate
- 16:16Hot topic conversation
- 17:21Hot topic preparation
- 17:47Selfreflection
- 18:36Selfcare
- 19:58Safety
- 21:51Awareness
- 22:46Gratitude
- 26:48Moderator
- 27:09How are you feeling
- 28:28Books
- 29:59Vagus Nerve
- 31:35Im doing something
- 32:11Meeting tension
related talks
47mCrucial Conversations: tools for handling difficult conversations
24mKeep talking and no-one explodes – Tips for smooth teams
57mDebugging Difficult Conversations - Or "How not to chicken out"
11mRiding the rollercoaster of emotions
36mDifficult Conversations
01h 00mBuilding a Culture of Healthy Conflict in Tech Teams
40mClosing Keynote
36mThe Developer's Model for Talking to Managers