5 ways to screw up your DevOps Transformation

on YouTube ↗29m

" summary

Five concrete failure modes and how they play out: naming the program DevOps creates cargo‑culting around tools like Kubernetes and CI/CD; using a rigid, linear roadmap instead of probe sense respond experiments kills learning; hiring only agile coaches leaves gaps in engineering, ops and security skills; vague culture talk never becomes behavior without joint prioritization and measurable habits; allowing Eisenbahn‑scheinbewegung—management pushing 150 features then 200 features and ignoring low confidence—produces fake change and team burnout.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 6:00Learn from Other Failures
3. 11:50Move towards an Incremental Way of Working
4. 20:09Prioritization
5. 21:30Allow Fake Change in Your Environment
6. 22:43Culture Follows Structure
7. 27:04Questions
8. 27:40Is 100 Devops Transformation Ever Possible and Is Sre the Future of Devops

" related talks

• 07mTen Ways to Doom Your DevOpsGeneGotimer · CodeMash 2023
• 05m5 Pitfalls of Using DevOps to GovernTanusree McCabe · DevOpsDays Washington, D.C. 2024
• 13mTen Ways to Doom Your DevSecOpsGene Gotimer · Conf42 DevSecOps 2023
• 33mThe DevOps disaster: 15 ways to fail at DevOpsBert Jan Schrijver · Codemotion Amsterdam 2016
• 17mDevOps Leadership in practice. True storiesAndriy Bilous · DevOpsDays Poznań 2021
• 25mDevOps: Why do we Keep Messing Up?Daniel Bojczuk · Devworld Conference 2025
• 32mTales from the DevOps Transformation TrenchesHolly Cummins · DevOps Enterprise Summit London 2019
• 49m5 Steps to a DevOps TransformationDan Barker · OSDC 2019