FinOps Maturity Model

The FinOps maturity model describes how advanced an organization's FinOps practice is, capability by capability. It uses three stages: Crawl, Walk and Run. A capability at the Crawl stage is basic and often manual, covering a small part of spending. At Walk, it is understood and practiced more widely, with some automation. At Run, it is mature, automated and embedded in how the organization operates. The model encourages starting small and growing in scale, scope and complexity as business value warrants.

The model is not a ladder that every capability must climb to the top. The FinOps Foundation is clear that the goal is not to reach Run in everything, but to mature the capabilities where improvement delivers business value. For IT financial management, the maturity model helps leaders assess where their FinOps practice stands, set realistic targets and explain priorities to stakeholders.

Definition of FinOps Maturity Model

The FinOps maturity model is the part of the FinOps Framework that describes levels of maturity for each capability and domain. It uses the designations Crawl, Walk and Run, with general characteristics for each stage and specific descriptions for individual capabilities.

Maturity is assessed for each capability separately. An organization may be at Run for allocation, Walk for forecasting and Crawl for unit economics at the same time. Some organizations also summarize maturity at the domain level, but the capability view is more useful for planning.

Crawl, Walk and Run

At the Crawl stage, a capability is just getting started. Processes are mostly manual and reactive, coverage is limited, and few teams are involved. Measures of success may not yet be defined.

At the Walk stage, the capability is understood and practiced across a larger part of the organization. Some processes are automated, measures of success are tracked, and the most significant issues are being addressed.

At the Run stage, the capability is well established across the organization, largely automated and integrated with other processes. Measures of success are consistently met, and the focus shifts to refinement and new opportunities.

Business Value Over Maximum Maturity

The FinOps Foundation stresses that Run is not the goal for every capability. Moving a capability from Walk to Run takes effort, and if Walk already meets the organization's needs, that effort may be better spent elsewhere.

For example, if anomaly detection at Walk is already catching the few cost spikes the organization experiences, investing in a more sophisticated approach may deliver little benefit.

The model is therefore a tool for prioritization, not a scorecard to maximize.

Importance of the FinOps Maturity Model in IT Financial Management

FinOps covers many capabilities, and no organization can improve all of them at once. The maturity model helps leaders see where the practice stands and decide where to focus.

It also provides a shared way to describe progress. Because the same three stages apply to every capability, the FinOps team can summarize a complex practice in a simple view that stakeholders can follow over time.

Executives and finance leaders can understand a statement such as forecasting has moved from Crawl to Walk more easily than a list of process changes.

Assessing the Current State

An assessment based on the maturity model gives a clear picture of strengths and gaps. It often reveals that capabilities the organization assumed were mature, such as allocation, have significant gaps in coverage or accuracy.

Involving engineering, finance, product and leadership in the assessment gives a more realistic view than a FinOps team assessing itself. Each group sees different strengths and weaknesses, and their input builds support for the priorities that follow.

The FinOps Framework includes a FinOps assessment capability that provides structure for this work.

Setting Targets

Once the current state is known, the organization can set target maturity levels for each capability based on its goals. A company focused on growth may prioritize cloud unit economics and forecasting, while one focused on cost control may prioritize usage and rate optimization.

Targets should be tied to measures of success, such as the percentage of costs allocated or the accuracy of forecasts, so that progress can be tracked objectively.

This approach aligns FinOps maturity with broader goals for IT financial management.