Observability maturity self-check
How close is your team to paradise?
16 habits across 5 areas, common in calm on-call rotations. Answer honestly and get a weighted score, your weakest area, and the three fastest wins. Share it as a link, an image, Markdown, or a PDF report. Nothing is stored on a server: your answers travel only inside what you share.
0/100
Answer honestly. Nobody's watching. (Well. We are observability people.)
0 of 16 answered
Your fastest wins
Share or save your result
Your answers travel only inside what you share. Nothing is stored on a server.
How the score works
Each habit is weighted by how much it matters for a calm on-call. "Yes" earns full weight, "Sort of" earns half, and "Not yet" earns nothing. The total is scaled to 100, and each area gets its own score, so a team that is strong everywhere except incident response can see it at a glance.
Fastest wins rank the gaps you reported by impact per unit of effort, from an afternoon's work to a project.
- Haunted
- 0+ · Your pager has a horror story in it. Start with one fast win below.
- Stormy
- 30+ · Some good habits, but the night shift still gets wet. Pick one gap and close it.
- Partly cloudy
- 55+ · The foundations are there. A few habits away from quiet nights.
- Golden hour
- 75+ · Most nights are calm. Close the last gaps and you are there.
- o11y paradise
- 90+ · Certified calm. Please share your story; the rest of us need it.
The five areas
Detect Know users are hurting before they tell you
Debug Get from symptom to cause quickly
Ship Change production safely
- Deploys go out as canaries that roll back on their own
- Deploys and config changes show up as markers on our graphs
- Alerts and dashboards live in git and get code review
Respond Handle incidents calmly
- Every alert that can page links to a short, tested runbook
- We alert on container restarts and memory pressure before users notice
- Incidents have a named lead, a comms channel, and regular status updates