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?