THANK YOU FOR SUBSCRIBING
Be first to read the latest tech news, Industry Leader's Insights, and CIO interviews of medium and large enterprises exclusively from CFO Tech Outlook
THANK YOU FOR SUBSCRIBING
By
CFO Tech Outlook | Monday, July 07, 2025
Stay ahead of the industry with exclusive feature stories on the top companies, expert insights and the latest news delivered straight to your inbox. Subscribe today.
FREMONT, CA: Recently, cloud usage has risen as businesses shift from traditional on-premises hosting to public cloud solutions. However, hybrid and multi-cloud patterns have posed issues in optimizing value and regulating cloud expenditure, resulting in a shift from capital to operational costs. FinOps is a growing cloud financial management discipline and cultural practice aimed at increasing company value in hybrid and multi-cloud systems. However, with a good understanding, implementing FinOps can be easier. Organizations must establish a clear course and avoid typical pitfalls to leverage the benefits and achieve the promise of FinOps.
Significant challenges and common mistakes when implementing FinOps are:
Organizations should establish a phased approach over time rather than attempting to incorporate everything from the start. Having the right people, processes, and technology in place is crucial for validating changes and understanding their impact on the consumption model and user experience.
Creating a clear journey path is necessary to identify the present state, determine the future state, and develop a transition plan from the current state to the future state with a clear execution approach. Well-defined design principles must be established and adopted consistently to ensure repeatability across several organizations or business units within the organization. Monitoring key performance indicators (KPIs) is necessary for tracking progress successfully.
Many organizations are already considering FinOps initiatives, although not in the most cost-effective way. Rather than addressing the underlying causes, they implement temporary fixes that lead to continuous problems. These temporary fixes include:
Architecture patterns: Regular modifications to architectural patterns based on new features and native services from hyperscalers may increase complexity without clear success indicators.
Periodic reviews: IT teams meet on a regular basis to resolve performance issues caused by size or overspending, usually in response to complaints from finance departments. However, this reactive strategy reinforces firefighting rather than proactive self-optimization.
External SMEs: Bringing in external subject matter experts for reviews is expensive, and it takes time to train them. This method results in ongoing expenses without long-term improvements.
It is crucial to develop clear KPIs, benchmarks, and processes for real-time insights and measurable results to prevent these errors. Some companies delegate FinOps responsibilities to a centralized team in charge of monitoring spending and selecting cloud services. This method can create silos and prevent visibility into planned changes, resulting in unhappiness and negative consequences for service performance. Federating FinOps activities across the organization promote greater participation and a diversified set of capabilities while also encouraging collaboration and preventing silos.
I agree We use cookies on this website to enhance your user experience. By clicking any link on this page you are giving your consent for us to set cookies. More info