Product Reviews
Help users design and facilitate product reviews that shift from status updates to...
Install
npx skills add RefoundAI/lenny-skills --skill product-reviews -g -a claude-code -y- Repository
- RefoundAI/lenny-skills1.5k
- Category
- Design
- Updated
- 4mo ago
- License
- MIT
- Context cost
- Mediumabout 1,708 tokens
- Runs scripts
- No, instructions only
What it does
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
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.


