Building SRE Culture (without SREs, Technically)
summary
Shows a real failure: a red sign build 37.2 gets rolled out accidentally, the platform lacks rollback so players download 53 GB downloads twice, many lose savegames and content leaks spread via piracy. Compares that to a monthly fixed‑stop assembly‑line release at The Pokémon Company International that enforces downtime and director approvals but can’t scale. Offers concrete practices: build dashboards tied to business teams, use data‑backed storytelling, give the test team final say, escalate when needed, and operate with joy to win adoption.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:49Culture over process
- 6:18From reckless to overprotective
- 6:40Integrate SRE practices
- 8:07Data-backed stories
- 10:19Visibility and accountability
- 12:45Customer advocacy
related talks
22mBuilding SRE: Culture from the Outside In
32mBuild vs. Buy in the Midst of Armageddon
29mThe Curious SRE: Cultivating a Mindset for System Resilience
25mCapabilities for Building High-performing Technology Teams
41mBuilding an SRE Capability Inside a Large Organization
19mBuilding for Scale: How not to get Caught out at Global Launch
24mThe 7 Habits of Highly Effective Release Managers
40mBuilding Data Cultures