Challenges in FinOps: Overcoming Common Roadblocks on the FinOps Journey
Every transformation faces resistance.
This post highlights common challenges in adopting FinOps—from cultural pushback to tooling overload—and offers practical strategies to overcome them. Learn how to build buy-in, simplify processes, and keep your FinOps initiative moving forward.
Common Challenges and How to Overcome Them
Adopting FinOps isn’t without its hurdles. Understanding common challenges can help you address them proactively and ensure your FinOps journey succeeds. Here are some frequent issues and ways to tackle them:
Uncontrolled Cloud Spending
When teams independently spin up resources, costs can spiral unchecked.
Solution: Implement central cost governance (a FinOps team and tagging policies) to enforce accountability and optimise purchasing (e.g. through bulk discounts and reservations).
Siloed Teams & Goals
Engineering focuses on performance, finance on budget – and they only connect when a huge bill arrives.
Solution: Foster cross-functional collaboration via FinOps culture so that teams share goals and communicate continuously. Regular cost review meetings with both tech and finance present can break down silos.
Lack of Cost Visibility
Without real-time, granular cost data, waste (like idle resources) stays hidden until it’s too late.
Solution: Use real-time dashboards and alerts for cloud spend, making cost data accessible and timely for all stakeholders. Establish a practice of showback (everyone can see their cloud spend) or chargeback to drive accountability.
Misused Pricing Options
Organizations sometimes overcommit to reserved capacity or discount plans that they don’t fully utilize.
Solution: Educate teams on cloud pricing models and analyze usage patterns before committing. Align commitments (like reserved instances or savings plans) with actual needs and review them regularly. Take full advantage of the cloud’s variable cost model – scale up or down as needed instead of paying for capacity you won’t use.
cultural resistance and tooling overload
Other challenges can include cultural resistance (people might be set in their ways or fear that FinOps will add bureaucracy) and tooling overload (getting lost in too many dashboards). The remedies usually come back to the FinOps principles: collaboration, education, and iteration.
For cultural pushback, start with small wins and celebrate them – show that FinOps helps engineers rather than hinders them (e.g. “thanks to FinOps, we saved money that we can now invest in that cool project”). Make cost optimization a positive, team-achievement thing, not a punishment. For tools, keep it simple – it’s better to have a few well-understood metrics than dozens of reports no one reads
leadership support
Leadership support is crucial. When executives, from the CIO to CFO, vocally support FinOps and ask about cloud efficiency in meetings, it sends the message that this is a priority. That backing helps overcome reluctance at lower levels. Conversely, if leadership is disengaged, FinOps often stalls. So part of the FinOps lead’s job is evangelism upward as well as downward.
Conclusion
Remember that no organization is alone in this – the FinOps community is growing, and many others have faced the same challenges. Learning from peers (through the FinOps Foundation, conferences, forums, etc.) can provide ideas on how to tackle obstacles like the ones above.
Recent Posts:
Measuring FinOps Success: KPIs That Prove Value and Drive Improvement
Challenges in FinOps: Overcoming Common Roadblocks on the FinOps Journey
