How to actually execute cloud cost recommendations (Inform → Operate)
Most teams can see their savings. Far fewer can ship them. Here is the workflow that moves a recommendation from a list to a verified result.
The FinOps Foundation describes a program in three phases: Inform, Optimize, and Operate. Inform is visibility: knowing what you spend and where. Optimize is identifying the changes worth making. Operate is making those changes a repeatable part of how the organisation runs.
Most teams get stuck between Optimize and Operate. They can see the savings and they can name them. What they cannot reliably do is ship them: turn a recommendation into a change that lands, sticks, and shows up on the bill. That last yard is where the value actually lives.
Why recommendations do not get done
- No owner: a recommendation assigned to "the platform team" is assigned to no one.
- No workflow: there is nowhere for the work to live between "spotted" and "done", so it lives nowhere.
- It competes with the roadmap: cost work loses to feature work every sprint unless it is scheduled like everything else.
- No proof, no reward: if nobody confirms the saving landed, the engineer who did the work gets no credit, and learns not to bother.
A workflow that ships
Treat each recommendation like a ticket with a lifecycle, not a row in a report. A workflow that consistently lands savings looks like this:
- Triage: everything that could be done lands in one inbox, ranked by value and effort, so the easy wins are obvious.
- Claim: an owner takes the item, now it is one person's job, with a name against it.
- Review and approve: the change is checked for risk and signed off, because cost work that breaks production is not a saving.
- Schedule: it goes into a real window of work, not "when we get to it".
- Implement: the owner makes the change.
- Validate: a stabilisation window watches cost and behaviour before and after, to catch reverts and surprises.
- Verify: the saving is confirmed against the bill and recorded as realised.
Make it routine, not heroic
The teams that operate well do not rely on a quarterly heroics push. They make the workflow boring: remediation SLAs so items cannot rot, a short daily digest so nothing is a surprise, and a monthly review where the numbers (including what got verified) are already on the slide. The work becomes part of the operating rhythm, which is exactly what the Operate phase means.