Skip to main content

Effective FinOps: Moving from Recommendations to Risks

Eric Ethridge
DoiT

FinOps champions crucial cross-departmental collaboration, uniting business, finance, technology and engineering leaders to demystify cloud expenses. Yet, too often, critical cost issues are softened into mere "recommendations" or "insights" — easy to ignore. But what if we adopted security's battle-tested strategy and reframed these as the urgent risks they truly are, demanding immediate action?

This shift isn't just about semantics; it's about survival. Unchecked cloud costs aren't minor annoyances; they're financial liabilities that can shatter a company's foundation. Startups can incinerate their monthly runway in a single day. For mid-market firms, unanticipated or overlooked cloud expenses can obliterate profitability in an instant. This financial bleed doesn't just erode profit; it undermines operational performance and even security.

FinOps teams must treat these financial risks with the same gravity as security threats. Security doesn't offer vague suggestions; it pinpoints specific risks, assigns severity levels and tracks vital metrics like mean time to resolution. By mirroring this approach, FinOps can evolve from passive optimization to a proactive financial defense system that tackles risks head-on. This transforms cloud cost management from an "if time allows" chore into the non-negotiable, timely imperative it must be.

Risks and Responsibilities

Changing the conversation from soft "recommendations" to hard "risks" ignites urgency and breeds accountability. Suddenly, teams aren't just trying to save a buck; they're active guardians of financial stability. Engineers attack cost issues with the same tenacity they apply to critical bugs, and finance teams are right there, collaborating every step of the way.

What do executives get?

Real outcomes measured by clear metrics, not just vague "what-ifs."

FinOps teams must adopt this aggressive mindset and equip themselves with the right tech. A solution's purpose isn't to churn out endless suggestions. It's to sharply identify cost risks, make them actionable and then track how quickly and effectively they're neutralized. This isn't about mere budget tweaking; it's about forging a culture where innovation flourishes alongside strong financial controls.

FinOps: A Force Multiplier for Security

This re-envisioned FinOps isn't just about money; it's a significant boost for security:

  • Shrinking the Attack Surface: FinOps excels at spotting overprovisioned or idle cloud resources. This isn't just cost savings; it's also a direct way to reduce potential targets for attackers and close security holes.
  • Hardwiring Accountability: The core of FinOps is accountability, a principle critical for security. When resources have clear owners, enforcing security policies becomes straightforward. Data breaches can be traced back to unauthorized usage, and better-managed environments drastically cut down on misconfigurations that create vulnerabilities.
  • Building a Security-First Culture: When cost accountability is deeply ingrained, employees at all levels are far more likely to stick to security best practices and proven configurations, knowing they're directly responsible.

Today's tools are powerful allies. The right cost and security monitoring platforms allow for side-by-side evaluation of critical data. Resource tags can simultaneously track both financial and security risks. Budget alerts can even flag potential security breaches by detecting unusual cost spikes caused by malicious activity. And automation can seamlessly integrate FinOps, consistently applying governance across financial and security landscapes.

A Better Picture

The current FinOps approach is falling short for far too many organizations. The deluge of "recommendations" isn't delivering. A radical reframing is desperately needed, one that starts by calling cost issues exactly what they are: actual risks, demanding swift urgency and clear accountability.

True success won't be found in the sheer number of suggestions, but in the critical issues unearthed and definitively resolved — and the speed and thoroughness with which that resolution occurs. This transformative approach doesn't just fix financial leaks; it shatters siloed decision-making, forcing crucial conversations where cost and security are always considered hand-in-hand, painting a far more complete and actionable picture.

Eric Ethridge is Senior Technical Account Manager at DoiT

Hot Topics

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Effective FinOps: Moving from Recommendations to Risks

Eric Ethridge
DoiT

FinOps champions crucial cross-departmental collaboration, uniting business, finance, technology and engineering leaders to demystify cloud expenses. Yet, too often, critical cost issues are softened into mere "recommendations" or "insights" — easy to ignore. But what if we adopted security's battle-tested strategy and reframed these as the urgent risks they truly are, demanding immediate action?

This shift isn't just about semantics; it's about survival. Unchecked cloud costs aren't minor annoyances; they're financial liabilities that can shatter a company's foundation. Startups can incinerate their monthly runway in a single day. For mid-market firms, unanticipated or overlooked cloud expenses can obliterate profitability in an instant. This financial bleed doesn't just erode profit; it undermines operational performance and even security.

FinOps teams must treat these financial risks with the same gravity as security threats. Security doesn't offer vague suggestions; it pinpoints specific risks, assigns severity levels and tracks vital metrics like mean time to resolution. By mirroring this approach, FinOps can evolve from passive optimization to a proactive financial defense system that tackles risks head-on. This transforms cloud cost management from an "if time allows" chore into the non-negotiable, timely imperative it must be.

Risks and Responsibilities

Changing the conversation from soft "recommendations" to hard "risks" ignites urgency and breeds accountability. Suddenly, teams aren't just trying to save a buck; they're active guardians of financial stability. Engineers attack cost issues with the same tenacity they apply to critical bugs, and finance teams are right there, collaborating every step of the way.

What do executives get?

Real outcomes measured by clear metrics, not just vague "what-ifs."

FinOps teams must adopt this aggressive mindset and equip themselves with the right tech. A solution's purpose isn't to churn out endless suggestions. It's to sharply identify cost risks, make them actionable and then track how quickly and effectively they're neutralized. This isn't about mere budget tweaking; it's about forging a culture where innovation flourishes alongside strong financial controls.

FinOps: A Force Multiplier for Security

This re-envisioned FinOps isn't just about money; it's a significant boost for security:

  • Shrinking the Attack Surface: FinOps excels at spotting overprovisioned or idle cloud resources. This isn't just cost savings; it's also a direct way to reduce potential targets for attackers and close security holes.
  • Hardwiring Accountability: The core of FinOps is accountability, a principle critical for security. When resources have clear owners, enforcing security policies becomes straightforward. Data breaches can be traced back to unauthorized usage, and better-managed environments drastically cut down on misconfigurations that create vulnerabilities.
  • Building a Security-First Culture: When cost accountability is deeply ingrained, employees at all levels are far more likely to stick to security best practices and proven configurations, knowing they're directly responsible.

Today's tools are powerful allies. The right cost and security monitoring platforms allow for side-by-side evaluation of critical data. Resource tags can simultaneously track both financial and security risks. Budget alerts can even flag potential security breaches by detecting unusual cost spikes caused by malicious activity. And automation can seamlessly integrate FinOps, consistently applying governance across financial and security landscapes.

A Better Picture

The current FinOps approach is falling short for far too many organizations. The deluge of "recommendations" isn't delivering. A radical reframing is desperately needed, one that starts by calling cost issues exactly what they are: actual risks, demanding swift urgency and clear accountability.

True success won't be found in the sheer number of suggestions, but in the critical issues unearthed and definitively resolved — and the speed and thoroughness with which that resolution occurs. This transformative approach doesn't just fix financial leaks; it shatters siloed decision-making, forcing crucial conversations where cost and security are always considered hand-in-hand, painting a far more complete and actionable picture.

Eric Ethridge is Senior Technical Account Manager at DoiT

Hot Topics

The Latest

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...

Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...