FinOps continues to grow in importance as organizations balance cloud services with on-prem systems, legacy applications, and evolving business demands. Many teams want to manage their costs more effectively but are unsure how to apply a FinOps strategy for hybrid IT outside the cloud.
In a new interview, Galileo Creator and Principal at ATS Group, Tim Conley, shares his perspective on where teams get stuck, what information they often overlook, and how hybrid environments can benefit from better data and stronger operational visibility. As Tim notes early in the conversation, “data doesn’t lie,” and that idea frames much of what follows.
This blog highlights several themes inspired by the interview and expands on them with additional context around FinOps strategy for hybrid IT. If you want a practical, experience-based look at strengthening your FinOps approach, the conversation is a great place to begin.
Watch the Full Interview with Tim Conley
The most meaningful takeaways come through in the conversation itself. To hear these insights directly from Tim and see how he and the Galileo team approach FinOps in real environments, you can watch the full interview here.
Why FinOps Needs a Broader View in Hybrid IT
FinOps began as a cloud-focused discipline centered on usage, billing, and optimization. Many organizations still think about FinOps this way and rarely extend the practice into physical infrastructure, storage systems, virtualization platforms, or distributed applications.
The result is a partial picture that limits the impact of the discipline and often prevents teams from building a complete FinOps strategy for hybrid IT.
A modern FinOps approach requires an understanding of how all parts of the environment contribute to cost and performance. This includes cloud resources, private data center assets, shared infrastructure, and any system that supports the delivery of a business service.
Visibility matters, but visibility alone is not enough. A strong FinOps practice connects spending to business outcomes and uses performance intelligence to guide decisions. This shift aligns with industry direction as the FinOps Foundation continues to broaden its guidance to include hybrid and on-premises infrastructure.
For a deeper look at why cloud-only approaches fall short, our previous post on hybrid FinOps provides additional context.
Understanding the FinOps Themes Behind the Conversation
1. Cost visibility is not the same as cost understanding
Teams often assemble cost dashboards or monthly reports and assume they have completed the first phase of FinOps. While these steps are helpful, they do not explain why resources behave the way they do or how performance influences cost. For example, a workload may appear expensive, but cost may be driven by poor configuration, inefficient data placement, or a performance issue deeper in the stack.
FinOps becomes effective only when teams bring together cost data, performance telemetry, and usage patterns. When these three elements align, leaders gain a complete view of value and can make informed choices about scaling, optimizing, or redesigning services.
2. Ownership is one of the most challenging aspects of FinOps
Modern environments involve many stakeholders. Storage teams, virtualization teams, cloud teams, database administrators, application owners, and finance all play a role. FinOps often stalls when no one is responsible for guiding cost-related decisions. Without clear ownership, optimization becomes episodic and inconsistent.
Successful FinOps organizations create a model where each category of cost has an accountable owner. These owners understand the operational context behind the numbers and can take action. When responsibility is shared among engineering, operations, and finance, decisions become faster and more precise.
3. FinOps must function as a continuous process
Hybrid IT environments evolve constantly. New workloads appear. Others are retired. Performance needs shift as business patterns change. Once-a-year or once-a-quarter review is not enough to sustain value. FinOps should follow an ongoing rhythm that includes monitoring, review, adjustment, and communication.
With regular evaluation, teams can identify trends early, avoid reactive spending, and plan infrastructure growth based on real demand. A continuous practice helps organizations avoid surprises and remain confident in their decisions.
4. Correlated data is essential for meaningful action
A recurring theme in the conversation is the need to correlate information. For example, rising costs may not be a spending problem but a performance constraint that pushes workloads to consume more resources. Without correlated data across performance, usage, and cost, teams are left guessing. This level of insight is also emphasized in FinOps working groups in the broader community.
Uniting all data in a single, consistent view allows teams to identify the source of problems, understand true business impact, and reduce unnecessary effort across departments.
Building a Stronger FinOps Strategy
The interview highlights several areas where organizations can improve. The following guidance expands on those ideas with practical next steps:
- Create a full inventory of your hybrid estate, including cloud, on-prem systems, and shared infrastructure.
- Identify your major cost drivers and map them to the business services they support.
- Integrate cost, performance, and usage information into one consistent view so teams can understand the relationship between them.
- Establish clear ownership for each domain and define responsibilities for decision-making.
- Add automation for reporting, resource adjustments, and routine checks where possible.
- Adopt a predictable evaluation rhythm, so FinOps becomes part of daily operations, not an occasional review.
The goal is not to reduce spending at all costs. The goal is to understand what the organization is paying for, why behavior looks the way it does, and how those choices influence the services the business relies on. These steps create the foundation for a reliable FinOps strategy for hybrid IT that is rooted in real operational behavior.
How Galileo Supports Hybrid FinOps
Galileo is designed for hybrid environments where cloud-only tools fall short. By capturing detailed performance telemetry across servers, storage, virtualization, and cloud resources, Galileo provides the context needed to make informed FinOps decisions. The platform correlates cost drivers with performance behavior so teams can understand not only what they spend but why consumption looks the way it does.
This level of visibility helps organizations move from reactive decision-making to a more proactive, value-focused FinOps discipline.
Strengthen Your FinOps Practice with Better Data
A mature FinOps practice helps IT leaders plan with confidence, understand true resource behavior, and align infrastructure decisions with the outcomes the business expects. If you want to take a closer look at how unified visibility and correlated data can support your FinOps goals, our team can help you evaluate what is happening across your hybrid environment.
We can walk you through workload behavior, cost drivers, and opportunities for performance and efficiency improvements.
When you are ready, you can schedule a conversation or request a guided demo to see what this would look like in your environment.
