Running the Practice: Cadence, Roles and Goals

A FinOps practice runs on a rhythm — daily anomaly checks, weekly team reviews, monthly business reviews, quarterly planning — with a small central team, team champions, executive sponsorship and measurable goals.

Tools and dashboards do not change behaviour; routines do. A FinOps practice is a set of recurring conversations backed by data.

flowchart LR
  D["Daily: anomalies, alerts"] --> W["Weekly: team cost review"]
  W --> M["Monthly: business review vs budget"]
  M --> Q["Quarterly: forecast, commitments, goals"]
  Q --> D
  SP["Executive sponsor"] -.-> Q
  %% step D: Owners triage anomaly alerts and budget alerts every day, mostly automated.
  %% step W: Each team reviews its top movers, open recommendations and untagged spend in 15–30 minutes.
  %% step M: Finance, product and engineering leads compare actuals with budget and forecast and explain variance.
  %% step Q: Quarterly planning updates forecasts, decides commitment purchases and sets the next goals.
  %% step SP: An executive sponsor gives the practice authority and settles trade-offs between teams.

Roles

Role	Responsibilities
Executive sponsor	Sets the mandate, backs goals, resolves conflicts
Central FinOps team	Data pipeline, reports, rate optimisation, policies, education
FinOps champions (in each team)	Bring cost into planning, act on recommendations
Finance partner	Budgets, forecasts, accruals, chargeback
Engineering owners	Implement usage optimisation; own their service costs

A RACI (responsible, accountable, consulted, informed) per capability avoids "I thought FinOps would do it".

Setting goals

Good goals are about behaviour and value, not only savings:

Allocation coverage above 95% by end of quarter.
Forecast variance within ±5% for the top 10 teams.
Commitment coverage 70–80% with utilisation above 95%.
Every product reports one unit cost metric monthly.

Assessing maturity

Run a FinOps assessment once or twice a year: score each capability Crawl, Walk or Run, compare with what the business needs, and pick the two or three capabilities to improve next. The FinOps Foundation publishes assessment guidance you can adapt.

Education and enablement

Short onboarding for new engineers ("how to read your team's cost dashboard"), office hours, a cost section in architecture reviews, and celebrating teams that saved money or improved unit cost.

Traps: a weekly meeting that just reads charts aloud; goals defined only as "save X%"; and a central team that does the work for others, so the practice stops when it gets busy.