Lesson 3 of 4
Crawl, Walk, Run: FinOps Maturity Model
Identify where an organization sits on the maturity curve and prescribe the right-sized action for each stage.
FinOpsDecode is an independent training product and is not affiliated with, endorsed by, or sponsored by the FinOps Foundation or any certification body.
Why Maturity Context Changes the Answer
A practice that is correct at Run maturity can be harmful at Crawl. Imposing automated cost guardrails on a team that has never seen a cost report will generate friction with no benefit. The exam rewards practitioners who prescribe solutions proportional to the organization's current capability. When a scenario describes an early-stage FinOps program, the correct answers are simple, manual, and visibility-focused.
Maturity Stage Characteristics
Crawl
- Basic cost visibility achieved
- Manual reporting
- Some tagging in place
- FinOps team just forming
Walk
- Consistent allocation model
- Showback reports active
- Optimization initiatives underway
- Cross-team engagement
Run
- Automated governance
- Chargeback enforced
- Real-time anomaly alerts
- FinOps embedded in SDLC
Crawl signals: 'just started,' 'no tagging,' 'first dashboard.' Walk signals: 'expanding to more teams,' 'improving accuracy.' Run signals: 'automating,' 'real-time,' 'engineering-led.' Map these to your answer's ambition level.
Recommend the next maturity step, not the end-state solution.
Practice this topic
Reinforce this lesson with scenario questions tagged FinOps Lifecycle, Crawl-Walk-Run, Governance.
Go to Practice