Culture is still a challenge
summary
Culture is deeply ingrained, forms early, and resists change; a historical example is the Welsh longbow flipping battlefield outcomes, showing a single tool can upend assumptions. Concrete claims: 70% of change initiatives fail and about half fail for cultural reasons (70% of 70%). Tech teams can change automation and metrics easily and share learnings via Slack or lunch-and-learns, but shifting organizational values requires executive buy-in; microcultures grow by opt-in success and then scale.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 0:44What is culture
- 3:12Battle of Crecy analogy
- 6:17Why culture is hard to change
- 8:22Edgar Schein's culture model
- 12:12Occupational vs organizational culture
- 14:41Breaking down silos
- 16:07Culture vs automation and metrics
- 17:56Microcultures and opt-in culture
- 19:19Summary and closing
related talks
43mSoftware Eats Culture For Breakfast
54mCloud Native Culture
14mA DevOps Mindset: Transforming Organizational Culture
27mTechnology is Easy. Culture is Hard.
45mShift Your Leadership
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
28mThe critical aspects of our transformations DevOps, Agile, Ecological
27mCulture Trumps YAML