Product review / QBR

Product Review and QBR are valuable not in the number of slides, but in the quality of decisions after a meeting. Build a conversation around changes in users, business, and risk; separate fact from interpretation, and end each topic with a fixed decision, owner, and validation date.

What is Product Review and QBR?

Definition and objectives

Product review is a regular meeting where the team and stakeholders discuss product progress, key metrics and plans. QBR (Quarterly Business Review) is a format of a deeper meeting once a quarter with a strategic focus: watch how the product and team meet business goals, record successes and failures, and immediately adjust plans.

What do you need?

Product review – helps to maintain the overall rhythm, convey progress, adjust tasks on the short horizon. QBR is needed to keep the strategic picture, to reconcile expectations at the level of top management, to synchronize different functions and to change priorities in time.

When they are

Product review is usually every 2-4 weeks, QBR every 3 months.

** Example:**
After the new functionality is launched, the team convenes a product review to discuss the first results and user feedback. On QBR, a quarter later, we analyze how this release helped advances on key metrics (e.g., user retention).

Key expectations of stakeholders and how to work with them

Minimize the gap between plan and fact

Stakeholders want to know where the product is relative to what they promised. It is important not only to show the numbers, but also to explain what they mean for the business. Without this expectation, reality diverges – distrust arises.

The best way is to compare the dynamics of key metrics (MAU, retention, NPS, LTV) and explain why the deviation occurred.

** Example:**
The product review shows the MAU plan for the month and the actual value. If below, explain that the new onboarding has not worked and is already testing the hypothesis with a different variant.

Transparency and honesty

Working with information is not just about success. Protect the confidence of stakeholders: talk about difficulties, failed decisions and plans for correction. Briefness and structure are more important than all your favorite beautiful slides.

Anti-pattern:
Hide negative results for the sake of a good picture. As a result, the problem will surface late, and stakeholders will feel the catch.

Effective product review and QBR

Effective communication: what is important to include

For a quick and clear perception, keep the structure:

1. Progress on targets with numbers
2. New insight or identified problem
3. How Team Actions and Plans Change Things
4. What is expected of stakeholders (solutions, confirmations, resources)

Example of the short product review agenda:

1. What they did for the sprint
2. Basic metrics and their dynamics
3. Failure/debt/risk
4. Plans for the next period, if necessary, requests to stakeholders

Visualization and storytelling

Instead of overloaded slides and tables, show the dynamics: graphs, trends, block schemes, problem clouds. Simple visualization reduces the number of clarifying questions.

Anti-pattern:
Classic pdf with 30 slides with details of each team. Stakeholders lose the main thing and do not ask key questions.

Key Mistakes and Traps in Working with Expectations and Information

Communication errors

1. Ambiguous wording, numbers without context.
2. Focus on the objectives, not the value of the product.
3. Trying to justify failure without analyzing the causes.
4. Lack of discussion of the implications and new risks.
5. There is no record of what is expected of listeners.

How to avoid:** Formulate clearly: plan/fact, what prevents, who/what will help remove the blockers. Acknowledge the risks and challenges, offer solutions, not just ask for approval.

Example:

On QBR, you set a target for subscriber growth: you didn’t achieve it because of marketing disruptions and competition. Don’t hide a weak result – suggest 2-3 steps that the team will take and ask for support or a specific solution if it goes beyond your authority.

How to Measure Review/QBR Performance and Improve Process

Metrics of success

Often use qualitative feedback and the following indicators:

1. Stakeholders understand where the product is based on the survey after the meeting.
2. The number of questions at the end of the meeting is reduced, which means that the information is provided clearly.
3. Decisions are made at a meeting, not postponed.

Improvements

Ask for feedback immediately after the meeting: what was clear and what was not enough. Record your decisions and next steps in one document and send them throughout the day. Try to change the format and channels of communication (for example, slide, short Loom, miro board) – look for a way in which you achieve the result with minimal time.

** Example:**
The transition from offline presentations to short video reviews with main points and graph parsing improved feedback from remote stakeholders and reduced the number of refinements.

FAQ on product review and QBR

**1. What is the difference between product review and QBR? Product review is more regular and shorter, the main focus is tactical product management and tasks; QBR is deeper, more strategic, and usually conducted for the tops of the company.

**2. Who participates in product review and QBR? In product review, the product team and key stakeholders (e.g. marketing, support). In QBR – top managers, heads of departments, business customers.

**3. What metrics should I show? **
Those related to product objectives: MAU, retention, LTV, NPS, revenue, conversion rate, etc. The specific set depends on the business.

**4. How long does the product review take? Usually 30-60 minutes, maximum - no more than one and a half hours. QBR is up to 2 hours, but a clear structure is required.

**5. How to prepare for review/QBR? In advance, they collect data on metrics, fix a plan / fact, form key problems and successes, prepare questions for stakeholders.

6. Which format is preferable? Compact dashboards, short slides with graphs, sometimes - video summaries. The main thing is clarity, relevance and the ability to quickly see the main thing.