The Splash in the Ocean Fallacy

Why most FinOps savings barely register in the boardroom

FinOps loves to celebrate savings. A team trims £50,000 here, cuts a cluster by twenty per cent there, and everyone feels victorious. From the team’s perspective, it is a huge splash.

But this confidence hides a fundamental misunderstanding about scale. A saving may look enormous from the perspective of the engineer who delivered it. At the executive level, it may barely register.

It is like throwing a ton of water into the ocean. Up close, the splash looks magnificent. Thirty metres away, you see almost nothing. From altitude, you see nothing at all.

FinOps often operates from the shoreline. Executives operate from altitude. This mismatch is why bottom-up FinOps struggles to gain sponsorship.

In the rest of the article, we unpack why your hard-won savings often disappear once they leave the engineering floor, and what changes when FinOps shifts from tactical tasks to strategic impact. If you want your work to matter higher up, this is the part you shouldn’t miss. Keep reading.

FinOps practitioners assume that “saving money” automatically matters to senior leadership. But executives do not react to tactical improvements; they react to strategic movement. They look at margin trajectories, cash flow timing, competitive pressure, product velocity, risk posture, and capital allocation.

A tactical saving without strategic relevance is simply noise.

This fallacy leads to a second dysfunction: engineers end up doing optimisation work informally, squeezed between feature deadlines, hidden outside the backlog, and rarely recognised. Teams attempt to “do FinOps on the side” and then wonder why it never scales.

Top-down FinOps fixes this by giving savings a purpose and a structure. FinOps provides recommendations. Platform allocates capacity. Managers put work into the backlog—because if it’s not in the backlog, it doesn’t exist. Engineers execute inside the normal sprint machinery. And the company rewards their contribution because it supports an explicitly stated business initiative.

Savings stop being splashes. They become waves, noticeable, directional and meaningful at executive scale.

Bottom-up asks: What can we save?
Top-down asks: What are we trying to achieve and how can savings help us get there?

Only the second question earns sponsorship. Only the second question earns attention. Only the second question turns optimisation into progress.