On-Call Experience Sharing
Share war stories.
Overview
On-call experience sharing is the deliberate practice of telling incident war stories at team level so the team learns from each other’s shifts, not only from formal postmortems. Postmortems capture the structured analysis; war stories capture the texture, the dead-ends, the subjective experience of being on the bridge at 3am, all of which transfer pattern recognition to the next operator faster than any document.
- Share war stories. Per-incident team-level story; the texture and dead-ends, not just the timeline.
- Weekly on-call reviews. Per-week dedicated 30-minute slot; the rotation off-going engineer narrates the shift to the team.
- Pattern recognition. Recurring patterns surface across stories that no single postmortem reveals; the team learns the systems through the stories.
- Onboarding integration plus searchable archive. New on-callers attend war-story sessions before going on rotation; per-incident searchable archive supports later investigation.
The approach
The practical approach is a weekly cadence (the off-going on-call narrates the shift), pattern-aware listening (the team flags recurring shapes), explicit onboarding integration (new joiners attend before going on rotation), a searchable archive of stories so they accumulate, and committed practice in the team handbook so the cadence survives leadership change. War stories are the connective tissue between formal postmortems and tribal knowledge.
- Weekly rhythm. 30-minute slot; off-going on-call narrates; team listens; the cadence is non-negotiable.
- Pattern recognition. Team flags recurring shapes during the session; cross-incident patterns become visible.
- Onboarding integration. New on-callers attend stories before going on rotation; ramp shortens by weeks.
- Searchable archive plus documented practice. Stories captured in a searchable doc; per-team sharing practice committed for onboarding.
Why this compounds
Experience sharing discipline compounds across years. Each story grows the team’s shared narrative; each shared narrative shortens the next operator’s diagnosis time; the team’s collective pattern library grows from lived experience rather than abstract documentation. After two years, new hires onboard into a team with vocabulary, not just runbooks.
- Team learning. Right sharing produces real growth; engineers learn the systems through each other’s shifts.
- Operator experience. War stories build team connection; on-call stops feeling like a solo ordeal.
- Operational hygiene. Per-week rhythm catches recurring patterns before they become incident classes.
- Institutional knowledge. Each story teaches incident patterns; the team’s pattern library grows from lived experience.
Experience sharing discipline is an operational discipline that pays off across years. Nova AI Ops integrates with incident telemetry, surfaces patterns, and supports the team’s incident-learning discipline.