Incident Narrative Review Session¶
Ritual — instantiates Hermeneutic Iteration
Uses a structured session to revisit incident details and whole account before lessons or narratives are finalized.
The Incident Narrative Review Session is a ritual gathering that revisits the raw details of a past incident — logs, timelines, operator testimony — and tests them against the draft account before the lessons and the official narrative harden. Its defining property is retrospective reconstruction: it reconstructs the meaning of a bounded, already-completed event from a fixed evidentiary record, letting a small contradicting detail still revise the story, and it stops when the account is adequate to write a corrective action. The event is over; what is at stake is getting its meaning right before it sets.
Example¶
A payments platform has just weathered a three-hour outage. The on-call engineer's draft timeline says, plainly, "the 14:02 deploy caused the outage." The team convenes a review session with the logs, the alert history, and two operators' recollections on the table. Working detail by detail, someone notices that database connection latency began climbing at 13:50 — twelve minutes before the deploy. That single log entry contradicts the story. Instead of explaining it away, the session lets it revise the whole: the account becomes "the 14:02 deploy exposed a pre-existing connection-pool leak that had been building since 13:50." The revised account is then tested against every other timeline entry to confirm it now fits them all. The session stops not at a full academic root-cause treatise but at the point where the account is adequate to write a concrete fix — bound the pool and add a leak alert. The lesson that gets recorded is grounded in the evidence, not in the first plausible story.
How it works¶
The session works strictly from the fixed record — logs, transcripts, metrics — so every claim in the account can be anchored to something that actually happened. Its core discipline is to surface contradicting details before finalizing: a detail that resists the draft story is brought into the room, not buried. The draft account is tested against each such detail, and revised when it fails. The stopping rule is action-adequacy: the session ends when the account is good enough to drive the corrective action, not when every philosophical question about the incident is answered. It is retrospective and bounded — the event is closed, and the record does not change under the team's feet.
Tuning parameters¶
- Timeboxing — a tight fixed session versus an open-ended dig. Tight boxes force adequacy; open ones risk endless re-litigation of a closed event.
- Blamelessness norms — how strongly blame is excluded. Stronger norms surface honest testimony but can soften accountability; weaker norms do the reverse.
- Room composition — just responders versus a wider set of stakeholders. Wider rooms catch more contradicting detail but dilute focus and candor.
- Reopening threshold — how strong a contradicting detail must be to reopen the account. A low threshold keeps the story honest but can thrash; a high one risks locking in a wrong narrative.
- Adequacy bar — stop at "enough to write a fix" versus "full causal understanding." A lower bar ships lessons faster; a higher one learns more but costs time.
When it helps, and when it misleads¶
Its strength is that it prevents premature story-lock: because the account must survive every contradicting log entry, the first plausible narrative cannot quietly become the official one. This is the "second story" discipline — insisting that the account go beyond the convenient surface explanation to the conditions that actually produced the outcome.[n1]
Its failure mode is convergence on a communicable story over an accurate one: teams gravitate to the narrative that is easy to tell leadership, and hindsight bias makes the outcome look more foreseeable than it was, distorting which details seem important. The classic misuse is running the session to produce a blame-assigning headline rather than a faithful account. The guarding discipline is to require the account to survive the resistant detail — not merely to sound coherent — and to keep the stop at action-adequacy rather than at the first satisfying story.
How it implements the components¶
interpretive_part— each log entry, alert, and piece of testimony is a detail the account must fit.evidence_or_text_anchor— the fixed record anchors every claim, so nothing in the account floats free of what happened.coherence_test— the draft account is checked against every detail and revised where it fails.action_adequacy_threshold— the session stops when the account is adequate to write the corrective action, not before and not endlessly after.
It does not facilitate live interpretation of an unfolding situation across many standpoints — no orchestrated participant_perspective_set and no open-ended revision_cycle on a moving target — because that prospective, live looping belongs to its nearest twin, Sensemaking Loop Facilitation; this session reconstructs a closed past event from a fixed record.
Related¶
- Instantiates: Hermeneutic Iteration — the session applies the part-whole loop to a closed event before its meaning hardens.
- Sibling mechanisms: Sensemaking Loop Facilitation · Ambiguity Log · Legal Interpretation Memo · Close Reading Protocol · Qualitative Analysis Memoing · Design Research Synthesis Wall · Iterative Coding Cycle · Part-Whole Mapping Matrix
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Incident Narrative Review Session operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it uses a structured session to revisit incident details and whole account before lessons or narratives are finalized
Independent corroboration: The frozen evidence defines Incident Narrative Review Session as 'Uses a structured session to revisit incident details and whole account before lessons or narratives are finalized', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Communication, Facilitation & Learning — The session is classified by its bounded test of an incident account against fixed evidence rather than by facilitation alone.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The incident-learning purpose and Sidney Dekker second-story anchor place the mechanism in modern safety and reliability engineering.
Related originating lineages:
- Aviation & Aeronautics — Accident investigation materially developed deeper systemic narratives beyond operator blame.
- Ethnography & Qualitative Methods — Operator testimony, interpretive reconstruction, and competing accounts use qualitative methods.
- Philosophy — Hermeneutic iteration supplies the part-whole method for revising an account against resistant details.
Review resolution: Both reviewers independently assign engineering_design as the primary originating domain, so that shared primary is retained. Alternate domains are the union of reviewer-identified formative or independently originating lineages; later application settings alone are excluded. The final form materially composes methods or concepts from more than one formative domain. It has established independent use across several domains, but that does not make it domain-free. The encyclopedia entry makes that composition explicit.
Attribution caveat: The named session is an encyclopedia synthesis of safety investigation and hermeneutic method.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The "second story" — Sidney Dekker's contrast (in the "new view" of human error) between the convenient first account that stops at a broken component or a bad actor and the deeper account of the conditions that made the failure sensible at the time. The session's insistence on surviving the resistant detail is what pushes it past the first story. ↩