Be low friction
summary
Describes a concrete habit: run three quick checks before arguing — do I understand different perspectives, do I optimize for the system, should I let it go — illustrated with a code review fight over tabs versus spaces and the advice to make trivial decisions fast and commit. Recommends empathy, ask who benefits from a choice, and default to calm, rational closure so meetings stop burning time and emotional energy and teams move faster.
AI-written summary · about
chapters (5)
- 0:00Introduction and welcome
- 1:52What is high friction
- 4:47Three questions to reduce friction
- 8:05Letting go of unnecessary conflicts
- 10:17Summary and closing
related talks
35mPushing through Friction
58mStop Trying to Fix Everything
24mKeep talking and no-one explodes – Tips for smooth teams
48mEmbracing Simplicity
39mDon't Take It Personally
37mFixing the mistakes we -all- make as developers, leaders and teams
21mDerailing irrationality
29mDriving clarity in ambiguous projects
