How to Set Up Effective SRE Service Level Objectives (SLOs)
Designed for Site Reliability Engineers and DevOps leads at mid-sized SaaS companies who have inherited legacy systems without structured SLOs and are responsible for defining measurable reliability targets for service teams. to spark real collaboration and high-energy learning.
A 90-minute interactive hybrid workshop set in a modern conference room with remote dial-in options. Attendees are frustrated by vague reliability goals and lack of actionable benchmarks, leading to firefighting and unclear priorities. They need practical guidance and peer support to shift from reactive to proactive SRE practices.
Mystery Metric Reveal
Kick off with a live poll showing three anonymized system dashboards (uptime %, error rate, latency spikes) and ask attendees which metric is most valuable for defining an SLO. After votes, reveal which one was actually used to drive customer satisfaction in a real SaaS outage case and why.
Tap to view the full activity.
Why this works
Curiosity draws participants in and primes them to question their assumptions. Real examples signal relevance and set the stage for deeper learning.
SLO Mythbusters
Present three common SLO myths, such as 'SLOs should always match SLAs' or 'Setting 99.999% is ideal.' Ask participants to vote 'True' or 'False' via colored cards (in-person) or chat emojis (virtual). Facilitator then debunks each myth with a concise, evidence-based explanation.
Tap to view the full activity.
Why this works
Confronting misconceptions early clears cognitive clutter and opens minds to new frameworks. Voting involves everyone without pressure.
Quick SLI Match Game
Hand out (virtual or physical) cards listing typical system events ('HTTP 500 error', 'slow API response', 'database timeout'), and ask participants to quietly match each to SLI, SLO, or SLA. No wrong answers — this is a warm-up. Reveal correct matches and clarify definitions.
Tap to view the full activity.
Why this works
Low-pressure sorting builds confidence and reinforces terminology. Quiet participation ensures everyone has a baseline before deeper activities.
SLO Lightning Draft
Split the room into small groups, each assigned a mock service (e.g., payments API, login portal). Give them 4 minutes to draft one SLO using a template (‘X% of requests complete in under Y ms’), then have teams race to share theirs. Encourage ‘creative outliers’ for bonus points.
Tap to view the full activity.
Why this works
Short deadlines and friendly competition spark energy and engagement. Group work pushes teams to apply concepts quickly, deepening memory.
Stakeholder Dilemma Hot Seat
Role-play: Assign one participant as ‘Product Manager’ and another as ‘SRE Lead’. Present a scenario: the PM pushes for tighter SLOs (99.99% uptime), but SRE warns of increased costs and diminished returns. Each gets 60 seconds to argue their case. Group votes on which perspective wins, and facilitator unpacks the business and technical implications.
Tap to view the full activity.
Why this works
Role-play exposes real-world trade-offs and builds empathy. Seeing both sides encourages nuanced thinking and better SLO design.
Personal SLO Storyboard
End session with each participant sketching (on paper or virtual whiteboard) a personal ‘SLO storyboard’: one reliability goal they wish their team had, why it matters, and how it would change their daily work. Share in pairs and gather 2-3 highlights for group discussion.
Tap to view the full activity.
Why this works
Active reflection bridges learning to personal context, increasing retention and ownership. Sharing stories deepens trust and relevance.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.