Design Critique and Feedback: Goodwin's and IDEO's Mechanics (2026)

The structure of a working design critique

The canonical structure of a working design critique drawn from Kim Goodwin's Designing for the Digital Age (chapter 25), the IDEO and Cooper-school heritage, and the publicly-discussed critique mechanics from senior designers at Apple, Airbnb, Stripe, and Figma:

1. Cadence: weekly, fixed time, 60–90 min. Same time every week. Don't cancel except in unusual circumstances. The cadence creates the rhythm that makes critique habitual rather than performative.
2. Pre-reads: 24 hours before. Each designer presenting sends a structured pre-read 24 hours ahead: the design problem, the user, the constraints, the design intent, the artifacts, the specific feedback they're seeking. The pre-read prevents the critique from being a 5-minute setup followed by 10 minutes of feedback.
3. Agenda: 3–4 designs per session. 15–25 min per design. A 60-min critique with 3 designs has 5–10 min for opening / wrapping plus 50–55 min for design discussion. Discipline on agenda prevents critique-creep.
4. Opening: 5 min. The design manager (or rotating critique facilitator) opens with the agenda, the principle ('today we're focusing on early-stage feedback' or 'today is shipping-readiness'), and the time-boxing.
5. Per-design structure (15–25 min):
   • Designer presents: 5–7 min. State the design problem, the user, the constraints, the design intent, the specific feedback you're seeking.
   • Clarifying questions: 2–3 min. Reviewers ask only clarifying questions, not feedback questions.
   • Feedback: 8–13 min. Reviewers offer feedback using the equation (observation + impact + question or request). The designer listens, takes notes, doesn't defend.
   • Wrap: 1–2 min. Designer summarizes what they're taking away and what they'll explore.
6. Closing: 5 min. The facilitator wraps with any team-level observations and any process-level adjustments for the next session.

The IDEO pattern: problem-finding before problem-solving

The most-cited critique-mechanic in IDEO and Cooper-school heritage is the separation of problem-finding from problem-solving. The mechanics:

1. The designer presents the design intent first. Not 'here's a button, what do you think?' Instead: 'I'm trying to help users complete the upgrade flow with confidence. The design intent is to make the price and the upgrade benefit clear before the action button. Here's the artifact.' The intent framing makes the critique a conversation about whether the design serves the intent, not a conversation about whether reviewers like the artifact.
2. Reviewers offer problem-finding first. 'I notice the price is below the benefit list — is that intentional?' Not: 'I would move the price above the benefit list.' Problem-finding feedback is observable; problem-solving feedback is prescriptive. The IDEO pattern is to spend 80% of feedback time on problem-finding.
3. The designer takes the problem-solving back. The designer either discusses problem-solving in the critique (briefly) or takes it back to a follow-up working session. The failure mode is the critique that becomes a group-design-session — the resulting design has no owner because the design decisions were made by committee.
4. Disagreement is named explicitly. When two reviewers offer conflicting feedback, the facilitator names the disagreement and asks the designer how they'll think about it. Resolution doesn't have to happen in critique; it has to happen before shipping.

The IDEO pattern works because design decisions are owned by the designer (or by the design-product-engineering triad), not by the critique panel. The panel surfaces concerns; the designer integrates them.

Hogan's feedback equation applied to design feedback

Hogan's feedback equation (observation + impact + question or request) applied to design feedback works well. Examples drawn from canonical design-critique patterns:

• Type hierarchy. Observation: 'I notice the type-hierarchy in this card design treats the title and the body at similar visual weight.' Impact: 'It might make scanning the card list slow for users in the dashboard view.' Request: 'Can we explore reducing the body weight by one step, or increasing the title size?'
• Information density. Observation: 'The dashboard has 14 metrics on the primary view.' Impact: 'For the user persona we identified — small-business owners checking weekly — that's likely too much for the primary view.' Request: 'Can we discuss what the top 3–5 metrics are and what could move to a secondary view?'
• Motion. Observation: 'The transition between the list view and the detail view is 600ms.' Impact: 'For users navigating quickly between items, that might feel slow.' Request: 'Can we test 300ms and see if the spatial-orientation cue still reads?'
• Consistency with design system. Observation: 'The button on the upgrade flow uses a custom green that doesn't match our design-system primary action.' Impact: 'It might look like a marketing CTA rather than a product action, which could confuse users.' Request: 'Was the off-system color intentional, or can we use the design-system primary?'

The equation works for any kind of design feedback. The mistakes new reviewers make:

• Skipping the observation. 'I don't like the color' — no observation, no specific reference, no actionable feedback.
• Skipping the impact. 'The color is bright green' — observation but no impact, so the designer doesn't know what to do with the feedback.
• Skipping the question. 'The color is bright green and might confuse users' — observation and impact but no question, so the designer doesn't know whether you want them to explore alternatives or just acknowledge.
• Combining problem-solving with feedback. 'You should change the color to our design-system primary' — prescriptive, takes the design decision away from the designer, and short-circuits the problem-finding step.

The failure modes of design critique

1. Critique-as-gallery-walk. Designers present their work, reviewers nod and say 'looks good,' and no specific feedback is delivered. The critique provides no value. The cause is usually no time-boxing and no expectation of structured feedback. The fix is the equation and explicit pre-reads.
2. Critique-as-design-by-committee. Reviewers offer prescriptive problem-solving feedback ('I would move the button up') and the designer accumulates contradictory directives. The resulting design has no owner. The fix is the IDEO pattern: problem-finding before problem-solving.
3. The manager dominates. The design manager offers feedback first, then everyone else aligns to the manager's perspective. The team's IC voices are silenced. The fix is for the design manager to speak last (or not at all) in critique. Bob Baxley's 'Direct Care' essay names this pattern explicitly.
4. Time runs over. Critique starts at 60 min, runs to 90 min, then 100 min. The team learns that the manager doesn't respect their calendar. The fix is rigorous time-boxing — set timers, signal the 80% mark, end on time.
5. The defensive designer. The designer presenting defends every piece of feedback rather than listening. The team learns that critique is a debate, not a feedback channel. The fix is for the design manager to coach the presenting designer privately before critique on listening posture.
6. The hostile reviewer. A reviewer offers feedback in a personal or aggressive tone. The team disengages. The fix is for the design manager to address the reviewer privately and to coach the team on the equation as the standard delivery mechanic.
7. Critique-without-pre-reads. Designers present cold; reviewers spend the first 5 min trying to understand the context; the critique runs over because of the slow start. The fix is enforcing pre-reads 24 hours ahead.