Panel: Oncall
summary
Panel discussion shows concrete practices: mandatory shadow and reverse-shadow onboarding, automated paging into rotations, tracking metrics like first-touch resolution, page-to-outage ratio and escalation counts, weekly short-term and quarterly trend reviews, and subjective “happy/sad” on-call checks. Teams build automation to capture bridge join times and reduce manual recording, apply load shedding by handing chronic pagers back to developers, enforce four‑hour turnovers, and use an incident command system for role-based handoffs; these measures reduce repeats and burnout.
AI-written summary · about