Overcoming SRE Anti-Pattern Roadblocks: Rebranding the Ops Team
summary
At FanDuel (Flutter/Blip) an SRE team retools incident management, observability and SLOs instead of just renaming ops: they own a SaaS observability stack, build Terraform modules to automated SLO creation, standardize metrics and dashboards across dozens of services, and map critical business flows (example: bet placement) to business-flow SLOs. They prioritize work with Pareto/Eisenhower, run on-call and postmortems, and report measurable improvements in incident clarity though full coverage remains a work in progress.
AI-written summary · about
chapters (14)
- 0:00Introduction to SRE anti-patterns
- 1:04Evolution of SRE and its principles
- 4:38SRE adoption and challenges
- 6:01Understanding anti-patterns
- 8:25Rebranding ops team as SRE
- 9:28Why rebranding fails as an anti-pattern
- 10:53Solutions to avoid anti-patterns
- 14:47Practical SRE approach at FanDuel
- 21:06More SRE anti-patterns to avoid
- 22:32Summary and key takeaways
- 23:15Q&A: SRE hero anti-pattern
- 25:00Q&A: Automating SLO creation
- 26:27Q&A: SRE vs operations differences
- 27:51Q&A: AI and reliability frameworks
related talks
25mSRE Guiding Principles & Transformational Framework
24mBeing Reasonable about SRE
45m“Disorganizing” Your SRE Organization
13mWhat To Do When SRE is Just a New Job Title?
38m"Disorganizing" Your SRE Organization
19mCrafting an SRE Roadmap for Enterprise Success
42mDemystifying SRE and DevOps
45mClearing the Way for SRE in the Enterprise