FinOps

Ask most technology leaders where cloud cost management lives in their organization and they’ll point you toward finance. Someone on the CFO’s team owns the budget. Someone in procurement negotiates the enterprise agreement. Someone in a FinOps rotation audits the monthly bill and files a report. That is the dominant operating model in enterprise technology today — and it consistently underperforms. The organizations that get cloud economics right have made a different choice. They treat cloud cost as an engineering problem: something to architect, instrument, and optimize — not budget, approve, and audit. The mental model is different. The tooling is different. The ownership is different. And the outcomes are measurably, durably different. ...

Most cloud cost governance initiatives fail — not because engineering teams don’t care about cost, and not because finance isn’t watching the bills. They fail because they’re built as policies, not systems. Documents. Guidelines. Aspirations. Nobody enforces them, nobody owns them, and the behavior never actually changes. I’ve seen the artifacts in every organization that’s been through this cycle: a tagging policy in a wiki that nobody reads, a cost dashboard that was impressive at launch and now sits un-bookmarked, a Slack channel where someone periodically posts a chart of rising spend with a 😬 emoji. The governance exists on paper. It just doesn’t exist in practice. ...

I’ve looked at a lot of cloud cost management tools. Visibility platforms that aggregate your billing data and break it by service, team, and environment. Anomaly detection that alerts when something spikes unexpectedly. Rightsizing recommendations that tell you which instances are over-provisioned. They’re all useful in the same way that a good thermometer is useful — they help you understand what’s happening. But I’ve never seen a tool fix a cloud cost problem. I’ve only seen engineers fix cloud cost problems, and usually only when they understood the problem and cared about fixing it. ...

I have a lot of respect for the FinOps discipline. The people who do it well understand cloud pricing models deeply, can find waste that engineering teams miss, and provide genuine business value. But I’ve also watched FinOps programs fail repeatedly in ways that are predictable once you understand the underlying mistake: they treat cloud cost as a financial problem when it’s actually an engineering behavior problem — and those require very different interventions. ...

Every organisation I’ve seen try to get cloud costs under control starts by creating a FinOps team or a Cloud Centre of Excellence. The reasoning is intuitive: costs are rising, we need specialists, let’s centralise the expertise and the accountability. And it works — for a while. The team runs analyses, identifies waste, creates savings plans, maybe sets up a tagging policy. Costs come down, leadership is happy, the team gets credit. ...