Marcus Andrey Study
Ler em português Library

UX Foundations · Step 8 · 5 min read

Design critique in practice

Showing unfinished work to colleagues is uncomfortable, and it's the fastest way to improve it. What a design critique is and how it differs from general feedback, how to present your work, how to give comments linked to goals, and a simple format your team can start next week.

"I don't like it" is a reaction, not a critique. Everyone has opinions about design, and most of them are about taste. A critique turns opinions into something useful: it asks whether the design does what it set out to do, for the people it's meant for. Done well, it's the cheapest way to catch problems before users do, and it makes a team better at talking about design.

What you'll be able to do after reading:

  • Tell a critique from general feedback
  • Present your work so you get useful comments
  • Give comments linked to goals, not taste
  • Run a short, regular critique with your team

1. Critique versus feedback

NN/g defines design critique as "analyzing a design, and giving feedback on whether it meets its objectives", and adds: "It does not mean simply judging a design" (NN/g, Gibbons, Design Critiques: Encourage a Positive Culture to Improve Products, 2016).

In this course we use the words like this: feedback is any reaction to a design ("nice", "too busy", "make the logo bigger"). Critique is feedback tied to a goal, a user and a reason. The difference is easy to hear:

Feedback Critique
"I don't like the green." "The green button and the green success message look the same; people may think they've already paid."
"It's too busy." "The goal is a quick sign-up, but the eye goes to the three promotions before the form."
"Move the button to the right." "On mobile, the main button is far from the thumb; could it sit at the bottom?"

NN/g's article gives a similar example. Instead of "I love those colors, but I think that button is in the wrong spot and the overall page looks busy", it suggests: "If the goal is to have the user register quickly, I'm concerned we are placing emphasis on the wrong elements and hiding the primary task by making the button hard to find."


2. Three things every critique needs

The same NN/g article names three themes of effective critiques:

  1. "Clear scope for the conversation." Say what is open for comment (the flow? the wording?) and what is not (the colours are from the brand, and fixed).
  2. "Agreed-upon design objectives for the work." Without a shared goal and users, comments are just taste. Bring your problem statement; see Problem statements and "How might we".
  3. "Conversation rather than command." Comments are questions and observations, not orders.

There are two roles: the presenter, who shares the work, and the critiquers, who comment. A facilitator keeps time, keeps comments on scope and makes sure notes are taken.


3. Receiving critique: how to present

  1. 1Set the goal

    Which problem, which users, what kind of feedback.

  2. 2Show quickly

    Tell the story in a few minutes; don't defend.

  3. 3Go round

    Each person speaks in turn, linked to the goal.

  4. 4Write it down

    Notes everyone can see; no solving on the spot.

  5. 5Follow up

    Share what you'll change and why.

A design critique in five steps. The goal comes first, so every comment has something to be measured against. Diagram: Marcus Andrey, CC BY 4.0.

NN/g's advice for presenters (same article):

  • Repeat the objectives: the problem, the users, the task.
  • Tell a story: where you started, what you learned, what you decided.
  • Present quickly: don't defend every choice; let people see the work as a user would.
  • Ask for specific feedback: "I'm unsure whether people will notice the delivery date."

Then listen. Write comments down, ask questions to understand them, and decide later. You don't have to agree with everything, and you don't have to answer on the spot.


4. Giving critique

  • Start from the goal: "If the goal is X, then…"
  • Describe what you see before judging: "My eye goes first to…"
  • Ask before suggesting: "What led you to put the filters on the right?"
  • Name what works too. NN/g lists "talking only about the negatives" among the pitfalls.
  • Don't redesign in the room. "Rushing to problem solve in the moment" is another pitfall in the same list.

A simple way to balance comments is Rose, Thorn, Bud: what's working (rose), what's painful (thorn), what's promising (bud). For the facilitation side, see Design critique.


5. Common mistakes

  • No goal agreed beforehand, so every comment is taste.
  • Critique sessions that are too long, or too rare.
  • Taking comments personally, or defending instead of listening.
  • Solving every problem in the meeting.
  • Only senior people speak; everyone else stays quiet.

6. Vocabulary

Term Meaning
Feedback Any reaction to a design
Critique Feedback tied to the design's goals, users and reasons
Presenter The person who shares the work
Facilitator The person who runs the session and keeps it on scope
Scope What is open for comment in this session
Round robin Everyone speaks in turn, around the table

7. Try it (no tools needed)

  1. Pick any screen: an app, a poster, a ticket machine. Write its goal in one sentence ("help a tourist buy a one-day ticket fast").
  2. Write three comments about it as plain feedback ("too cluttered").
  3. Rewrite each one as a critique: goal, what you see, why it matters for the user.
  4. Add one rose, one thorn and one bud.

Reflection questions: Which of your first comments were really about taste? How did linking them to the goal change what you'd suggest?


8. If you already practise

  • NN/g suggests starting small: "Try dedicating 30 minutes a week to a round-robin critique" of one project.
  • Send the work and the scope before the session, so people come with considered comments instead of first reactions.
  • Rotate the facilitator role; it spreads the skill and stops one voice dominating.
  • Invite a developer or a content designer now and then; critique works best across disciplines.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Design critique · Rose, Thorn, Bud · Heuristic evaluation · How people think · Case studies and your portfolio

Saved only on this device.

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