End design critiques with a decision on every note

End design critiques with a decision on every note

End design critiques with a decision on every note

Design process

The short answer

A critique only helps if the feedback goes somewhere. Say what stage the work is at and what kind of feedback you need, tie every comment to the design's goals, and before people leave, give each note a decision: do it, push back, or clarify. Then tell everyone what changed and what didn't.

A critique only helps if the feedback goes somewhere. Say what stage the work is at and what kind of feedback you need, tie every comment to the design's goals, and before people leave, give each note a decision: do it, push back, or clarify. Then tell everyone what changed and what didn't.

Original mobile concept in charcoal and bright yellow-green. An app called Critique shows a session for a fictional team invite flow, marked mid-fidelity, feedback on the flow, not visuals. Goal: invite a teammate without help. Asking: does the flow meet the goal? Notes, 4 of 5 decided: Send button is below the fold (Do it, designer, next iteration). Error doesn't say how to fix it (Do it, designer, next iteration). Add a tutorial overlay (Push back, conflicts with the goal, revisit). How often do admins invite many? (Clarify, researcher, before next crit). Make it feel more premium (not yet decided; which goal does it serve?). Note: every note gets a decision before we leave; recap goes out after the session. Buttons: Add note and Send recap. Beside the phone, a dithered drawing of loose note tiles on a slab and three trays of sorted notes, with one yellow-green note being placed on the first tray. Text: Illustrative concept. Every note gets a decision. Do it, push back, or clarify.
Original mobile concept in charcoal and bright yellow-green. An app called Critique shows a session for a fictional team invite flow, marked mid-fidelity, feedback on the flow, not visuals. Goal: invite a teammate without help. Asking: does the flow meet the goal? Notes, 4 of 5 decided: Send button is below the fold (Do it, designer, next iteration). Error doesn't say how to fix it (Do it, designer, next iteration). Add a tutorial overlay (Push back, conflicts with the goal, revisit). How often do admins invite many? (Clarify, researcher, before next crit). Make it feel more premium (not yet decided; which goal does it serve?). Note: every note gets a decision before we leave; recap goes out after the session. Buttons: Add note and Send recap. Beside the phone, a dithered drawing of loose note tiles on a slab and three trays of sorted notes, with one yellow-green note being placed on the first tray. Text: Illustrative concept. Every note gets a decision. Do it, push back, or clarify.

Illustrative concept, not client work or measured results.

Feedback that goes nowhere

Most critique advice is about the meeting. NN/g's Rachel Krause looks at what comes after: in many teams the session ends and the "feedback gets filed away in a document that nobody touches again." When people never hear what happened to their input, she writes, they "learn to stop contributing."

Feedback that goes nowhere

Most critique advice is about the meeting. NN/g's Rachel Krause looks at what comes after: in many teams the session ends and the "feedback gets filed away in a document that nobody touches again." When people never hear what happened to their input, she writes, they "learn to stop contributing."

Ask for the feedback you need

Start with context. A GDS designer's post on design crits says to begin "by specifying what you want to get feedback on," including "what stage the project is at." NN/g's Sarah Gibbons adds: "reiterate the goals of the work," then ask for "what works, what doesn't, where you need input and suggestions." The GDS post calls "I don't like it" personal opinion, and "not useful." Tie each comment to a goal.

Give every note a decision

Krause's advice on derailed critiques is to sort the list into "To do," "To persuade" and "To clarify." Do that before the room empties, and put a name on each note. Then send a short recap: "what we're moving forward with, what we're still investigating, and what we've decided not to pursue." For each note you won't act on, name it, state the decision, give the reason and say what happens next.

Ask for the feedback you need

Start with context. A GDS designer's post on design crits says to begin "by specifying what you want to get feedback on," including "what stage the project is at." NN/g's Sarah Gibbons adds: "reiterate the goals of the work," then ask for "what works, what doesn't, where you need input and suggestions." The GDS post calls "I don't like it" personal opinion, and "not useful." Tie each comment to a goal.

