Index of every page on this site: llms.txt
All skills
deanpeters avatar

/launch-metrics

@476ae12
Run it yourself

Define 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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/launch-metrics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

template.md

≈719 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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

9. Riskiest assumptions (committed copy)


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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    No security issues were detected. The skill provides a strategic framework and templates for defining launch metrics without including any executable scripts or dangerous commands.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: MEDIUM · 1 issue

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[what launched or is launching, and how long your sales cycle is]
type
component
theme
strategy-positioning
Other metadata
intent
Turn "was the launch a success?" into a question the team can answer with data, early enough to act, using thresholds and responses agreed before anyone sees the results. Pairs leading with lagging indicators across adoption, commercial, operational, and customer categories, and schedules structured reviews that end in owned actions.
best_for
[
  "Defining what launch success means before a launch, not after",
  "Choosing leading indicators when sales cycles are long or revenue arrives late",
  "Setting up 30, 90, and 180-day reviews with agreed stay / adjust / escalate triggers",
  "Auditing a launch dashboard that tracks activity instead of results"
]
scenarios
[
  "How will we know the route optimizer launch is working before the quarterly numbers land?",
  "Our launch dashboard shows trade-fair leads and press mentions. What should we track instead?",
  "Plan the 90-day review for a new controller with an 8-month sales cycle",
  "Distributor orders are strong but I don't trust them. What am I missing?"
]
estimated_time
30-45 min

README badge

README badge for deanpeters/product-manager-skills/launch-metrics