Part 7: The FinOps Framework

Main Idea

• The FinOps Framework is a practical operating model for building and maturing a FinOps practice.
• It gives organizations a shared structure for principles, personas, maturity, domains, capabilities, and measures of success.
• The Framework is meant to be adapted to an organization's real operating needs rather than followed as a rigid checklist.

Why This Matters

• FinOps practices need a structure that keeps teams from reinventing the wheel.
• The Framework helps organizations focus on the capabilities that matter most right now while still understanding what comes later.
• It also creates a common language for discussing maturity, responsibilities, and outcomes across business, finance, engineering, and FinOps teams.

Core Concepts

• The Framework is a set of building blocks, not a fixed sequence of tasks.
• It supports practices at all maturity levels.
• Different organizations will apply different capabilities depending on their cloud usage, goals, and operational constraints.
• The Framework helps teams move deliberately instead of discovering avoidable problems through trial and error.

Think of the Framework as an Operating Model

• It is not a step-by-step recipe that every organization must follow in the same order.
• It is a structured way to decide which activities, capabilities, and improvements are most useful at a given time.
• The goal is to build feedback loops and prioritize the right FinOps actions as the organization changes.

Main Building Blocks of the Framework

• Principles.
• Personas.
• Maturity.
• Phases.
• Domains.
• Capabilities.

Principles

• The FinOps principles are the foundation for how the Framework should be used.
• Any customization of the Framework should stay aligned with those principles.
• The principles shape the intent behind domains, capabilities, and activities.

Personas

• The Framework is not just for FinOps practitioners.
• Business leaders use it to understand outcomes and investment priorities.
• Engineering teams use it to understand how their work supports FinOps capabilities.
• A shared framework vocabulary helps every persona understand the role they play.

Maturity

• Every FinOps practice uses the Framework at some level of maturity.
• Different capabilities will mature at different speeds.
• The goal is not to reach an advanced level in every capability.
• The goal is to reach the right maturity level for each capability based on business need.

Maturity Should Be Intentional

• Teams should understand both the capabilities they are actively improving and the ones they are intentionally delaying.
• Not every capability deserves the same amount of effort early on.
• Shared cost allocation is a good example: a simple agreed percentage may be enough at first, and a more complex model may not yet be worth the effort.

Phases

• The Framework aligns with the FinOps lifecycle phases:
• Inform.
• Optimize.
• Operate.
• These phases help teams improve iteratively rather than treating FinOps as a one-time project.

Domains and Their Outcomes

• Domains organize FinOps work around business outcomes.
• At a high level, the Framework domains help answer questions such as:
• What is driving cost?
• How is performance changing over time?
• Where can spending be reduced?
• How can teams make faster, data-driven decisions?

Major Framework Domains

• Understanding cloud usage and cost: Drives accountability and transparency.
• Performance tracking and benchmarking: Defines what good looks like.
• Real-time decision making: Enables fast feedback loops for spend decisions.
• Cloud usage optimization: Improves efficiency and reduces waste.
• Cloud rate optimization: Lowers the price paid through discount mechanisms and commitment strategies.
• Organizational alignment: Connects cloud usage to business structure and goals.

Capabilities Within Domains

• Each domain is made up of capabilities that solve specific FinOps challenges.
• A capability describes the data, actions, and metrics required to improve in that area.
• Capabilities are the practical units of work that help the organization achieve the broader domain outcomes.

Standard Structure of a Domain

• Definition: Explains the domain and the questions it helps answer.
• Capabilities: Lists the specific capability areas inside the domain.
• Vendors and service providers: Identifies tools or partners that can support the domain.
• Training and courses: Points to education options for building domain knowledge.

Standard Structure of a Capability

• Definition: Explains the scope of the capability.
• Maturity assessment: Shows how the capability looks at different maturity levels.
• Assessment lenses: Provides ways to evaluate capability strength.
• Functional activities: Describes the tasks and processes that make the capability real.
• Measures of success: Defines how progress is measured.
• Inputs: Identifies supporting data, resources, and references.

Five Assessment Lenses

• Knowledge: Do people understand the capability?
• Process: Is there a usable, repeatable process for doing it?
• Metrics: Is progress measured in a meaningful way?
• Adoption: Has the capability been accepted across the organization?
• Automation: Is it being executed efficiently and consistently through tooling or automation?

Functional Activities

• Functional activities are the real tasks and processes that make a capability work.
• They can include:
• enablement
• education and knowledge sharing
• advocacy
• actionable tasks
• maturity improvement through better process and tooling
• As FinOps matures, the number and sophistication of these activities grows.

Measures of Success

