Artwork

Managing Commitments, Anomalies & Regulations in FinOps ft. Gordon Douglass, SAP NS2 | Ep 37

FinOps in Action

published

Play Playing
iconShare
 
MP3•Episode home
Manage episode 509973146 series 3638213
Content provided by Alon Arvatz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Alon Arvatz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://staging.podcastplayer.com/legal.

What does FinOps look like in highly regulated industries — and why is speed so critical when managing commitments and anomalies?

In this episode of FinOps in Action, I sat down with Gordon Douglass, VP of Cloud Assets & Risk Management at SAP NS2, to talk about the real-world challenges of running FinOps in government and enterprise-scale environments.

Gordon shares why commitments are one of the scariest parts of FinOps, how to balance anomaly detection with meaningful action, and what it means to wear “many hats” as a FinOps leader. He also explains how regulations, procurement, and engineering collaboration add layers of complexity — and how to navigate them successfully.

Here’s what we talked about:

  • Why commitments can make or break FinOps strategy

  • How to balance speed and accuracy in anomaly detection

  • What FinOps looks like in regulated industries like government cloud

  • The “many hats” of a FinOps practitioner and leader

  • Lessons from SAP NS2’s approach to cloud cost management

🎧 Subscribe for more FinOps leadership conversations → https://www.finopsinaction.com/

Quote of the Show:

"We have regular cadences both internally within my group itself in addition to that also with engineering and operations, just to see and make sure that they understand or can justify what's going on. " - Gordon Douglass

Links:

Ways to Tune In:

…   continue reading

40 episodes

#Business #Arvatz #FinOps