Effective Product Reviews
Run rigorous alignment sessions that raise the quality bar and accelerate decision-making.
Help the user with effective product reviews using insights from 12 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Assess review culture - Evaluate current review formats and identify bottlenecks or gaps in quality standards.
- Select a framework - Recommend the appropriate review stage or template based on the project's complexity and lifecycle.
- Draft review materials - Assist in framing problem statements, mapping the option space, and preparing pre-read documents.
- Facilitate the session - Provide techniques for gauging sentiment, managing dissent, and capturing clear decisions.
Core Principles
Evaluate Frameworks, Not Solutions
From "How Figma builds product": "One thing I encourage for both is to first present the “option space”—it’s really powerful to have a framework that maps all possible solutions or problems and use that as a device to discuss high-level tradeoffs or philosophical differences."
High-quality decisions come from mapping the entire field of possible solutions rather than debating a single proposal in isolation.
Establish a Transparent Cadence
From "How Duolingo builds product": "Product review meetings happen every Tuesday and Thursday for a total of two hours. These two hours are divided into 20-minute slots that product teams sign up to present. The agenda of these meetings is product teams presenting their proposed product changes for the first 5 to 10 minutes and then reviewers asking questions and giving feedback for the rest of the time."
Recurring, short review slots prevent feedback bottlenecks and create a shared understanding of what constitutes quality across the organization.
Separate Problem from Solution
From "How Miro builds product": "Product reviews can focus on different stages of the product development lifecycle: P-Strat: long-term strategy and vision; P0: the opportunity and problem that we want to pursue; P1: the proposed solution; P2: what we launched and how it’s performing."
Structure reviews into distinct stages to ensure leadership agrees on the problem and the strategic direction before teams commit to high-fidelity design work.
Operationalize Quality Mantras
From "How Miro builds product": "One of the product leaders came up with the 'Mona Lisa principle'—simply put, everything we ship should be like a Mona Lisa painting, something we’d be proud of putting our name on. . . Every month, they review everything that was shipped and say what is high-quality or not."
Use simple metaphors or principles to build intuition across the team, helping everyone understand the bar for excellence without constant oversight.
Alignment Over Sales Pitches
From "How Snowflake builds product": "The goal of a product review isn’t to “sell” the leadership team on a new investment but to detail customer requirements, align on relative business priorities, and provide a clear direction of how to address these challenges."
Format reviews as collaborative sessions focused on consistent decision-making rather than internal marketing or selling an idea to leadership.
Focus on Rigorous Problem Clarification
Tomer Cohen: "I push a lot for what is actually your opinion, what is your potentially controversial opinion and the best principles have teeth. So saying that we should build a simple product for me is useless. Who doesn't want to build a simple product?"
Reviews should be deep-dives into specific problems and principled opinions, avoiding the trap of high-level status updates that provide no strategic value.
Templates & Frameworks
- Product Review Stages (P-Strat, P0, P1, P2) (How Miro builds product) - A four-stage product review framework aligned to the product development lifecycle, each with defined templates and review criteria
- Uncertainty × Impact 2x2 Review Cadence Rubric (Five principles for successfully managing managers) - A 2x2 matrix for skip leads to determine how closely to review delegated projects based on uncertainty and impact
- Option Space (How Figma builds product) - A framework for product reviews where the presenter maps all possible solutions or problems before discussing specific directions, enabling better debate on tra
- Alignment Scale Widget (Yuhki Yamashata) - A FigJam/Figma widget that shows a spectrum where reviewers click to place their avatar, enabling quick pulse checks on alignment during product reviews
- Snowflake Product Review Document (Six-Pager) (How Snowflake builds product) - A six-page document shared one week before product reviews that outlines the customer problem, proposed solution, and key data for leadership review
- Notion's Four-Stage Product Review Process (How Notion builds product) - A structured check-in process at four key milestones in product development, replacing unstructured working sessions. Primarily async with a shift to synchronou
- Async Product Review Workflow with Talktracks (How Miro builds product) - A workflow for making product reviews more efficient by shifting presentations to async and focusing meetings on discussion
- Project Murder Board (Nabeel S. Qureshi) - A peer-review process for new projects where a 2-page plan is aggressively critiqued by smart outsiders.
See references/artifacts.md for the full list with details.
Questions to Help Users
- "What stage of the product development lifecycle is this project currently in?"
- "Have you mapped out the full range of possible solutions or are you presenting a single path?"
- "What is the specific, nuanced problem statement you are trying to solve?"
- "How does this project rank on the uncertainty versus impact matrix?"
- "Are there dissenting opinions within the team that should be surfaced during this review?"
- "What are the principled opinions that the team is bringing to this discussion?"
Common Mistakes to Flag
- Treating reviews as status updates - This wastes leadership time and fails to address strategic blockers or quality issues.
- Reviewing too late in the process - Teams become wedded to a solution, making leadership feedback feel like a demoralizing roadblock rather than guidance.
- Seeking consensus instead of alignment - Waiting for everyone to agree slows down development and often results in watered-down product decisions.
- Debating solutions before agreeing on the problem - This leads to circular arguments where stakeholders are optimizing for different goals.
Deep Dive
For all 12 sourced insights from 12 guests, see references/guest-insights.md
Related Skills
- Executive Communication
- Managing Up
- Running Meetings
- Written Communication
