Phases and Maturity
The three phases
FinOps operates in an iterative loop: Inform, Optimize, Operate. Inform creates visibility through data ingestion, allocation, reporting, and anomaly detection. Optimize changes usage or rates: rightsizing, eliminating waste, commitments, and workload design. Operate runs the practice day to day: budgeting, forecasting, reviews, accountability, and continuous improvement. The phases repeat; they are not a one-way project sequence.
Maturity: Crawl, Walk, Run
Maturity is assessed per capability, not as a single organization-wide label. Crawl is a valid starting point: manual, reactive, limited coverage. Walk adds repeatable process, broader adoption, and automation. Run is proactive, automated, and integrated into planning and engineering workflows. A team can be Run in allocation but Crawl in forecasting. Maturity should match business needs; over-engineering early wastes effort.
Traps
Questions often imply that Optimize comes first or that Operate means finished. Another trap is treating Crawl as failure or assuming high spend means high maturity. Maturity is not the same as tool sophistication; process adoption matters.
Worked example / rule of thumb
A team starts in Crawl: monthly cloud bill tagged by team, one owner, basic variance review. It moves toward Walk by adding showback, forecast reviews, and an anomaly alert process. It reaches Run when engineering sees cost in delivery workflows and commitments are managed against forecasts. Rule of thumb: no optimization without allocation and visibility. Inform first, optimize with evidence, then operate the loop.