deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/launch-metrics
launch-metrics
VerifiedDefine launch success metrics, decision triggers, and 30/90/180-day reviews before launch. Use when you need to know early whether a launch is working and what you will do if it isn't.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.4 KB |
| examples/sample-industrial.md | markdown | 3.8 KB |
| examples/sample.md | markdown | 3.6 KB |
| template.md | markdown | 2.8 KB |
template.md
View on GitHub# Launch Metrics Template
Every baseline, target, and threshold without a source stays `[NEEDS SOURCE]`. AI-suggested
metrics carry no numbers. Quality checks at the bottom.
---
## 1. Scope
**Launch:** [offering, markets, channels, date] · **Target outcome:** [from the business case]
**Sales cycle:** [length] · **Review forum / escalation decider:** [names]
## 2. Metric set (8-12 total)
| # | Category | Metric (exact definition) | Lead/Lag | Guardrail? | Baseline + source | Target + date + basis | System | Owner | Frequency | Tag |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Adoption | | | | | | | | | |
| 2 | Commercial | | | | | | | | | |
| 3 | Operational | | | | | | | | | |
| 4 | Customer | | | | | | | | | |
Every lagging metric is paired with a leading one: [pairs listed].
## 3. Decision triggers
| # | Stay the course | Adjust (owner, action) | Escalate (to whom, options) | Data points before it fires |
|---|---|---|---|---|
## 4. Funnel (defined in this offering's terms)
| Stage | Definition here | Source | Baseline conversion to next |
|---|---|---|---|
| Acquisition | | | |
| Activation | | | |
| Retention | | | |
| Revenue | | | |
| Referral | | | |
**The conversion that matters most:** [stage → stage, and why]
## 5. Cohorts
| Cohort (shared start) | Count | Month 1 | Month 3 | Month 6 | Metric |
|---|---|---|---|---|---|
Show the count beside every rate. No conclusions from a cohort of three.
## 6. Review plan
| Review | Date | Attendees | Metrics in focus | Question | Decision it can make |
|---|---|---|---|---|---|
| 30-day | | | | Is it running? | |
| 90-day | | | | Is it on track? | |
| 180-day | | | | Is it working? | |
| 12-month (long-cycle) | | | | | |
## 7. Post-launch review record
**Rose / Bud / Thorn** (each owner writes alone first; record who saw it)
| Observation | Type | Seen by / where | Theme |
|---|---|---|---|
**Retro rundown**
| Metric or decision | Expected (agreed pre-launch) | Actual + source | Why (hypothesis until checked) | What to change (owner, trigger answered) |
|---|---|---|---|---|
**Premortem drivers:** did any start to happen? [yes/no, which]
**Goes to the next product review:** [list] · **Hands over to ongoing metrics on:** [date, owner]
## 8. Baselines to collect before launch
1.
## 9. Riskiest assumptions (committed copy)
1.
---
## Quality checks
- [ ] All four categories covered; guardrails marked
- [ ] Each lagging indicator has a leading one
- [ ] No activity metric is standing in for a result
- [ ] Intake is separate from sell-through or activation
- [ ] Every baseline and target has a source and an owner, or is `[NEEDS SOURCE]`
- [ ] Triggers set before launch, with data points required
- [ ] Each metric names a system and a person
- [ ] "Expected" in every review traces to a pre-launch target
- [ ] Every thorn and action has an owner
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |