the brief → sign in
5 min left 0%

product review template

A product review is not a demo. It is fifteen minutes where leadership decides whether your product deserves more investment, less investment, or different investment. Show up with the wrong format and you lose that decision to whoever prepared better.
Talvinder Singh, Pragmatic Leaders

Most product reviews fail because they become feature demos. The PM walks through what shipped, shows a few screenshots, gets polite nods, and leaves with no decisions made. Leadership walks out knowing what happened but not whether it mattered.

A product review is a strategic conversation: is this product on track, and what needs to change? The format below forces that conversation. Five sections, one page, fifteen minutes. If you cannot fit your review into this structure, you are reporting activity, not outcomes.

The template

Copy everything between the horizontal rules below.

# Product Review: [Product Area]

**PM:** [Your name]
**Date:** [Review date]
**Period:** [Month/Quarter being reviewed, e.g. Jan 2025 or Q4 2024]
**Audience:** [Who is in the room — VP Product, CTO, CEO, etc.]

---

## 1. Outcomes vs Plan

[Pick 2-3 metrics that matter most for this product area right now.
Not a dashboard dump — the metrics leadership will judge this product by.]

| Metric | Target | Actual | Status | Why |
|--------|--------|--------|--------|-----|
| [e.g. D30 retention] | [42%] | [38%] | Off track | [Onboarding drop-off at step 3 — fix shipped week 8, too early to see impact] |
| [e.g. Weekly active teams] | [1,200] | [1,340] | On track | [Slack integration drove 180 net-new teams in 6 weeks] |
| [e.g. Revenue per account] | [INR 18K] | [INR 16.5K] | At risk | [Free tier usage growing faster than paid conversion — pricing experiment needed] |

**One-line summary:** [Are we winning or not? Say it plainly.]

---

## 2. What Shipped and What It Did

[Features that launched this period. Not a changelog — only what is worth
discussing at this level. Include early signal, not just ship date.]

- **[Feature name]** — Launched [date]. [Early signal: adoption rate, user
  feedback, or first metric movement. One sentence.]
- **[Feature name]** — Launched [date]. [Early signal.]
- **[Feature name]** — Shipped but adoption below expectations. [What you
  are doing about it.]

---

## 3. What We Learned

[The non-obvious stuff. Customer insights, experiment results, competitive
signals. Things that should change how leadership thinks about this product.]

- **[Insight]:** [What you found and why it matters. One line.]
- **[Experiment result]:** [What you tested, what happened, what it means
  for the roadmap.]
- **[Market signal]:** [Competitor move, regulation change, or category
  shift that affects your plan.]

---

## 4. What Is at Risk

[Problems ahead that leadership needs to know about. Be specific — vague
risk statements waste everyone's time.]

- **[Risk]:** [What could go wrong, when it would hit, how bad it would be.
  One line.]
- **[Risk]:** [Same format. Include technical debt, team capacity gaps,
  dependency blockers, competitive threats.]
- **[Risk]:** [If you have no risks, you are not looking hard enough.]

---

## 5. What We Need

[Decisions, resources, or alignment from leadership. Be specific about what
you are asking for and why you cannot solve it yourself.]

- **Decision needed:** [What the decision is, what options exist, what you
  recommend, and by when.]
- **Resource ask:** [What you need, what it unblocks, and the cost of not
  getting it.]
- **Alignment check:** [Where your plan conflicts with another team's plan,
  and what you propose.]

Presentation notes

Timebox: 15 minutes. Five minutes to present, ten minutes to discuss. If you are still presenting at minute ten, you brought too much material.

Lead with outcomes, not features. Open on Section 1. If the metrics are on track, leadership relaxes and the rest of the conversation is productive. If they are off track, leadership knows immediately and the conversation focuses on why and what to do — which is the point.

Bring the hard questions. Section 5 is why you are in the room. If you leave a product review without a decision or a resource commitment, the meeting was a status update you could have sent as an email. Write Section 5 first when preparing, then build the rest of the review to support those asks.

Do not read your slides. Leadership can read. Walk in, state the one-line summary from Section 1, then let them scan the page. Spend your five minutes on Section 3 (what you learned) and Section 5 (what you need). Those are the sections that require your voice.

// exercise: · 30 min
Prepare your next product review

Take the template above and fill it in for your current product area. Use real numbers, not placeholders.

When you finish, run this self-check:

  1. Section 1: Can someone who missed the last three months read your outcomes table and know whether this product is healthy? If not, your metrics are wrong or your “Why” column is vague.
  2. Section 2: Did you list more than five features? Cut to three. A product review is not a release notes email.
  3. Section 3: Is there at least one insight that would surprise someone in the room? If every learning is obvious, you are not digging deep enough.
  4. Section 4: Read your risks aloud. Would you bet your own money that none of them will hit? If yes, you are underreporting.
  5. Section 5: For every ask, check: could you solve this without leadership? If yes, remove it. This section is for things that genuinely require someone above you to act.
product review template 0%
5 min left