On-Call Shadow Program

Shadow before solo.

Overview

An on-call shadow program pairs new operators with experienced ones for a defined window before solo. Reading runbooks teaches the steps; shadowing teaches the texture, the dead-ends, the cadence of a real bridge. Without a shadow window, new on-callers go solo when they pass an arbitrary threshold and discover the gap between runbook and reality during their first sev1.

• Shadow before solo. Per-operator explicit shadow window; the path is named, not "ask Slack when ready".
• Pair on real incidents. Per-incident the new operator pairs with a senior; learning happens on real bridges, not synthetic exercises.
• Shadow runbook checklist. Per-team checklist of incident classes the shadow has observed; readiness is measured against the checklist, not against time.
• Mentor pairing plus documented policy. Per-shadow the named mentor; per-team shadow rule committed to the team handbook for onboarding.

The approach

The practical approach is to pair the new operator with a named mentor, ground the shadow window in a checklist of incident classes the new operator must observe before solo, run the shadow on real incidents (not exercises), review progress weekly during the window, and document the per-team shadow rule so the practice survives leadership changes. The mentor is the shape of the program; the checklist is the readiness measure.

• Paired on incidents. Per-incident the new-operator pair with the mentor; the new operator sees the bridge from the seat next to the IC.
• Mentor driven. Per-shadow named mentor; the relationship anchors the learning.
• Checklist grounded. Per-team checklist of incident classes; readiness is incident-class coverage, not calendar time.
• Per-week review plus documented policy. Per-week shadow progress reviewed; per-team shadow rule committed to the handbook.

Why this compounds

Shadow program discipline compounds across hires. Each shadow week grows the new operator’s incident vocabulary; each mentor relationship preserves institutional knowledge that would otherwise leave with the senior; the team’s ability to onboard new on-callers becomes a strength rather than a continual cost.

• Operator readiness. Right shadow produces real confidence; the new operator goes solo with context, not just permission.
• Incident response. Per-operator shared context produces consistent response quality; the rotation does not have a strong-versus-weak operator gap.
• Operational hygiene. Per-week review keeps shadow progress on track; gaps surface before solo, not on the first sev1.
• Institutional knowledge. Each shadow teaches incident patterns the team reuses; the mentor relationship transfers tribal knowledge into shared knowledge.

Shadow program discipline is an operational discipline that pays off across years. Nova AI Ops integrates with on-call telemetry, surfaces readiness patterns, and supports the team’s onboarding discipline.