Software Eats Culture For Breakfast
summary
Argues that large cultural change usually fails unless new software makes different ways of working possible, backed by 11 years of State of DevOps work and a survey spanning 140,000 organizations; shows technologies that enable flow—Git, CI/CD, Jenkins, Terraform, Puppet/Ansible/Chef, Docker, NATS—let teams stop handoffs and run self‑service clouds that “blow up org charts.” Notes the popular “70% change failure” stat is a myth and points to examples like teams that deploy 50 times a day and platform teams with clear mandates as the patterns that actually work.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 3:53Culture vs technology in change
- 10:30Defining culture and its limits
- 14:02What software can and cannot fix
- 22:15Team topologies and mandates
- 27:32Technology enabling new workflows
- 35:41Summary and implications
- 36:05Q&A: Technology adoption in organizations
- 40:01Q&A: Climate change and tech impact
- 41:10Q&A: Future tech shaping organizations
related talks
54mCloud Native Culture
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
14mA DevOps Mindset: Transforming Organizational Culture
37mWant to do the DevOps? Change Everything
31mThe Continuous Culture
28mSoftware-Defined Culture
09mexplains DevOps Culture
32mTales from the DevOps Transformation Trenches