Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Other, alternatives like "Not right now" or "Can we stop working on x and focus on this?” While it's important to meet customer requests, allowing them to get everything they want can negatively impact our employees and take time away from items help all customers. Agile has streamlined the process of request and delivery, but it can also lead to wasting time on less important tasks. To protect our employees and our business, we should focus on the highest priority items that will improve our MESS. M-Maintain Efficient Operations E-Expand Customers or Revenue S-Save Expense S-Security Improvements