green plant


SRE: It's not about numbers–it's about customer satisfaction

Part of the For Cloud Professionals podcast series

When most people think about SRE, they think numbers, percentages, SLIs, and SLOs. That stew of acronyms is important, but, really, what drives site reliability engineering is the goal of building systems that truly satisfy customers and keep them coming back.

Listen and subscribe to Deloitte On Cloud podcast:

Listen on Apple Podcast Listen on Google Podcast Listen on Spotify Listen on Stitcher Listen on Souncloud Listen on Pandora

SRE: The goal is to build reliable systems that customers love

Most organizations have implemented some version of site reliability engineering (SRE) to help them understand system performance and develop more reliable systems. However, SRE isn’t just about managing to a number or a percentage. Instead, it’s about defining “reliability” in terms of customer satisfaction and letting data drive decisions. In this episode of the podcast, Mike Kavis and guest, Google’s Nathen Harvey, discuss how organizations can do SRE better. Nathen’s perspective is that SRE is organic to each organization and that, in addition to error budgets, SLIs, and SLOs, SRE is really about leadership. Leaders set the tone and help ensure that SRE is implemented in an inclusive manner that stresses teamwork, fosters communication, and delivers reliable systems customers love.

Disclaimer: As referenced in this podcast, “Amazon” refers to AWS (Amazon Web Services) and “Google” refers to GCP (Google Cloud Platform).

We have to take a customer–or user-centric point of view of our systems.Nathen Harvey, cloud developer advocate at Google, helps the community understand and apply DevOps and SRE practices in the cloud. He is part of the DevOpsDays conferences global organizing committee and was a technical reviewer for the 2019 Accelerate State of DevOps Report.

Back to top

How can SRE help organizations achieve better and fast results?

Site Reliability Engineering (SRE) offers many benefits, but to implement SRE well it's critical to harness the full value of human capital and DevOps team to build more effective systems.

Back to top

golden circles

Chaos engineering: Stress-testing the cloud

It's nearly impossible to predict and prevent cloud failures. Chaos engineering aims to discover cloud failure points, in in-production systems, before they become disasters.

Back to top

circle electrical waves

Put Cloud in context with the future of business and technology

Because cloud is never just about cloud, a podcast about cloud isn’t either. Our two hosts deliver two unique perspectives to help bring you closer to achieving what matters most—your possible.

For Cloud Professionals, hosted by David Linthicum, provides an enterprise-level, strategic look at key issues impacting clients’ businesses. David, ranked as the #1 cloud influencer in a recent Apollo Research report, has published 13 books on computing, written over 5,000 published articles and performed over 500 conference presentations, making his specialization in the power of cloud simply undeniable.

As a pioneer in cloud computing, Mike Kavis leads Architecting the Cloud, which offers insights from the POV of those who’ve had hands-on experience with cloud technology. Mike’s personal cloud journey includes leading the team that built the world's first high-speed transaction network in Amazon's public cloud—a project that ultimately won the 2010 AWS Global Startup Challenge.

With two leaders in your ear, you’ll have the content you need to drive the next conversation around cloud. Check out both talk tracks within the Deloitte On Cloud podcast to get the compelling stories on your schedule to help you understand the topics that are reshaping today’s market.

Contact us at for information on this or any other On Cloud podcasts.

Or visit the On Cloud library for the full collection of episodes.

Subscribe now on: iTunes | SoundCloud | Stitcher | Google Play | Spotify

Previous episode