How to Run Product Reviews That Build Trust

TL;DR

Start a product review with the recommendation or most controversial proposal, ideally within the first 20% of the deck or five minutes of the meeting. The primary goal is not merely to secure a decision, but to build trust and win over key stakeholders by focusing discussion on disagreement, making important points easy to scan, and creating memorable language that spreads internally.

Transcript

hello Lenny con I'm Mika I'm a product lead at figma and the founding PM for figma slides and I'm Yuki and I lead the product team at figma and today we are so excited to be chatting with you about how to do the product review right by actually doing it a little bit wrong specifically we're super excited to take you behind the scenes and give you b... Read More

Key Insights

• The most important outcome of a product review is building trust and winning over key stakeholders, not simply making a decision between competing options. Decisions may still occur, but treating them as the only purpose overlooks the relationship and alignment created through a well-directed discussion.
• Executive requests for the deck link can signal a desire to see the recommendation immediately. When reviewers scroll ahead while the presenter supplies context, they may be looking for the conclusion needed to judge whether the preceding problems, goals, and principles support the proposed direction.
• Early requests for agreement often produce silence because participants lack enough information to evaluate the framing. Reviewers may hesitate to endorse problems, goals, or principles before seeing the recommendation, since apparently reasonable framing can still lead to a conclusion they do not support.
• The punchline should appear within the first 20% of the deck or the first five minutes of the review. This gut check prevents background material from consuming the meeting and gives participants enough time to react to the consequential or controversial parts of the proposal.
• Strong negative reactions can be useful when they happen early because they reveal what requires attention. Presenting controversial material near the beginning encourages active participation and allows the group to spend the review investigating disagreement instead of discovering it during the final minutes.
• Opinionated slide headings make the review easier to scan and understand. A heading should communicate the conclusion or point of view rather than use a generic label such as audience, helping distracted participants quickly recover the argument and rejoin the discussion.
• An alignment widget identifies where participants are most misaligned before discussion time is allocated. Soliciting everyone's opinions helps the product manager focus the conversation on areas of genuine disconnect instead of spending equal time on topics that already have broad support.
• Memorable internal language can help a proposal spread through a company. Figma's slides initiative used the name Flides to create curiosity and support for a bottom-up effort, and the term became attached to work streams, animations, layouts, and informal Friday greetings.

Questions & Answers

Q: How should a product review begin?

A product review should begin with the recommendation, controversial proposal, or other consequential conclusion instead of a long sequence of background slides. The presenters recommend reaching this material within the first 20% of the deck or the first five minutes. Showing the punchline early gives reviewers a reason to pay attention and creates more time for substantive discussion.

Q: What is the main goal of a product review?

The main goal of a product review is to build trust and win over key stakeholders, rather than treating the meeting only as a moment for choosing between two radical options or granting a green light. A decision can still be an outcome, but the review is also a forum for demonstrating judgment, exposing disagreement, and strengthening stakeholder confidence.

Q: Why should product managers avoid lengthy context setting?

Lengthy context setting can cause reviewers to tune out, multitask, or scroll directly to the recommendation. Background, problems, goals, and principles may sound reasonable without giving participants enough information to judge them. If the consequential proposal appears only near the end, the strongest reactions arrive when little time remains to understand or address them.

Q: Why do executives sometimes skip to the end of a review deck?

Executives may skip to the end because they want to know the actual recommendation before evaluating the setup. The Figma presenters describe a request for the file link as possible code for wanting the conclusion. Seeing the recommendation helps a reviewer determine whether the earlier framing is relevant and whether the proposed direction deserves agreement or challenge.

Q: Why can asking for alignment early create awkward silence?

An early alignment check can create silence because participants may not yet understand what agreement would commit them to. They might accept the stated problem or principles but worry that those ideas lead to an unsuitable recommendation. Some reviewers therefore want to look ahead at the conclusion before confirming that they agree with the framing presented at the start.

Q: How can slide headings improve a product review?

Slide headings can improve a review by stating a conclusion or point of view rather than merely naming the section. A title such as a generic audience label forces reviewers to infer the message, while a punchline-style heading reveals it immediately. This approach also helps participants who become distracted scan the deck, recover the argument, and rejoin the conversation.

Q: How can teams identify disagreement during a product review?

Teams can use an alignment widget to collect each participant's opinion and reveal where views diverge. The product manager can then concentrate discussion on the areas with the greatest disconnect. This is especially useful when the controversial part of a proposal is not obvious beforehand, because the group directly indicates which topics require closer examination and conversation.

Q: How can memorable language help an internal product proposal?

Memorable language can generate curiosity and help an initiative spread across a company. Figma's slides product was initially called Flides internally because the team wanted a distinctive name rather than a generic label. The term spread into animation and layout work streams, Friday greetings, and broader company conversation, supporting a bottom-up effort to place a new product on the roadmap.

Summary & Key Takeaways

• Product reviews can feel broken when executives skip ahead, take control of the material, or disengage during lengthy setup. These behaviors often indicate that reviewers want the actual recommendation first. A successful review should help the presenter direct attention toward the areas that need discussion while building trust with key stakeholders.

• Traditional review structures place background, problems, goals, and principles before solutions and recommendations. This gradual buildup can bury the most consequential proposal until the meeting is nearly over. Starting with the punchline creates engagement earlier, reveals strong reactions, and leaves more time to examine the assumptions or choices that produce disagreement.

• Clear, opinionated headings and alignment widgets make reviews easier to navigate. Headings should state conclusions instead of merely naming topics, while alignment widgets reveal where participants disagree. Memorable internal names can also generate curiosity and support, as Figma's temporary name for its slides product spread across teams and became part of company language.