FinOps becomes more valuable when it stops reporting and starts translating

I joined Michael Stephenson on Turbo360’s FinOps on Azure podcast to talk about a problem I keep seeing in practice: cloud cost is still treated as something to optimise after the fact, even when the real questions are strategic.

That is where many FinOps efforts become smaller than they should be. They stay close to dashboards, discounts, and reporting cycles, while the harder decisions sit elsewhere: what level of risk the company is willing to take, where it is willing to spend ahead of demand, which outcomes matter enough to justify higher cost, and which trade-offs are simply not acceptable.

My view is that FinOps becomes far more useful when it starts there.

I did not arrive at that position through theory alone. Part of what shaped it was seeing cloud through a market lens. At Strategic Blue, I learned to look at reserved instances and similar commitments less as savings tricks and more as financial instruments. They are ways of expressing a view about future demand, price, and risk. That changes the conversation. The question is no longer ‘How do we get a discount?’ but ‘What kind of exposure is the organisation prepared to hold?’

That is why I keep arguing for top-down FinOps.

A top-down approach begins with executive intent. The C-suite defines the business direction, the level of acceptable risk, and the outcomes that justify investment. From there, that intent has to be translated into something operational: policies procurement can support, constraints engineers can work within, and financial expectations that can actually be monitored. Without that chain, strategy gets diluted at every layer until teams are left optimising local cost while the organisation absorbs unmanaged risk.

This also changes what a good FinOps practitioner does.

The role is not to act as a human discount button. It is to translate between finance, procurement, leadership, and engineering so that cloud decisions reflect what the business is actually trying to do. That requires more than tooling. It requires language, judgement, and enough financial literacy to understand how the organisation describes value to itself.

That is one reason I think quarterly shareholder reports matter more than many practitioners realise. If you want influence, you need to understand how the business talks about performance, risk, and growth. Another dashboard rarely gives you that. Reading the financial story the company tells the market often does.

That, more than anything, is the shift I wanted to surface in this conversation with Michael. FinOps does not become strategic because we say it does. It becomes strategic when it can carry executive intent all the way into implementation without losing the plot.

If you want to hear the full discussion, the interview is on Turbo360’s FinOps on Azure series.