This work is licensed under CC BY 4.0 - Read how use or adaptation requires attribution

Establishing a FinOps Decision & Accountability Structure

Help by contributing content for this capability

Community collaboration is at the heart of the Foundation, why not create the initial content for this page so others can benefit and build onto it?



definition for this Capability. the objective here is to capture the “What” (not the “How”) for this Capability.

Maturity Assessment

description of the characteristics of each maturity level (crawl, walk, run) for this Capability in the context of the organization’s FinOps practice.

Functional Activity

written for each persona responsible for the functional activity and processes encapsulated by his Capability. each one should be associated generally to one of the FinOps Phases (Inform, Optimize, Operate). for example:

As a [FinOps Persona], I will [functional activity] so that [desired outcome] is achieved.

Measure(s) of Success & KPI

Measures of success are represented in the context of cloud costs and may include one or more key performance indicators ( KPI ), describe objectives with key results ( OKR ), and declare thresholds defining outliers or acceptable variance from forecasted trends.

at least one measure of success; should be described in a context of cost; this could be an efficiency KPI or an agreed upon threshold or target. for example:

  • idle resource costs will not exceed 3% of total monthly cloud spend
  • anomaly costs will not exceed $150/month


the information used that contributes to the measure(s) of success listed above; information here may include specific datasources, reports or any relevant input

Resources and Projects

View All

  • Willing to contribute your real world stories, videos, a how-to guide, or a FinOps Capability playbook?
    Suggest resources here