Failure Replay Theater — A Year of Incidents as Thirty-Second Screenplays
Replay every production incident from the past year as a 30-second screenplay. Same characters, same blocking. Then write the meta-incident: which character keeps making the same mistake?
Why this exists
Postmortems treat each incident as unique. New cause, new owner, new action items, file it away. Stack a year of them on a shelf and you get a stack of one-offs. Stage that same year as theater — same cast, same blocking, thirty seconds each — and the repetition stops being deniable. The same character walks on stage and makes the same kind of mistake, scene after scene. The actual lesson is structural, not individual.
What you get back
- A thirty-second screenplay for every production incident in the window — same characters, same blocking, just the variables swapped.
- Recurring character analysis: which role keeps driving the bad scene, and what shape the mistake takes each time.
- The structural pattern that keeps producing the same scene — the org behavior that casts that character every quarter.
- A list of changes that would rewrite the script, not retrain the actor.
When to reach for this pattern
Annual reliability reviews where the action-item backlog has grown faster than the fix rate. New SRE leadership taking over a service with a thick incident folder and no clear narrative. Any moment you suspect the systemic issue is hiding behind a year of individually reasonable incident reports.
Replay every production incident from the last year as a thirty-second
screenplay. Same characters across all scripts: the on-call, the
customer, the deploy, the alert, the post-coffee Slack message. Same
blocking. Then write the meta-incident — which character keeps making
the same kind of mistake? Cast the pattern, not the person.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- Incident reports look like one-offs. They almost never are.
- Staged as theater with a fixed cast and fixed blocking, the recurring character becomes obvious within three scripts.
- The lesson is rarely 'this engineer made a mistake.' It's 'the system keeps producing this same scene.'