The four domains
| Domain | Outcome |
|---|---|
| Understand Usage & Cost | The organization can see technology usage and cost with enough quality and context to act. |
| Quantify Business Value | Spend can be connected to planning, forecasting, KPIs, unit economics, and business results. |
| Optimize Usage & Cost | Teams continuously improve usage, architecture, rates, licensing, SaaS, and sustainability trade-offs. |
| Manage the FinOps Practice | The practice itself is governed, measured, automated, assessed, and integrated with related disciplines. |
Capability map
| Domain | Representative capabilities |
|---|---|
| Understand Usage & Cost | Data Ingestion, Allocation, Reporting & Analytics, Anomaly Management. |
| Quantify Business Value | Planning & Estimating, Forecasting, Budgeting, KPIs & Benchmarking, Unit Economics. |
| Optimize Usage & Cost | Architecting & Workload Placement, Usage Optimization, Rate Optimization, Licensing & SaaS, Sustainability. |
| Manage the FinOps Practice | Executive Strategy Alignment, Practice Operations, Governance/Policy/Risk, Education & Enablement, Invoicing & Chargeback, Assessment, Automation/Tools/Services, Intersecting Disciplines. |
How to use the map
Do not memorize the Framework as a flat list. Use it diagnostically. If teams distrust numbers, look at Understand Usage & Cost. If leaders ask whether spend is worth it, look at Quantify Business Value. If waste is known but action is slow, look at Optimize and Operate behaviors. If the practice depends on heroics, look at Manage the FinOps Practice.
Every capability can mature independently. A company may have strong reporting but weak forecasting, strong rate optimization but poor allocation, or good executive sponsorship but weak engineering action loops.
Knowledge check
Q. Which statement best distinguishes Domains from Capabilities?
Outcome versus activity. Domains say what the practice should achieve; capabilities are the repeated activities that make those outcomes real.