Skip to main content
Next Step PM
Back to the library

Measure and improve · Core

Hold a post-launch review

A few weeks after launch, step back as a team: did the product achieve what you hoped, what did you learn, and what will you do differently next time?

About 2-4 hoursEvergreenLast reviewed 5 November 2026

Who this applies to

Skills it builds
Data and measurementCommunication and influence
PM types
All
Product types
All
Starting points
All
Ways of working
All
Experience
All
Size of organisation
All

Steps, by experience

Beginner (under 1 year)

  1. Book the review two to six weeks after launch, once there is real data.
  2. Gather the results against your hypothesis and success metrics.
  3. Ask everyone what went well, what did not and what surprised them.
  4. Focus on the process and decisions, never on blaming people.
  5. Agree three or four actions with owners.
  6. Share a short summary with stakeholders.

Intermediate (1 to 4 years)

  1. Review outcomes against the hypothesis and metrics.
  2. Review delivery: plan versus actual, and why.
  3. Agree actions with owners.
  4. Publish a short summary.

Experienced (5+ years)

  1. Compare the outcome with the original business case and be honest about the gap.
  2. Look for patterns across several launches.
  3. Feed lessons into planning and estimation practices.
  4. Share learning across teams, including failures.

Who can do this

Owner: Product manager

Can be delegated to

  • Scrum Master or Delivery Manager: Facilitate the review
  • Data Analyst or Performance Analyst: Present results against the metrics

Reviewed by: Delivery Manager, Tech Lead

Tool examples

Confluence
Use a retrospective template and link it to the product brief.
Miro
Run the review on a board with sections for results, delivery and actions.
Google Docs
Write a one-page summary for stakeholders.

Definition of done

  • Results reviewed against the hypothesis
  • Actions agreed with owners
  • Summary shared

Common pitfalls

  • Holding it too early, before there is data
  • Turning it into blame
  • Agreeing actions nobody follows up

If you lead the team

What good looks like: Teams review results a few weeks after launch and share what they learned.

Ask your PM

  • Did we achieve what we hoped, and what did we learn?
  • What are we changing because of it?

Warning signs

  • Reviews never happen once the next project starts.
  • Lessons are written down but not used.

Do these first

Sources