Domains and Capabilities
Domains group capabilities
The framework organizes capabilities into domains so practitioners can manage related work coherently. Common domains are Understand Usage and Cost; Quantify Business Value; Optimize Usage and Cost; and Manage FinOps Practice. A capability is a repeatable business activity, not a product feature. Examples include data ingestion, allocation, reporting and analytics, anomaly management, forecasting, budgeting, unit economics, benchmarking, rate optimization, workload optimization, cloud sustainability, licensing and SaaS, education and enablement, tooling, automation, assessment, and practice management.
How the domains fit
Understand Usage and Cost creates trustworthy data and allocation. Quantify Business Value connects spend to budgets, forecasts, unit economics, and benchmarks. Optimize Usage and Cost changes demand or price through engineering, commitments, and vendor choices. Manage FinOps Practice builds the operating model: skills, tools, automation, assessment, and governance.
Traps
Candidates confuse a domain with a capability, or a capability with a tool. Another trap is jumping to optimization before allocation and reporting are reliable. Unit economics is not just cost per customer; it must connect cost to a meaningful business driver. Benchmarking is context, not a target.
Worked example / rule of thumb
If asked where chargeback belongs, trace the capability: allocation and showback/chargeback sit with understanding and allocating cost, supported by reporting. If anomaly alerts are noisy, fix data ingestion and allocation before blaming the alert tool. Rule of thumb: capabilities are interdependent; strengthen the data foundation before acting on optimization or value metrics.