DOP 340: Why Operations Teams Resist Every Technology Wave

DOP 340: Why Operations Teams Resist Every Technology Wave

From DevOps Paradox by Darin Pope & Viktor Farcic

March 4, 2026 · 43 min · Episode 340

About this episode

The episode discusses why operations teams often resist new technologies and the implications of this resistance on their effectiveness.

#340: The smartest ops people are often the most likely to resist new technology -- and they're not wrong. If you don't change anything, nothing breaks, and nobody blames you. That's a completely rational choice. It's also the one that guarantees you fall behind. Bare metal to VMs, VMs to cloud, cloud to Kubernetes -- every time, the teams that played it safe ended up scrambling to catch up two years later. The safe bet isn't safe. It just feels that way. It gets worse when you look at where the tools come from. Kubernetes? Built by developers. Terraform? Developers. Containers? Developers. The tools ops teams depend on were made by a different tribe. So the pushback isn't really about whether the tech is ready or whether the risk is too high. It's about identity. 'Not my people' is a harder objection to overcome than 'not ready yet,' because no amount of documentation or proof-of-concepts answers it. And about proof -- everyone wants it before they'll move. But the proof already exists. It's the tool someone on your team has been running in shadow IT for a year without any official support. If it survived that long on its own, that's stronger evidence than any pilot program…

Topics covered

  • operations
  • technology adoption
  • Kubernetes
  • cloud computing
  • DevOps

Keywords

  • shadow IT
  • proof of concept
  • AI in ops
  • identity in technology

Mentioned in this episode

Products: Kubernetes, Terraform, containers

More episodes of DevOps Paradox

Explore listener stats, chart rankings, contacts and more on the DevOps Paradox podcast page.