Using KPIs to evaluate optimization, performance, and business value across diverse technology categories (Cloud, SaaS, Data Cloud Platforms, and on-premises environments), all FinOps Scopes, and against industry peers, to inform decision making and align FinOps activities with organizational objectives.
Benchmarking allows organizations to compare KPIs for important aspects of technology value and optimization, both internally between different teams and FinOps Scopes, and externally with other organizations using technology in similar ways. Well-defined KPIs provide the foundation for meaningful benchmarking, enabling organizations to measure performance consistently and make informed decisions that are aligned with organizational strategy and business objectives.
FinOps Practitioners should work with Leadership, Product, and Engineering Personas to identify and define KPIs that provide meaningful insights into the organization’s technology investments across all FinOps Scopes and technology categories, including cloud, SaaS, data platforms, and on-premises environments.
Internal benchmarking between different segments of the organization, or between product and engineering teams, can assist in decision making related to technology value and optimization. Internal benchmarking programs can be implemented effectively with clear definition of benchmarked KPIs, transparent communication of goals and objectives, accurate data collection and reporting, and supportive leadership. The effectiveness of internal benchmarking programs can be further enhanced through gamification or incentive programs that encourage and reward desired behaviors across stakeholder Personas.
Whenever information is available, organizations should endeavor to also benchmark their technology KPIs against other organizations. External benchmarking should be performed carefully to protect pricing, usage, and other commercially sensitive information. Because many organizations are reluctant to share detailed information publicly, implementing external benchmarking in depth can be challenging.
The FinOps Foundation community can often provide opportunities to share information informally with peer organizations. State of FinOps data can provide useful insights into the practices and performance of other FinOps practices. Analysts, large system integrators, and technology service providers can also sometimes share aggregated or summary information on certain types of technology usage and efficiency.
Every organization’s technology usage and FinOps practice will be unique. KPI and Benchmarking should be one component of a broader approach to assessing technology value and efficiency rather than the sole mechanism. FinOps Practitioners must balance this Capability with other approaches to understanding technology value and communicating the return on technology investment to Leadership.
As with many FinOps practices, perfect information is rarely available and successful organizations continuously review and refine their benchmark KPIs, making informed decisions based on the data available to them rather than waiting for ideal conditions. See the FinOps Foundation KPI Catalog for illustrative examples across FinOps Scopes and technology categories.
Shifting Left in KPIs & Benchmarking means defining, before an intervention happens, what counterfactual baseline it will be measured against, rather than assembling a justification for a number after the fact.
Cost avoidance is future expenditure prevented, not a reduction from the existing run rate (that is cost savings). A credible claim requires a documented counterfactual baseline, consistent demand and service assumptions, intervention evidence, a defined time horizon, and post-action validation.
As someone in the FinOps team role, I will…
As someone in a Product role, I will…
As someone in a Finance role, I will…
As someone in an Engineering role, I will…
As someone in a Leadership role, I will…