Navigating team friction
summary
Argues that team friction comes from predictable brain responses and names a concrete mechanism: six core needs (BICEPS) that trigger amygdala hijacks. Gives exact, repeatable practices: a feedback equation (observation → impact → question), regular retros, a living team charter, and a Venn diagram of roles to map responsibilities. Uses a desk-move case study and surgery research to show familiarity with teammates affects outcomes, and emphasizes measurable changes in meetings and documentation to reduce recurring storming.
AI-written summary · about
chapters (11)
- 0:00Start
- 8:20Core Needs at Work
- 9:33Improvement Progress Progress towards purpose, improving the lives of others
- 11:45Belonging Improvement/Progress Choice Equality/Fairness Predictability
- 15:56Significance No more comer office Far from leadership
- 16:26Knowing and addressing core needs is a shortcut to making others feel understood and valued.
- 17:49Feedback equation bit.ly/FeedbackEquation
- 19:23behavior
- 22:25Ask about their preferred feedback medium
- 23:35TEAM PROCESSES
- 24:05Retrospectives
related talks
30mNavigating team friction
37mFixing the mistakes we -all- make as developers, leaders and teams
44mUsing Neuroscience To Build High Performance Teams
01h 00mBuilding a Culture of Healthy Conflict in Tech Teams
32mA Neurobiologist's Guide to Mind Manipulation
39mThe Key To High-Performing Teams Based On Trust
43mRetrospect Yourself!
42mKeynote: Upside Down