Not having conflicts is not an option… let’s have good ones
summary
Asserts conflict is inevitable and productive if run as a fair, prepared process; defines a “good conflict” as topic‑focused, team‑first, quick and solution‑oriented. Offers the SOR(T) model (situation → thoughts → feelings → actions → results), coaching and simple neuroscience hacks like the six seconds calm to stop amygdala hijack, the flip test for bias, and prep rules: send data in advance, state goals, agree process. Cites 16% witness rate of illegal workplace behavior and claims diverse boards boost performance ~25–36%. Shares a failed chocolate meeting and a successful redo using the model.
AI-written summary · about
chapters (11)
- 0:00The nature of conflict
- 2:06Defining a healthy team
- 6:56Personal conflict experiences
- 10:54Characteristics of good conflict
- 15:25The conflict framework
- 20:47Managing thoughts and biases
- 26:41Regulating emotional responses
- 35:06Curiosity as a superpower
- 40:04Action and communication
- 47:10Achieving positive results
- 50:40Culture and final takeaway
related talks
54mHow To Not Strangle Your Coworkers: Resolving Conflict with Collaboration
01h 00mBuilding a Culture of Healthy Conflict in Tech Teams
25mWorkplace Zen, Handling Conflict
59mHow To Not Strangle Your Coworkers: Resolving Conflict with Collaboration
54mBuilding a Culture of Healthy Conflict in Tech Teams
47mCrucial Conversations: tools for handling difficult conversations
32mPay your (conflict) debts on time
37mFixing the mistakes we -all- make as developers, leaders and teams