NO ONE WORKS HERE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PARADE.PAULCHEEK.COM • PAUL@CHEEK.ORG 01110000 01100001 01110010 01100001 01100100 01100101PARADE WEEK / Worksheets Worksheet: Incident Report · © Cheek LLC 2026 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Parade Week Packet · Worksheets Worksheet: Incident ReportA blameless postmortem. One rule before you write a word: The log is the truth. Write from telemetry, not memory. The room remembers a blur; the log remembers timestamps. Where they disagree, the log wins. Blameless means the question is never who did this. The question is what allowed this. Incidents come from missing controls, not from guilty agents, and not from guilty people. Write accordingly; redesign accordingly.
1. Incident summaryOne paragraph, for a reader who was not there: what went wrong, how big it got, how it was stopped, what it cost. Numbers over adjectives. 2. TimelineBuilt from the telemetry. Start before the first bad action: the last known-good moment matters too.
3. DetectionHow was it first noticed, and how fast?
4. ContainmentThe actions that stopped it, in order, with times.
5. Root causeThe missing guardrail, not the guilty agent. Name the control layer that was absent or too weak: cap, gate, scope, monitor, or kill switch. If your first answer describes an agent's behavior, ask what boundary made that behavior possible, and write that down instead.
6. DamageNumbers, each with its source in the log.
7. What heldThe controls that worked as designed. Containment is evidence too, and the redesign should keep what earned its place. 8. RedesignChanges committed, not considered. Each with an owner and a date.
9. Communications
Sign-off
|