The Uncomfortable Truth
Most DevOps failures I’ve seen were not caused by a wrong tool choice or a misconfigured pipeline. They were caused by misaligned incentives, unclear ownership, and teams that were never given permission to change.
Pattern 1: No One Owns the Pipeline
When CI/CD is “everyone’s responsibility,” it’s no one’s. The fix isn’t a better pipeline — it’s a named owner with authority to enforce standards.
Pattern 2: Velocity Is Measured, Stability Is Not
If your KPIs only count features shipped, you’ll get a lot of features and a fragile system. Error budget thinking (borrowed from SRE) is one of the most effective ways to rebalance this.
Pattern 3: The Big Bang Mentality
Clients often want to go from “no automation” to “full GitOps” in one sprint. The path that actually works: one small, visible win, then build from there.
What This Means for an Engagement
Before I write a single line of Terraform, I spend time understanding team structure, on-call rotation, and how deployment decisions are made. The technical work is the easy part.