Marcus Andrey Study
Ler em português Library

Framework · People leadership · 3 min read

Design critique

A structured session where designers give feedback on work against goals and principles, kept separate from approval, so the work improves without anyone defending their taste.

  1. 5 min
    Frame

    Presenter states context, goal, stage and the feedback they want

  2. 5 min
    Silent review

    Everyone writes questions and observations

  3. 10 min
    Clarify

    Clarifying questions only, no opinions yet

  4. 20 min
    Feedback

    Against goals and principles: I like / I wish / What if

  5. 5 min
    Summarise

    Presenter says what they will take away

  6. 15 min
    Patterns

    Second presenter, or "Have other teams solved this?"

About 60 minutes in total · every two weeks · works best with 4–12 designers

A cross-team design critique: understand the work first, then give feedback against goals, and leave decisions to a separate review.

Use it when

  • Designers on different product teams solve the same problem in different ways and never see each other's work.
  • Feedback in your reviews sounds like "I don't like the blue" instead of "Does this help operators find exceptions faster?"
  • Junior designers wait until work is polished before anyone sees it.

How to use it

  1. Set the roles. One presenter, one facilitator who keeps time, and everyone else as reviewers. Rotate the facilitator. Output: named roles for each session.
  2. Have the presenter frame the work. They state the context, the goal, the stage (early idea or near handoff) and what feedback they want. Output: a clear question the group will answer. About 5 minutes.
  3. Review in silence, then clarify. Everyone looks at the work and writes questions and observations. Then the group asks clarifying questions only, no opinions yet. Output: a shared understanding of the work before anyone judges it.
  4. Give feedback against goals and principles. Link each comment to the stated goal or to your Design principles. Use "I like / I wish / What if" to keep it specific and open. Output: a set of comments tied to the goal. About 20 minutes.
  5. Let the presenter summarise. The presenter says what they will take away. They decide what to change; the group doesn't vote. Output: the presenter's own list of next steps.
  6. Look for patterns across teams. Use the last part to ask "Have other teams solved this?" Output: shared patterns and connections between designers.

Worked example

A cross-team critique on an internal operations platform, every two weeks for 60 minutes.

Time What happens
0–5 The presenter shows a new exception list. Goal: operators find late orders in under a minute. Stage: early. Feedback wanted: "Is the grouping clear?"
5–10 Silent review. Reviewers write notes.
10–20 Clarifying questions: "How many exceptions does a typical operator see per shift?"
20–40 Feedback: "I like that late orders sort first. I wish the grouping label said why an order is late. What if the filter remembered the last view?"
40–45 The presenter takes away two changes and one question to test with operators.
45–60 Pattern spotting: another designer shows a similar grouping from the warehouse team's tool.

Watch out for

  • Critique as approval. If a senior person says "ship it" or "no" in the room, it has become a review. Make the decision in a separate meeting.
  • Taste instead of goals. "I'd use a different font" helps nobody. Ask the reviewer which goal or principle it affects.
  • Solutions too early. Jumping to "just add a tab" before clarifying questions skips understanding. Hold suggestions until step 4.
  • Loudest voice wins. Silent review and written notes give quiet designers the same space. Techniques like 1-2-4-All help too.

Template

Send this to the presenter the day before.

Presenter:                    Facilitator:
Context:      (product, users, problem)
Goal:         (what this design must achieve)
Stage:        early idea / in progress / near handoff
Feedback I want:
Feedback I don't need now:

Agenda (60 min)
  5   Presenter frames the work
  5   Silent review (notes)
  10  Clarifying questions only
  20  Feedback: I like / I wish / What if
  5   Presenter summarises takeaways
  15  Second presenter or pattern spotting

Takeaways (presenter):
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close