How to run a design critique as a product manager requires separating observation from opinion, grounding all feedback in user goals and product principles, and closing with a clear decision or next step — not a list of competing preferences.
Design critiques fail when they become opinion markets. Everyone shares what they like or dislike, the designer walks away with 11 contradictory notes, and nothing improves. A PM-led critique should produce one of three outputs: a clear decision, a list of specific questions the team needs to answer before deciding, or validated design direction with no open blockers.
This framework gives you a repeatable critique process that respects design craft while keeping product goals central.
The PM's Role in a Design Critique
You are not the creative director. Your job is to:
- Ensure the design is evaluated against the right criteria (user goals, product principles, business constraints)
- Prevent the room from optimizing for aesthetics over outcomes
- Drive to a decision — not more iteration for iteration's sake
- Protect the designer from receiving feedback that is really about disagreements in strategy, not design
According to Lenny Rachitsky's writing on PM-design collaboration, the most damaging thing a PM can do in a design critique is treat it as a status check. The critique is a working session, not a review meeting.
Pre-Critique Setup (10 Minutes Before)
H3: Share the Brief in Advance
Send the following before the session:
- Problem statement: What user problem does this design solve?
- User goal: What is the user trying to accomplish?
- Success metric: How will we know if this design works?
- Constraints: Technical, time, accessibility, brand
Without the brief, feedback defaults to personal preference. With it, all feedback can be evaluated against shared criteria.
H3: Set the Format
Three critique formats and when to use them:
| Format | Use When | Duration | |--------|----------|----------| | Silent review first | Complex or contentious work — prevents anchoring | 10 min silent, 30 min discussion | | Structured walkthrough | Designer needs to explain context before feedback | 15 min walkthrough, 25 min feedback | | Hot critique | Quick feedback on a specific decision | 20 minutes total |
The Critique Framework
H3: Step 1 — Observations Only (5 Minutes)
Start with observations, not opinions. Ask the room: "What do you notice?" Not "What do you think?"
Observations are factual: "The CTA appears below the fold on mobile." Opinions are evaluative: "The CTA placement is bad."
This step trains the room to separate what exists from what they value.
H3: Step 2 — Connect to User Goal (10 Minutes)
For each major design decision, ask: "Does this help the user accomplish [stated goal]?"
Frame all feedback against the user goal, not personal preference:
- Instead of: "I don't like the navigation pattern"
- Use: "Will users who are [user type] know how to get to [action] from this navigation?"
H3: Step 3 — Identify Open Questions (10 Minutes)
The best critiques surface questions the design hasn't answered yet:
- "What happens when the user has zero items in this list?"
- "What does this look like in RTL languages?"
- "How does a new user experience this versus a returning user?"
Capture these as explicit questions, not design changes. The designer may have already solved them in another screen.
H3: Step 4 — Prioritize Feedback (5 Minutes)
Not all feedback is equal. Categorize before the session ends:
- P0 — Blockers: Design cannot ship as-is (accessibility failure, missing user flow, incorrect behavior)
- P1 — Strong recommendations: Should be addressed in this iteration
- P2 — Consider: Worth exploring if time allows
- P3 — Future: Out of scope for this version, log it somewhere
According to Annie Pearl on Lenny's Podcast, the most important discipline in a design critique is distinguishing between feedback that addresses the problem statement and feedback that addresses taste. Taste feedback belongs in P3 or nowhere.
Common PM Critique Dysfunctions
H3: The HiPPO Trap
The highest-paid person in the room (HiPPO) shares their opinion and the room collapses around it. Countermeasures:
- Ask the HiPPO to go last, not first
- Respond to all opinions with: "Does that address the user goal? What's the evidence?"
- Name the dynamic explicitly if needed: "Let's make sure we're evaluating this against the brief, not personal preference"
H3: Scope Creep Feedback
"While we're at it, we should also redesign the…" This happens in every critique. Shut it down explicitly: "That's a separate problem — let's add it to the backlog and stay focused on what we're solving today."
H3: The "Make It Pop" Feedback
Vague aesthetic feedback with no connection to user goals. Respond with: "What specific user behavior are we trying to drive with that change?" If they can't answer, the feedback is taste, not signal.
According to Shreyas Doshi on Lenny's Podcast, the proxy for good critique culture is whether the designer leaves the room energized or demoralized. Productive critique is specific, grounded in user goals, and ends with clear next steps — not a pile of unranked opinions.
Closing a Design Critique
Never end a critique without one of:
- Decision: "We're going with option B. Designer to update the prototype by [date]."
- Open questions: "We have 3 questions to answer before we can decide. [Name] owns each one by [date]."
- Validated direction: "Design direction is approved. No blockers. Moving to build."
FAQ
Q: What is a design critique in product management? A: A structured working session where a product team evaluates a design against user goals and product principles, producing a decision or clear next steps — not a list of competing preferences.
Q: How should a PM give feedback in a design critique? A: Ground all feedback in the user goal and stated success metric. Separate observations from opinions. Prioritize feedback as blocker, recommendation, or future consideration.
Q: How do you prevent opinion-driven design critiques? A: Share the design brief in advance so all feedback is evaluated against shared criteria. Start the session with observations-only before moving to opinions.
Q: What should a design critique produce? A: One of three outputs: a clear decision, a list of specific questions to answer before deciding, or validated design direction with no open blockers.
Q: How long should a PM-led design critique take? A: 20–40 minutes for most feature-level critiques. Complex or high-stakes designs may warrant 60 minutes with a structured pre-read.
HowTo: Run a Design Critique as a Product Manager
- Share the design brief in advance including the problem statement, user goal, success metric, and constraints so all feedback can be evaluated against shared criteria
- Open the session with observations only — ask what participants notice, not what they think, to separate facts from opinions
- Connect every major design decision to the user goal by asking whether it helps the user accomplish the stated task
- Identify open questions the design has not yet answered and capture them explicitly for the designer to address
- Prioritize all feedback as P0 blocker, P1 strong recommendation, P2 consider, or P3 future before closing
- Close with a decision, a set of owned open questions with due dates, or explicit validation of the design direction — never leave without a clear next step