Pushing through Friction
summary
Explores why organizational friction stalls a 75% improvement that would take two weeks, ties recurring failures to the normalization of deviance, and frames mid‑size companies (100–2,000 employees) as the most affected. Proposes concrete fixes: single source documentation, mandatory RFCs, operability reviews, onboarding that captures new‑hire WTFs, renaming a confusing package to checkout UI, and promoting “glue work,” while stressing psychological safety and face‑to‑face advocacy as the paths that actually get changes executed.
AI-written summary · about
chapters (13)
- 0:00The frustration of friction
- 1:34Introduction to the talk
- 2:53Defining work friction
- 5:12Causes of organizational friction
- 7:54Normalizing deviance
- 10:06Friction in engineering
- 12:25Impact of growth
- 15:01Short-term fixes
- 18:34Long-term cultural changes
- 21:21Valuing glue work
- 26:17Psychological safety
- 27:52Individual agency
- 32:16Conclusion
related talks
30mNavigating team friction
06mRemoving engineering friction: Creating an evolutionary culture
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
37mLet’s Make It Easy
52mUnderstanding UnHealthy Syndromes of Software Delivery
11mBe low friction
45mOvercoming Frustrations
01h 05mSabotaging a Transformation:Myriad Ways Organizations Inhibit Transformation