This recap includes the following episodes and guests.
Guest title reflects the guest's position at the time of the episode.
Recipes:
Understanding Scope 1, 2, and 3 Emissions
Use Data-Driven Infrastructure Insights
Leverage AI for Infrastructure Efficiency
Act on What You Measure
Art of Automation
Season with Diverse Perspectives
Executive Recipe: Turning Sustainability Ambition into Action
🎯 Goal: Use data to drive sustainability across the supply chain.
Mike Hollinger broke down the three scopes of emissions and explained how data plays a critical role in managing them:
The takeaway? Organizations need to orchestrate and normalize data across systems to understand their full environmental impact—and act on it. Scope 3, in particular, requires collaboration, transparency, and smart data integration to uncover hidden emissions and drive meaningful change.
🥄 Practical Tips:
Inventory your data sources across IT and OT systems.
Use carbon accounting tools to visualize and analyze emissions.
Prioritize Scope 3 visibility by collaborating with suppliers and partners.
Scope 1: Direct emissions from owned or controlled sources.
“You measure that by your power draw, by the things you make.”
Scope 2: Indirect emissions from the generation of purchased energy.
“You ask your suppliers and do the math—how much carbon did they put in the world?”
Scope 3: All other indirect emissions in the value chain, including those from suppliers’ suppliers, product use, and disposal.
“Scope 3 is the tough one—it’s about understanding the full story across your supply chain, and that’s a data orchestration challenge.”
🎯 Goal: Optimize physical and cloud systems through measurement.
In our conversations, Mike Hollinger emphasized the power of data as the foundation for sustainable infrastructure. He said, “We have this data, we have the ability to drive insights.” That’s the first ingredient in our recipe—knowing what you have before deciding what to cook. Jerry Cuomo added, “In the precious data logs of SREs lies answers.” It’s not just about collecting metrics; it’s about surfacing the right ones with context.
🥄 Practical Tips:
Start with a clear question before building a dashboard.
Bridge IT and OT data sources to get a full picture.
Use consumption metrics alongside service-level indicators to guide decisions.
🎯 Goal: Apply predictive analytics for capacity and energy usage.
AI is the sous-chef in our infrastructure kitchen. Jerry reminded us, “Striving for autopilot brings amazing things.” But it’s not about handing over control—it’s about augmenting human judgment. Kevin (me!) shared how tools like Instana are changing the game: “I can pick a golden signal and apply it across all systems in seconds.” That’s automation with purpose.
🥄 Practical Tips:
Use AI to detect anomalies and surface risks before they escalate.
Right-size environments by analyzing actual consumption patterns.
Choose smaller, task-tuned models to reduce energy and cost.
🎯 Goal: Drive real-world change from digital insights.
Mike’s story about the Sund & Baelt bridge was a standout. “The fusing of visual data with sensor data… lets the team choose where to invest.” That’s what intelligent infrastructure looks like—data that leads to action. I added, “Why don’t we surface that context in the first place?” Let’s stop making engineers dig through dashboards and start giving them answers.
🥄 Practical Tips:
Design alerts to be actionable—either by people or automation.
Use historical data to prioritize maintenance and reduce waste.
Build feedback loops that connect insights to real-world outcomes.
🎯 Goal: Eliminate toil and scale reliability with smart systems.
Automation isn’t just about scripts—it’s about intentional design. Jerry said it best: “AI eats data for breakfast.” But it needs the right recipe. Mike challenged us to think differently: “How can I do a computation once?” That’s the kind of thinking that leads to sustainable systems. And yes, we joked about omelettes, but the point stands—automate what’s repetitive, but always with context.
🥄 Practical Tips:
Identify high-toil tasks and automate them with AI-assisted workflows.
Use historical failure patterns to guide automation triggers.
Don’t automate blindly—always validate with service-level outcomes.
🎯 Goal: Challenge assumptions and enrich infrastructure decisions.
Innovation thrives on diversity. Mike shared, “If we can’t answer why we’re doing it this way, it’s a trigger for change.” That’s the kind of question that leads to better systems. Jerry added, “Technology gives us back the greatest gift—time.” But only if we design it with intention and inclusivity.
🥄 Practical Tips:
Invite cross-functional teams into infrastructure conversations.
Use ESG frameworks to guide sustainable design choices.
Encourage questioning of legacy practices—especially from new voices.
🎯 Goal: Guide leadership teams to operationalize sustainability through data, insight, and action.
In our conversation, Mike laid out a clear and practical framework for C-suite leaders looking to move from sustainability ambition to measurable outcomes. His advice was grounded in real-world experience and focused on data as the starting point.
“The first thing is understanding what data you have… you might be surprised at what you’re already paying for.”
“Once you know what you have, ask what you need—and what gaps you must fill to take action.”
Jerry reinforced this with a call to embrace AI as a productivity tool, not a replacement for human insight:
“Become a prompt engineer. It doesn’t require a degree—just curiosity and repetition.”
“Go shopping for the smallest possible model that’s documented and fine-tune it for your tasks.”
Together, their insights form a practical 4-step recipe for executives:
Audit existing systems across IT and OT.
Identify silos from M&A, legacy systems, or departmental divides.
Understand what telemetry, usage, and environmental data is already available.
Ask: What decisions do we want to make?
Determine what data is missing to support those decisions.
Consider inferencing models where direct measurement isn’t possible (e.g., cement production).
Use dashboards not just for visibility, but to drive action.
Connect insights to operational systems—whether it’s rolling a truck, reallocating VMs, or shutting down idle equipment.
Ensure every insight has a path to execution.
Encourage teams to experiment with prompt engineering.
Collaborate with data scientists to fine-tune models for specific use cases.
Focus on augmentation—AI that assists, not replaces.
Mike summed it up perfectly:
“If I have a dashboard and take no action from it, what good is it?”
And Jerry added:
“Spend more time on things your users appreciate—nothing’s better than working on a product people love.”
This recipe isn’t just for sustainability—it’s for building smarter, more resilient organizations.
What’s one automation you’ve implemented that didn’t deliver the expected value—and why?
How do you decide which metrics are worth acting on versus just monitoring?
What’s your process for validating that an AI model is truly helping your infrastructure goals?