• Every capability should have at least one measure of success.
• These measures let teams set targets, track progress, and identify blockers.
• Example success measures include:
• percent of spend allocated to an owner
• forecast variance
• percentage of spend tied to idle or inefficient resources

Inputs

• Inputs are the materials that support a capability.
• These can include external data, vendor guidance, policies, whitepapers, training, or cloud adoption frameworks.
• Inputs help teams build functional activities and improve capability maturity more effectively.

Adapting the Framework to Your Organization

• The Framework is designed to be directional rather than prescriptive.
• Organizations should tailor it to their own processes, industry constraints, approval models, and operating realities.
• Examples of organization-specific adaptation include purchase approvals, change management workflows, and public-sector budgeting rules.

Framework Implementations

• Implementations are community-created resources that show how to apply the Framework in real contexts.
• These can take the form of guides, playbooks, assessments, or videos.
• They often reflect industry-specific, vendor-specific, or organizationally specific ways to improve a capability or domain.

Why Implementations Matter

• They help teams learn from proven approaches instead of starting from zero.
• They provide examples for situations where the core Framework needs tailoring.
• Teams can also contribute their own implementations back to the community.

Working Alongside Other Frameworks

• FinOps does not need to replace other operating models that already work well.
• It can integrate with frameworks such as:
• IT Financial Management
• Technology Business Management (TBM)
• IT Asset Management (ITAM)
• IT Service Management (ITSM)
• The goal is to clarify responsibilities, share the right information, and avoid duplicating work.

Strategic Lessons

• The Framework helps organizations build structure without forcing uniformity.
• It gives teams a way to align on outcomes, maturity, and priorities.
• It is most useful when adapted thoughtfully rather than copied mechanically.
• A successful FinOps practice uses the Framework to choose where to focus, how to measure success, and how to evolve over time.

Key Takeaways

• The FinOps Framework is an operating model for building and maturing a FinOps practice.
• It includes principles, personas, maturity, phases, domains, and capabilities.
• Not every capability needs advanced maturity right away.
• The Framework should be tailored to how the organization actually works.
• Shared terminology and common assessments improve alignment across teams.
• Community implementations can accelerate adoption and reduce guesswork.

Glossary

Term	Definition
Assessment lenses	The five ways of evaluating a capability: knowledge, process, metrics, adoption, and automation.
Automation	The extent to which a capability is performed in a repeatable, efficient, and tool-supported way.
Capability	A specific functional area of FinOps activity inside a broader domain.
Cloud rate optimization	The domain focused on lowering the amount paid for consumed cloud resources through discount strategies and commitments.
Cloud usage optimization	The domain focused on improving efficiency and reducing wasted cloud spend.
Community implementation	A guide, playbook, assessment, or other resource created by practitioners to show how the Framework can be applied in real contexts.
Definition section	The part of a domain or capability that explains what it covers and what problems it is meant to address.
Domain	A major area of FinOps focus organized around a business outcome.
FinOps Assessment	A Framework-based evaluation used to assess organizational maturity and align stakeholders around current capability levels.
FinOps Framework	The structured operating model used to design, assess, and mature a FinOps practice.
Framework implementation	A practical, contextualized application of the Framework for a specific industry, toolset, or organizational need.
Functional activities	The tasks and processes that help a capability operate and mature in practice.
Inform, Optimize, Operate	The three lifecycle phases used to organize FinOps activity in an iterative way.
Inputs	Supporting resources such as data, policies, reports, whitepapers, training, or vendor guidance that help a capability succeed.
Knowledge lens	The assessment lens that asks whether people understand a capability and its concepts.
Measures of success	The metrics used to evaluate whether a capability is working and improving over time.
Maturity assessment	A description of how a capability appears at different stages of maturity, used to assess current state and guide next steps.
Operating model	A structured way of organizing work, decisions, and responsibilities across a practice.
Organizational alignment	The domain focused on connecting cloud usage and FinOps practices to business structure and goals.
Performance tracking and benchmarking	The domain focused on defining expected performance levels and comparing results over time.
Persona	A stakeholder role involved in FinOps, such as finance, engineering, business leadership, or the FinOps practitioner.
Process lens	The assessment lens that evaluates whether a capability has a usable and valid process behind it.
Real-time decision making	The domain focused on enabling fast, data-driven responses to spend and usage changes.
Shared cost capability	A capability concerned with allocating costs used by multiple teams, often with varying levels of complexity depending on maturity.
Understanding cloud usage and cost	The domain focused on accountability, transparency, and identifying what drives spend.
Vendor and service provider section	The part of a domain that identifies tools or partners that can help implement or improve it.