Observability Fundamentals
SLOs teams can defend in planning
Draft error budgets, user-journey slices, and measurement windows that survive roadmap arguments and seasonal traffic.
- Format
- Cohort
- Duration
- 4 weeks, evening cohort
- Skill
- Intermediate
- Stack
- Prometheus recording rules
Tuition (informational): KRW 360,000
Request a syllabus conversation
SLO workshops often die in slide decks. Here you pair product and engineering voices using anonymized journey maps. You calculate budgets with transparent assumptions, document what happens when budgets burn, and practice saying no to low-impact feature work without sounding like a villain in standup notes.
What is included
- Journey mapping exercises with realistic seasonal curves
- Budget math spreadsheets peers can audit
- Role-play negotiations when a launch threatens burn
- Templates for alerting tied to budgets, not vanity graphs
- Guidance on revisiting windows without thrashing teams
- Short writing lab for SLO descriptions non-engineers parse
- Capstone defense to a skeptical pretend VP
Outcomes
- You publish an SLO set with explicit exclusions everyone signed.
- You tie at least one alert change to a budget state, not a gut feeling.
- You retire one metric that pretended to be an SLI but was not.
Instructor of record
Enterprise success manager who translates between procurement-ready roadmaps and engineering reality—here without operational shortcuts.
Noah Lee
Primary feedback on labs
Participant questions
Yes, we encourage pairs. Technical depth stays approachable with glossaries and async prep videos.
Recent voices
“VP capstone was awkward in the best way—we finally said out loud which journeys we were pretending to protect.”
“Would have liked one more async template for internal comms, but the live drills carried the value.”