DevOps Paradox DOP 340: Why Operations Teams Resist Every Technology Wave
Mar 4, 2026
A discussion about why operations teams prefer stability and often resist new waves like cloud, containers, and Kubernetes. The hosts explore how tool origins and tribal identity shape adoption decisions. They highlight shadow IT as a signal for change and argue for incremental migrations. They also cover practical AI uses for ops and offer ways to persuade cautious teams without promising perfection.
AI Snips
Chapters
Transcript
Episode notes
Ops Resistance Is About Identity Not Just Risk
- Ops resistance often stems from identity and incentives, not just technical judgment.
- Tools like Kubernetes and Terraform felt foreign because they were built by application developers, so ops said “not my people.”
3 A.M. War Rooms Shape Ops Conservatism
- Ops recall repeated 3 a.m. war rooms after risky developer-driven releases as painful memories.
- That history explains why stability-first incentives push many ops teams to resist rapid change.
Migrate One Service At A Time
- Move platforms in small, learnable chunks instead of grand rewrites.
- Example: migrate one service to cloud/Kubernetes, learn lessons, then repeat with adjusted vision.