Give every note a decision

Krause's advice on derailed critiques is to sort the list into "To do," "To persuade" and "To clarify." Do that before the room empties, and put a name on each note. Then send a short recap: "what we're moving forward with, what we're still investigating, and what we've decided not to pursue." For each note you won't act on, name it, state the decision, give the reason and say what happens next.

Illustrative concept: From notes to decisions. Critique notes sorted into three columns. Do it / To do: Send button is below the fold; Error doesn't say how to fix it; both owned by the designer for the next iteration. Push back / To push back: Add a tutorial overlay; conflicts with the goal of inviting without help; designer to revisit after testing. Clarify / To clarify: How often do admins invite many? (researcher, before next crit); Make it feel more premium (ask which goal it serves). Recap sent right after the session. Moving forward: below-the-fold fix, clearer error copy. Still investigating: how often admins invite many. Not pursuing: tutorial overlay, because it conflicts with the goal; revisit after testing.
Illustrative concept: From notes to decisions. Critique notes sorted into three columns. Do it / To do: Send button is below the fold; Error doesn't say how to fix it; both owned by the designer for the next iteration. Push back / To push back: Add a tutorial overlay; conflicts with the goal of inviting without help; designer to revisit after testing. Clarify / To clarify: How often do admins invite many? (researcher, before next crit); Make it feel more premium (ask which goal it serves). Recap sent right after the session. Moving forward: below-the-fold fix, clearer error copy. Still investigating: how often admins invite many. Not pursuing: tutorial overlay, because it conflicts with the goal; revisit after testing.
Illustrative concept: From notes to decisions. Critique notes sorted into three columns. Do it / To do: Send button is below the fold; Error doesn't say how to fix it; both owned by the designer for the next iteration. Push back / To push back: Add a tutorial overlay; conflicts with the goal of inviting without help; designer to revisit after testing. Clarify / To clarify: How often do admins invite many? (researcher, before next crit); Make it feel more premium (ask which goal it serves). Recap sent right after the session. Moving forward: below-the-fold fix, clearer error copy. Still investigating: how often admins invite many. Not pursuing: tutorial overlay, because it conflicts with the goal; revisit after testing.
Illustrative concept: From notes to decisions. Critique notes sorted into three columns. Do it / To do: Send button is below the fold; Error doesn't say how to fix it; both owned by the designer for the next iteration. Push back / To push back: Add a tutorial overlay; conflicts with the goal of inviting without help; designer to revisit after testing. Clarify / To clarify: How often do admins invite many? (researcher, before next crit); Make it feel more premium (ask which goal it serves). Recap sent right after the session. Moving forward: below-the-fold fix, clearer error copy. Still investigating: how often admins invite many. Not pursuing: tutorial overlay, because it conflicts with the goal; revisit after testing.
Illustrative concept: From notes to decisions. Critique notes sorted into three columns. Do it / To do: Send button is below the fold; Error doesn't say how to fix it; both owned by the designer for the next iteration. Push back / To push back: Add a tutorial overlay; conflicts with the goal of inviting without help; designer to revisit after testing. Clarify / To clarify: How often do admins invite many? (researcher, before next crit); Make it feel more premium (ask which goal it serves). Recap sent right after the session. Moving forward: below-the-fold fix, clearer error copy. Still investigating: how often admins invite many. Not pursuing: tutorial overlay, because it conflicts with the goal; revisit after testing.

Before your next critique

  • Share the work, its goals and its stage ahead of time.
  • Say what feedback you need, and what's out of scope.
  • Turn taste into a question about the goal.
  • Sort every note: do, persuade or clarify.
  • Send the recap right after, including what you won't change.

Before your next critique

  • Share the work, its goals and its stage ahead of time.
  • Say what feedback you need, and what's out of scope.
  • Turn taste into a question about the goal.
  • Sort every note: do, persuade or clarify.
  • Send the recap right after, including what you won't change.