How would you structure a product review meeting?
Model answer
Model answerMost product reviews are status updates disguised as reviews. A good product review is about decisions, not reports. Structure: 10 minutes on what changed since last time and why, 20 minutes on the hardest open question the team is facing, 15 minutes on what we're shipping next and the hypothesis behind it, 5 minutes on what we're stopping. The PM's job is to facilitate, not to present.
Framework · Communication Framework
- DDecisions, not reports
Every agenda item should end with a decision or a clear owner of a decision - HHardest question first
Put the most ambiguous problem in the room while energy is highest - SShip and stop
What's going out and what's being cut? Both need air time - AAsync pre-read
Send context ahead — the meeting is for discussion, not information delivery
Related questions
- How would you prioritize building for power users vs. new users?
- A major competitor just launched a feature you were building. What do you do?
- How do you align stakeholders when they disagree on the roadmap?
- How would you evaluate the ROI of a product investment before building it?
- How would you evaluate a potential acquisition target from a product perspective?