Cloud governance maturity is measured across five dimensions: visibility, allocation, accountability, guardrails, and forecasting. Each sits at a crawl, walk, or run stage, and the dimension at the lowest stage caps the value of all the others. Score yourself honestly on each, fix the weakest first, and governance advances at the speed of its slowest part rather than its strongest. This checklist gives you the criteria for each stage and the move that takes you up one.
The common mistake is to invest in the dimension you are already good at. A team with strong visibility buys a more sophisticated dashboard while half its spend stays untagged. A team with good guardrails tightens them further while no one owns the forecast. Maturity is a chain, and the weakest link sets the strength. This sits inside the wider FinOps operating model guide.
How mature is your spend visibility?
At crawl, you see a monthly invoice and little more. At walk, you have a normalised cost view across AWS, Azure, GCP, and OCI, refreshed at least daily, with the FinOps Foundation FOCUS billing standard giving you one schema across providers. At run, near real time spend is visible to the teams that create it, not just to finance, and anomalies surface within a day. Visibility is the foundation: you cannot allocate, hold accountable, or forecast what you cannot see. If this dimension is at crawl, nothing downstream can be better.
Is your spend actually allocated?
Allocation is where most programmes quietly fail. At crawl, spend lands in a single bucket and untagged resources are the norm. At walk, a tagging policy exists and the majority of spend maps to a team or product, with a backstop rule for the remainder. At run, untagged spend sits below 5 percent, shared and platform costs are split by a rule teams accept, and the allocation survives reorganisations. Choosing how to attribute spend, showback or chargeback, is the pivotal decision here, weighed in showback versus chargeback, choosing the model.
Who is accountable for the bill?
Accountability turns numbers into behaviour. At crawl, cost is finance's problem and engineers never see it. At walk, teams receive a monthly view of their spend and a regular review happens. At run, engineering leaders own a cost target as a first class metric, a monthly review drives decisions rather than just reporting them, and unit cost is part of how teams measure themselves. The review meeting is the engine of this dimension, and a good one is described in the monthly spend review meeting that works.
A European SaaS company had a polished spend dashboard and tight budget alerts but 40 percent of cost was untagged, so the dashboard could not say who owned what. Rather than buy more tooling, we fixed the weakest link: a tagging policy with a backstop, a showback model teams accepted, and a monthly review that gave each engineering lead a target. Within the first 90 days untagged spend fell below 8 percent and accountable teams retired idle resources on their own. The wider engagement cut spend 29 percent. Figures are verified against billing data and anonymised.
Are your guardrails preventing waste without blocking teams?
Guardrails are where maturity is most misunderstood. At crawl there are none, or there are hard limits that generate tickets and resentment. At walk, budget alerts and basic policy as code catch the obvious problems. At run, policy as code prevents the most expensive mistakes at deploy time, anomaly detection catches the rest within a day, and quotas act as a safety net rather than a daily obstacle. The test is simple: good guardrails stop waste while letting engineers move. If your controls slow delivery without cutting spend, you have heavy governance, not mature governance.
Can finance trust your forecast?
Forecasting is the last dimension to mature because it depends on all the others. At crawl, the forecast is last year plus a percentage. At walk, it is built bottom up from allocated spend and tracked against actuals. At run, forecast accuracy is itself a tracked metric, variance is explained each month, and the forecast is trusted enough to size commitments and set budgets. A forecast finance trusts is only possible once visibility and allocation are solid, which is why this dimension reveals your true maturity.
The maturity checklist
| Dimension | Crawl | Run |
|---|---|---|
| Visibility | Monthly invoice only | Near real time, per team, anomalies in a day |
| Allocation | One bucket, mostly untagged | Untagged under 5 percent, shared costs split fairly |
| Accountability | Finance owns it alone | Engineering leaders own cost targets |
| Guardrails | None or blunt hard limits | Policy as code plus anomaly detection |
| Forecasting | Last year plus a percentage | Bottom up, accuracy tracked, trusted by finance |
Score each dimension, find your lowest, and make that your next quarter's work. Do not advance a dimension already at run while another sits at crawl.
Frequently asked questions
What does cloud governance maturity measure?
How do I move up a governance maturity stage?
Is more cloud governance always better?
Score your governance with us
We run the maturity assessment against your real estate, identify the one dimension capping your programme, and build the path up a stage. We take zero provider commissions and answer only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.