INCIDENT POSTMORTEM PRESENTATION BRIEF

Authored example for adaptation; not a real customer incident or product test.

Review audience:
Question this meeting must answer:
Incident reference and approved distribution:
Event date and time zone:
Reviewed source record / source owner:

EXAMPLE RECORD (all times UTC on the same fictional event date)
09:00: release starts; first recorded report-job failures also appear.
09:04: alert notifies the on-call team.
09:12: rollback starts.
09:27: new report jobs are completing normally according to monitoring.
10:00: reconciliation records all 180 identified affected jobs complete.
The 180 counts distinct job identifiers, not distinct customers.
Failure logs contain an unrecognized-status error.
The component that introduced that status and the gap in pre-release testing remain under investigation.
No verified distinct-customer count or commercial-impact calculation is supplied.
Completion does not by itself establish correctness or absence of data loss.

SEVEN-SLIDE ROUTE
1. Bounded impact, current state and open release decision.
2. Affected workflow and 180-job definition; customer count unknown.
3. Timeline: first failure, detection, rollback, new-job recovery, catch-up.
4. Observed / proposed explanation / evidence still needed.
5. Specific supported response strengths or delays; no invented lessons.
6. Proposed changes, accepted owners to confirm, priority and completion evidence.
7. Actual decisions, unresolved evidence and conditions for the next release review.

PROPOSED ACTION EXAMPLES (not approved or completed)
Compatibility test: reproduce the rejected status on the failing producer/worker combination; record expected behavior on the corrected combination.
Recovery procedure: separately record restored new work, affected-job reconciliation and unresolved jobs in a rehearsal.

WORKING FIELDS FOR EACH CLAIM
Statement:
Observed / inferred / unknown:
Source, event time and recording time:
Impact definition / denominator:
What this does not establish:

WORKING FIELDS FOR EACH PROPOSED ACTION
Specific change:
Failure or delay it addresses:
Owner who has accepted it:
Priority / due date:
Evidence to inspect:
Remaining uncertainty:

DRAFTING INSTRUCTION
Create an incident-review draft from the supplied record. Keep impact, detection, rollback, new-job recovery and affected-job reconciliation separate. Distinguish observations from hypotheses. Preserve unknowns, source references and time zones. Do not invent affected customers, financial loss, causes, accepted owners or completed actions.

AFTER THE REVIEW
Actual agreed decision and conditions:
Unresolved question and evidence owner:
Accepted action and review date:
Source record updated by: