# FinOps Assessment ## Overview The FinOps Assessment feature, is an essential resource designed to help organizations evaluate and enhance their cloud financial operations. This tool provides a structured approach for assessing the maturity of your FinOps practices, enabling you to identify areas for improvement and implement effective financial management strategies. ### Assessment Scope & Intent This guide provides a set of concepts and measurements to support an analysis of the current state and planned goals of your overall FinOps practice. This assessment can be done at any level of an organization, from specific service or functional teams, to organizational divisions or entire business units. It is designed to measure operational maturity in consistent and well-understood terms, whether you are measuring one application team or the whole organization. The goal of a FinOps Framework assessment is not to be a precise analytics grading the FinOps practice, but rather to provide a high-level overview of the current state and to identify targeted areas for the FinOps team to investigate or develop. This assessment does not need to be done for every [FinOps Framework Capability](https://www.finops.org/framework/capabilities/) at once. Targeting a single capability, or perhaps a set of related capabilities in a single domain may allow for deeper analysis on a per-capability level. This can be especially useful when those capabilities were highlighted by an earlier assessment for further improvement. For each assessment, be very clear in establishing your: * **Target Scope:** Which capability(or capabilities) are you going to be assessing? * **Target Group:** On which part of the organization will you be assessing this Target Scope? Include those who will have primary impact on the Scope and Group selected. Consider including those who might be targets for later assessments as well to give them some experience with the process. ### **Key Features** 1. **Comprehensive Assessment Framework:** The tool follows a detailed framework that evaluates your FinOps capabilities across various dimensions. It assesses your organization’s practices in cost management, budgeting, forecasting, and optimization, ensuring a thorough evaluation of your cloud financial operations. 2. **Maturity Model Evaluation:** Using a maturity model, the tool provides insights into the current state of your FinOps practices. It categorizes your organization’s maturity into different levels, helping you understand where you stand and what steps are needed to advance to more sophisticated practices. 3. **Actionable Insights:** After completing the assessment, the tool generates actionable insights and recommendations tailored to your organization’s specific needs. These insights help you prioritize improvements and address any gaps in your FinOps processes. 4. **Benchmarking and Best Practices:** The tool enables you to benchmark your FinOps practices against industry standards and best practices. This comparison helps identify gaps and opportunities for optimization, guiding you towards more efficient and cost-effective cloud financial management. 5. **Continuous Improvement:** The FinOps Assessment Tool is designed to support ongoing improvement. It encourages regular reassessment to track progress over time and adapt to changing cloud environments and financial landscapes. ### **Benefits** * **Enhanced Visibility:** Gain a clear understanding of your current FinOps practices and how they align with industry standards. * **Improved Efficiency:** Identify inefficiencies and optimize cloud spending based on actionable recommendations. * **Strategic Planning:** Develop a roadmap for advancing your FinOps maturity and aligning financial management with organizational goals. * **Informed Decision-Making:** Utilize insights and benchmarks to make data-driven decisions that enhance financial operations. ### Key Terms #### Lens(es) We use the concept of a Lens to talk about how you inspect and analyze a FinOps Practice. These lenses are essentially different functional inspection views through which to consider any given Framework Capability, each requiring different effort, and evidence to support. #### Domain FinOps Domains represents a sphere of activity or knowledge designed to achieve an outcome for the organization. #### Capability FinOps Capabilities represents functional areas of activity in support of their corresponding FinOps Domains. Each Capability includes definitions, key personas, performance metrics, and functional activities involved in a real FinOps practice. #### Framework An end-to-end structural view of the entire delivery model of a FinOps Practice, incorporating the Domains, Capabilities, lifecycle, maturity model, and principles of FinOps. #### Maturity A consistently applied measure of experience, breadth of ability, and success in the delivery of a specific element of the Framework. Maturity is not something to attain for the sake of being mature, but rather something one develops in response to the need to handle more complexity of cloud use or of organizational need when it produces value. #### Discovery Preamble questions that form the basis of understanding to build a clear picture of the maturity level being set in the assessment. #### Target Score Within this assessment process, we use the term “Target Score” to describe an intended goal for a particular FinOps practice. If there is a maximum assessment score of 20 within a capability (5 x lenses, each max score of 4) then how perfect do we realistically expect that capability to become at this stage in our journey? How important is that capability? Perhaps a score level of 12 out of 20 is “good enough” for our present roadmap – especially if it is a new muscle (capability) we are exercising. ### Lenses Used in Assessment The lenses provide insight into five key aspects of successfully performing each FinOps Capability. Each will help you identify potential strengths or areas for development in how you perform the Capability, and what steps you can focus on next. Understanding each of these lenses is key to effectively applying a consistent analysis, which is critical to compare your improvement over time by performing subsequent assessments. Each lens has five descriptive levels of performance, with examples of what would be expected at each level. Compare these descriptions to how you currently operate, and use the descriptions as a way to understand what more mature organizations need to do when their environments become complex. There is no need to be operating at higher levels in all cases. By reading the next higher level description, you can assess whether your organization would see value in that more advanced operating model. By understanding how you are operating from the perspective of each lens, it will be more clear where you might focus on improving your practices overall. #### Lens 1: Knowledge The KNOWLEDGE lens considers the breadth of understanding and awareness of this capability across the target group. When responding to this lens, consider how clearly this capability is communicated? How widely is this concept, it’s mechanisms terms and processes known? | Maturity | Heading | Description | | -------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0 | No Knowledge | At this level, knowledge of the capability as defined by the framework is effectively non-existent within the target group. There are no discussions happening about this capability, and nobody is actively involved in developing any further knowledge. | | 1 | Partial Knowledge | Preliminary knowledge of the Capability being assessed is now beginning to spread amongst key stakeholders and individuals, but the capability is not yet common knowledge across the target group. | | 2 | Developing Knowledge | Basic knowledge of the Capability is understood by a limited number of key stakeholders but information is limited in unscaled disbursements. | | 3 | Full Knowledge | Strong knowledge of the assessed capability is known throughout the target group, incorporated with starter onboarding and periodic reinforcement via training or other appropriate communication methods. | | 4 | Knowledge Leader | The target group is now driving awareness of this capability beyond itself to other peer groups and the wider industry. Leveraging deep awareness across individuals in the group, working to improve awareness and build new insights into the capability. | #### Lens 2: Process PROCESS relates to both the set of actions being performed in order to deliver the capability being assessed, and the artefact defining and documenting those actions. Consider the efficacy, validity and prevalence of such processes. | Maturity | Heading | Description | | -------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0 | No Process | There are no described, consistent processes in place governing any aspect of the assessed capability within the target group. | | 1 | Implementing Process | Processes to standardise this assessed capability are being formed, defined and possibly tested. Processes are not yet formalised as BAU for the target group. | | 2 | Developing POC Process | Relevant, functional processes are now in place, agreed upon and being followed by at least some of the teams. | | 3 | Scaled Process | Scaled processes are now in place, documented and you’ve implemented periodic feedback loops. | | 4 | Mature (Agile) Process | Clearly defined, transparent, and fully integrated processes are now universally established and consistent. This does not necessarily mean there is one process for each task but that processes in place are all in this state. Processes are being iterated on with key stakeholder feedback and ongoing agile refinement. | #### Lens 3: Metrics Is this capability measured? Is there a way to measure and prove progress over time? How are those measurements obtained, and how relevant are they? It is important to note that this lens does not measure how high any metric scores are, but how the measurements themselves are defined and used. | Maturity | Heading | Description | | -------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0 | No Metrics | There are no measurements being taken at this point. No direct insight is available concerning the progress or current state of this capability. | | 1 | Identified Metrics | Identified key metrics the business finds valuable for this capability to make trade-off decisions. | | 2 | Baselined Metrics | Initial, manually generated metrics are in place providing rudimentary traffic-light (eg: Red/Yellow/Green) measurement of this capability. | | 3 | Established & collecting Metric Targets data | KPIs are now in place covering at least some of this capability within the target group and cadence has been established for collection | | 4 | Mature, Global KPIs | S.M.A.R.T. KPIs are now globally in place, automated and refined/iterated on with a regular cadence. Direct links to business goals. Direct link to business performance. | #### Lens 4: Adoption Consider the knowledge, processes and metrics you are using to govern this capability being used by your target group. How widely has this capability been adopted and accepted by the target group as part of its integral and critical functions? Consider the prevalence and presence of this capability across the entire target group being assessed. | Maturity | Heading | Description | | -------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | 0 | No Adoption | The capability is not in place anywhere within the target group. | | 1 | Siloed Adoption | Elements of the capability are being adopted by a siloed group, lacking standardization and evidence best practices. | | 2 | Initial Standardized Adoption | Early elements of the capability are being standardized and vetted by a few individuals within the target group. | | 3 | Key Adoption | Fully established standardized elements of the capability as a part majority target groups BAU (Business As Usual) behaviors. | | 4 | Full Adoption | The capability now exists in totality across all elements of the target group, and is being actively engaged with and worked on. | #### Lens 5: Automation Why spend valuable time executing a repeatable task with predictable decision points and iterations? Automation drives consistency, speed and scalability across your target group. | Maturity | Heading | Description | | -------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 0 | No Automation | Virtually all of the required actions within the Capability are being executed manually at this stage. | | 1 | Identified Automation Opportunities | Starting to identify and map your automation requirements for a solution that will reduce labor and time toil. | | 2 | Experimental Automation | Early adoption of some key actions are beginning to be optimised through automated workflows and solutions. | | 3 | Primary Automation | Primary or most demanding actions have now been offloaded to automation solutions. | | 4 | Full Automation | All material, repeatable tasks within this capability are now automated, any new tasks are reviewed for automation potential or implemented as automation as the capability evolves | Reference: ## Assessment Flow
### How to Access FinOps Assessment Tool * **Logon** to your TechsaverFX instance * Click **Insights > FinOps Assessment**.
### New Assessment * Click **Insights > FinOps Assessment > New Assessment** * Enter Organization Name * Click **Next** * **Enter your current capability score (choose the predefined profiles provided for easy of use)** * Click **Next** * **Enter your Target Capability (choose the predefined profiles provided for easy of use)** * Click **Next** * Enter the FinOps Maturity Assessment Quentionares * Click **Complete Assessment** * **System will calculate the Maturity Score and provide automated Recommendation for Focus Areas** * Review the score by Clicking **"View" (you can review each capabilities individually on the Dashboard)** * Download the Report by clicking the **"download icon"** ***Note: Track your progress on the Dashboard. System is designed to evaluate and verify your scores for some of the capabilities(available in next release).*** ### **Gen AI Configuration** TechsaverFX uses GenAI LLM Llama 3 models which are trained to provide FinOps Maturity Recommendation. If you wish to change these configurations. Please contact CloudFX team. Model Configuration can be accessed * **Logon** to your TechsaverFX instance * Click **Settings > Control Panel > Config > AI Configuration**