Launch findings and next-launch-changes doc
Writes the launch findings document and the prioritised next-launch-changes list from post-mortem analysis.
In / outLaunch dataset and qualitative notes → findings doc with key metrics, what worked/didn't, and prioritised next-launch changes
You might say…
“I keep making the same mistakes because I never write down what I'd change — the post-mortem always gets skipped.”
What it does
Reads the assembled actuals-vs-targets data and writes the structured debrief — what worked, what failed, and the specific changes to make next launch, with the reasoning behind each call. Used in the one-off post-cart-close debrief session to extract transferable lessons.
Trigger: Use after assembling the launch dataset to produce the documented findings and carry-forward improvement list.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation