{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"FinOps in Action","title":"Death by Dashboard: Why FinOps Needs Stories, Not More Charts ft. Gilad Katz, Riskified | Ep #47","html":"","width":"100%","height":180,"duration":2478,"description":"Is “death by dashboard” holding your FinOps program back more than you realize?In this episode of FinOps in Action, I sit down with Gilad Katz, FinOps Lead at Riskified, to explore why world-class FinOps isn’t about knowing every technical detail or pushing engineers to make changes; it’s about neutrality, trust, and telling the right story with data.Gilad describes the moment he realized that trying to “know everything” in cloud infrastructure was slowing him down and why the real turning point in his career happened when he shifted from feeling pressure to recommend solutions to embracing his role as the person who brings clarity, context, and facts. As he puts it, “I’m not a recommendation guy, I’m a data guy.” That mindset reshaped the way he collaborates with engineering and finance, and why the most important part of FinOps work is often diplomacy, not technical expertise.We also talk about what happens when cloud costs spike, why looking backward slows teams down, and how practicing FinOps “with a smile” builds long-term credibility. Gilad pulls back the curtain on how Riskified manages monthly business reviews, how he keeps engineers engaged without blame, and why empathy and composure often matter more than technical mastery.Here’s what we talked about:Why trying to “learn everything” in cloud infrastructure actually slows FinOps practitioners downWhat it means to act as the “UN” between Finance and Engineering, and why neutrality drives influenceWhy reporting to the COO removes bias and prevents CTO–CFO misalignment from derailing cost decisionsWhat “death by dashboard” looks like and why FinOps needs stories, summaries, and context, not dozens of charts Why looking forward matters more than looking backward when costs spike, and how to avoid blame cyclesHow to communicate cloud costs in a way that reduces tension and increases cooperationWhy FinOps is a marathon of relationship-building, not a sprint of optimizations 🎧 Subscribe for more FinOps...","thumbnail_url":"https://img.transistorcdn.com/19z3-eWZl6c0TEQCJZvYXIgN4CxYIhl9_e56I_mkpWs/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wYTdj/YWRhNmM4YzM4NzQ0/NDVlNzFhYmE2NmVi/Y2ZiZC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}