launch-debrieflisted

# Launch Debrief (MIRROR Protocol) A structured post-launch retrospective engine that transforms raw launch data into quantified learnings, root-cause analyses, and improvement playbooks. MIRROR ensures every launch makes future launches better by extracting actionable insights from both successes and failures through systematic analysis rather than anecdotal recall. ## When to Use - Conducting a post-launch retrospective (ideally at T+30 and T+90) - Analyzing why a launch over- or underperformed expectations - Building an institutional knowledge base of launch learnings - Creating improvement playbooks for the next launch cycle - Presenting launch results to leadership with root-cause analysis - Comparing actual results against pre-launch projections - Identifying systemic issues across multiple launches ## What You'll Need **Critical inputs (ask if not provided):** - Launch name, date, and type (GA, beta, feature, expansion) - Pre-launch targets for all VITAL metrics (from launch-pulse) - Actual performance data for all tracked metrics - Launch readiness scores from gate reviews (from launch-command) - Budget allocation and actual spend (from budget-allocator) - Channel performance data by channel (from demand-engine) **Nice-to-have:** - Customer feedback (NPS, surveys, support tickets, social mentions) - Internal team feedback (retro notes, Slack threads, post-mortems) - Competitive activity during launch window (from battle-scanner) - Sales feedback on messaging and