Cost Culture

I’ve spent a lot of time helping organizations get their cloud costs under control. The pattern is always the same: someone in finance notices the bill is growing faster than revenue. A task force is formed. Dashboards are built. Optimizations are identified.

And then… nothing really changes.

The tools aren’t the problem

Every cloud provider has cost management tools. There are dozens of third-party products that will find inefficiencies. The visibility is there. The optimization opportunities are obvious.

But costs keep growing because cost management is a behavior problem, not a tooling problem.

What I’ve learned

The organizations that actually control costs have a few things in common:

They make costs visible at the team level. Not aggregated into department-wide buckets, but broken down so engineers can see what their code costs to run. Visibility creates ownership.

They celebrate efficiency. Most engineering cultures celebrate features shipped. The ones that manage costs well also celebrate resources saved. They make heroes of people who make things cheaper.

They build cost into the definition of done. A feature isn’t finished when it works. It’s finished when it works efficiently. This sounds obvious, but I almost never see it in practice.

The uncomfortable truth

Cost culture requires executives who actually care about efficiency, not just in quarterly reviews but in how they allocate time and recognition. Without that, any cost initiative is just theater.

I don’t know how to make executives care about this. But I’ve seen enough organizations struggle with it to know that tooling alone won’t solve it.