What This Template Is For

A product review is a recurring meeting (weekly or bi-weekly) where the product team reviews metrics, checks feature progress, and surfaces blockers. Unlike stakeholder reviews that face outward, product reviews face inward -- they are for the team building the product.

This template covers the five things every product review should address: metrics health, feature progress, blockers, customer signals, and the sprint ahead. It keeps the meeting under 30 minutes.

When to Use This Template

Weekly cadence: Run every Monday or Tuesday to set the week's focus.

Bi-weekly cadence: Run at the midpoint or end of each sprint to align on priorities.

Pre-launch windows: Increase to twice per week during major feature launches.

After metric changes: When a key metric moves significantly, use the template to structure the response.

Step-by-Step Instructions

Step 1: Update the Metrics Dashboard (10 minutes before the meeting)

Pull the latest numbers for your 4-6 core metrics. Compare to last period and targets. Flag anything that moved more than 10%.

☐ Metrics pulled from analytics tool with week-over-week comparison

☐ Anomalies or significant changes flagged with a brief explanation

Step 2: Review Metrics (5 minutes)

Walk through the dashboard. Spend time only on metrics that changed. For stable metrics, a quick "on track" is sufficient.

Step 3: Feature Progress Check (10 minutes)

Review each in-flight feature. Focus on what shipped since last review, what is on track, and what is at risk.

Step 4: Blockers and Escalations (5 minutes)

Surface anything blocking progress. Assign owners to resolve each blocker. Decide who escalates and by when.

Step 5: Customer Feedback Digest (5 minutes)

Share 2-3 customer signals from the past week: support tickets, interviews, NPS verbatims, or sales notes.

Step 6: Next Sprint Preview (5 minutes)

Preview what is coming next. Highlight new roadmap items and anything needing design or engineering input before next planning.

The Product Review Template

Meeting: Product Review

Date: [Date]

Cadence: [Weekly / Bi-weekly]

Attendees: [PM, Eng Lead, Design Lead, QA Lead, Data Analyst]

Metrics Dashboard

Metric	Last Period	This Period	Target	Trend
[Core metric 1]	[Value]	[Value]	[Value]	Up / Down / Flat
[Core metric 2]	[Value]	[Value]	[Value]	Up / Down / Flat
[Core metric 3]	[Value]	[Value]	[Value]	Up / Down / Flat
Feature adoption	[Value]	[Value]	[Value]	Up / Down / Flat

Key observations: [1-2 sentences on what the data tells you]

Feature Progress

Feature / Initiative	Status	Owner	Shipped / ETA	Notes
[Feature 1]	Shipped	[Name]	[Date]	[Outcome or early data]
[Feature 2]	In Progress	[Name]	[Date]	[% complete or milestone]
[Feature 3]	At Risk	[Name]	[Date]	[Reason + mitigation]
[Feature 4]	Not Started	[Name]	[Date]	[Dependency or prep needed]

Blockers

Blocker	Impact	Owner	Resolution Plan	Due
[Blocker]	[What it blocks]	[Name]	[Next step]	[Date]

Customer Signals

Source	Signal	Related Feature	Action
[Support / Interview / NPS]	[What the customer said]	[Feature or "New insight"]	[Next step]

Next Sprint Preview

☐ [Upcoming item 1] | [Upcoming item 2]

☐ [Design review needed for]: [Item]

Example

Meeting: Product Review | Date: Feb 13, 2026 | Cadence: Weekly

Attendees: Alex (PM), Dana (Eng Lead), Kim (Design), Raj (QA)

Metric	Last Week	This Week	Target	Trend
DAU	12,400	12,850	15,000	Up
Activation rate (Day 7)	31%	32%	35%	Up
P95 page load	1.8s	2.1s	1.5s	Down
Search feature adoption	8%	12%	20%	Up

Key observations: Search adoption doubled after shortcut hint shipped. Page load regression tied to analytics script -- Raj investigating.

Feature	Status	Owner	ETA	Notes
Search keyboard shortcut	Shipped	Dana	Feb 10	12% adoption, up from 8%
CSV export	In Progress	Raj	Feb 19	Backend done, UI in review
Onboarding v3	At Risk	Kim + Dana	Feb 28	Design revisions -- 3 day slip

Blocker: Page load regression (core web vitals failing) -- Owner: Raj, audit analytics script by Feb 14.

Customer signal: 3 support tickets about confusing export format options. Adding descriptions to UI in current sprint.

Tips

Keep it under 30 minutes. Product reviews are check-ins, not working sessions. If a topic needs deep discussion, schedule a follow-up.

Automate metric collection. Set up a dashboard that auto-updates before the meeting. Manually pulling numbers wastes time and invites errors.

Rotate who brings customer signals. When only the PM shares feedback, the team develops a secondhand relationship with users.

Track feature outcomes, not just ship dates. Add a row back to the table 2-4 weeks after launch with adoption data. This closes the feedback loop.

Use the next sprint preview to prevent surprises. If a designer sees next sprint's items for the first time in sprint planning, you are too late.

Product Review Meeting Template