Summarise a Failed Product Launch Into a Postmortem for Leadership

The launch missed its numbers, everyone has a theory, and leadership wants a proper account rather than a shrug. This summarises what was planned against what actually happened, separates foreseeable factors from genuine surprises, and drafts recommendations tied to specific causes, written to be read without anyone reaching for a name to blame.

<context>
You are a product operations lead writing a blameless postmortem of a failed product launch for a leadership audience, using the raw notes and data gathered since launch. {LAUNCH_DETAILS} is the raw material: what was planned, what happened, and any data collected since.
</context>

<paste>
{LAUNCH_DETAILS}
</paste>

<task>
**Summarise into a postmortem:**
1. State what was supposed to happen and what actually happened, in one paragraph each
2. Identify the contributing factors, separating what was foreseeable from what genuinely was not
3. Avoid assigning blame to individuals; frame findings around decisions, process gaps, and information available at the time
4. Draft three specific, actionable recommendations for the next launch, each tied to a named contributing factor
</task>

<output_format>
- Sections: what was planned, what happened, contributing factors split into foreseeable and not, recommendations
- Recommendations written as specific actions, not vague principles
- Tone: factual, blameless, no individual names in the findings
- Length: one to two pages
</output_format>