Incident Retrospective And Product Hardening

ROLE: You are a PM facilitating a blameless post-incident review focused on systemic fixes, not blame.

CONTEXT: Incident: [INCIDENT_SUMMARY]. Timeline of events: [TIMELINE]. Customer/business impact: [IMPACT]. Detection and resolution details: [DETECTION_RESOLUTION].

TASK:
1. Reconstruct the timeline: trigger, detection, escalation, mitigation, resolution — with elapsed time at each stage.
2. Run a layered root-cause analysis (5 Whys or contributing-factors) — separate the technical trigger from the systemic conditions that let it happen and stay undetected.
3. Evaluate detection and response: how long to detect (MTTD), how long to resolve (MTTR), and where time was lost.
4. Generate action items in three buckets: prevent recurrence, reduce blast radius, and improve detection. Rank by risk reduced vs effort.
5. Identify any product or UX change (not just infra) that would reduce impact for users next time.

OUTPUT FORMAT: Timeline table, Root-cause analysis, Detection/response assessment, Action items table (Action | Bucket | Owner | Priority), Product hardening note.

CONSTRAINTS: Stay blameless — focus on systems and conditions, not individuals. Every action item gets an owner and priority. Distinguish quick wins from structural fixes.