Feature Launch Retrospective

Template Overview

Shipping a major product capability represents the culmination of weeks of cross-functional collaboration. The Feature Launch Retrospective template gathers engineering, design, marketing, and support teams to analyze real-world performance, evaluate adoption metrics, celebrate wins, and capture operational lessons.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Launch Retrospective: [Feature Name]"
date: [YYYY-MM-DD]
launch_lead: "[[Product Manager]]"
engineering_lead: "[[Lead Architect]]"
marketing_lead: "[[Product Marketing Lead]]"
feature: "Local Whisper On-Device Transcription"
launch_date: "[YYYY-MM-DD]"
overall_verdict: "Successful Launch / Follow-Up Needed"
tags: [launch-retro, product, release, retrospective, gtm]
---

# Launch Retrospective — [Feature Name]

## 1. Launch Metrics: Forecast vs Reality
| Metric | Projected Target | Actual Result (Day 7) | Evaluation |
|---|---|---|---|
| **Beta Sign-Up Conversions** | 1,500 users | 2,840 users | Exceeded (+89%) |
| **Crashes / Unhandled Exceptions** | < 0.1% | 0.02% | Exceptional Reliability |
| **Model Download Completion Rate** | 85% | 94.2% | Healthy Network Fallback |
| **Average Meeting Length Recorded** | 35 Minutes | 42 Minutes | High Engagement |

## 2. Cross-Functional Perspectives
### What Engineering Learned
- Apple Silicon CoreAudio ScreenCaptureKit pipelines performed with higher stability than expected across macOS Sonoma and Sequoia.
- Model file downloads required progress resumability to prevent failures on flaky coffee-shop Wi-Fi networks.

### What Marketing & Design Learned
- Messaging emphasizing 'No Bot Joins Your Meeting' generated 4x higher social engagement than generic 'AI meeting notes' positioning.
- Dark mode app screenshots converted 28% higher than light mode variants on landing pages.

## 3. Customer Support & Friction Surfaced
- Top support inquiry: Users asking whether an external microphone requires separate macOS permissions (clarified in updated documentation).
- Minor UI confusion: Users looking for a cloud sync button; resolved by educating them on local vault folder portability.

## 4. Post-Launch Polish Items (Technical & GTM)
- [ ] [[Engineering Lead]] Ship patch adding resume support for partial model weight downloads.
- [ ] [[Marketing Lead]] Update FAQ section clarifying that microphone and system audio capture are isolated locally.
- [ ] [[Design Lead]] Refine empty state illustration when zero meeting notes are present in today's folder.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Launch Retro: Markdown Template Gallery"
date: 2026-10-08
launch_lead: "[[Maya Lin]]"
feature: "Template Gallery Wave 1"
tags: [launch-retro, product]
---

# Launch Retro: Markdown Template Gallery

## 1. Key Results
The launch of 120 curated templates drove a 210% increase in organic search impressions within 48 hours. Download actions performed with 100% client-side reliability.

When to Use and When to Avoid

When to Use

• Use within 1 to 2 weeks following a major feature release or milestone launch.
• Use to gather cross-functional feedback across engineering, design, marketing, and support.
• Use to audit actual customer metrics against initial business projections.

When to Avoid

• Avoid using for weekly iterative sprint bug scrubs.
• Avoid using before launch metrics and customer feedback have materialized.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the feature launch retrospective recording:
1. Extract actual launch metrics and compare them to projected business targets.
2. Outline key lessons learned across engineering, design, and marketing disciplines.
3. List all post-launch bug fixes, polish items, and documentation updates into clean Markdown.

Your data remains securely on your Mac with zero cloud exposure.