pm-postmortem-writer

To write a postmortem report, provide your launch goals, timeline records, outcome data, and issue lists. The process generates a structured document comparing planned objectives against actual results and assigning action items.

Root cause analysis in a retrospective traces deviations back to controllable causes using methods like 5-Why and timeline analysis. It identifies why specific issues occurred during a launch or incident to prevent recurrence.

Yes, you can use a postmortem template for OKR retrospectives and A/B experiment summaries. The process adapts to feature rollouts and quarterly reviews by comparing goal-versus-result data and extracting lessons learned.

The best way to document action items is to capture what went well, what should stop, and assign clear owners and deadlines for follow-up actions. This ensures accountability after the root cause analysis is complete.

Yes, incident root cause analysis requires goal-versus-result comparison to highlight gaps with concrete numbers. This comparison contextualizes the incident's impact and frames the subsequent 5-Why investigation.

To generate a structured launch review, you need launch goals, timeline records, outcome data, and issue lists. These inputs enable the system to perform multi-layer root-cause analysis and produce actionable follow-up steps.