Giving and Receiving Design Feedback: Practical Frameworks for Useful Critiques
How to give and receive design feedback with SBI and Radical Candor, how to prepare a team critique, and the mistakes designers make when critiquing.
What does it mean to give and receive feedback in design?
Giving feedback means saying what works, what does not, and why, against a goal the team has already agreed on. Receiving it means listening to that opinion without defending the screen at all costs, but also without accepting everything that is said. They are two different skills, and both are worth practicing.
Nielsen Norman Group separates two formats that are worth not confusing:
- Design critique: a conversation to improve a work in progress. It has a presenter, critics, a facilitator, and a note-taker.
- Design review: an evaluation against heuristics or criteria, often done by an expert or to approve a deliverable.
Mixing them up creates the wrong expectations: the presenter wants help improving the work and gets a verdict, or the other way around.
Why does this matter for a junior designer?
Because feedback is one of the fastest ways to grow, and one of the hardest to ask for. A junior who does not know how to request a specific critique receives vague comments like “I don’t love it” or “let’s try something else”, which do not help anyone decide.
Design feedback is also usually given in a group. Knowing how to do it without humiliating anyone or turning the session into a debate about taste keeps the conversation on the product.
Which frameworks help you give feedback?
SBI (Situation, Behavior, Impact). The Center for Creative Leadership presents it as a research-based method. It has three parts:
- Situation: when and where it happened, with concrete detail.
- Behavior: what was observed, without interpretation or judgment.
- Impact: what effect it had, on the user, the project, or the team.
Illustrative example: “In yesterday’s review (situation), when you showed the payment flow without the confirmation step (behavior), the support team did not understand what had been charged (impact).” This sentence is hard to dispute because it describes facts, not intentions.
CCL also proposes a variant, SBII, which adds an intent step: asking the other person what they meant to achieve before you share your reading. That turns the feedback into a two-way conversation.
Radical Candor. Kim Scott organizes it on two axes: care personally and challenge directly. Crossing them gives four quadrants:
| Quadrant | What it means |
|---|---|
| Radical Candor | You care about the person and challenge them directly. This is the goal. |
| Ruinous Empathy | You care about the person, but stay quiet or sugar-coat what needs to be said. |
| Obnoxious Aggression | You challenge without showing you care about the person. |
| Manipulative Insincerity | You neither care nor challenge: flattery up front, criticism behind their back. |
According to Radical Candor, these are behaviors anyone falls into at times, not personality types, and the framework asks you not to write anyone’s name in these boxes. That makes it easier to review your own conduct without labeling yourself.
How do you prepare a team critique?
Figma describes six critique formats: standard, jams or workshops, pair, silent, paper or printed, and FYI. Any of them works if you choose it on purpose. These are the common steps the sources recommend:
- Define who and what for. Nielsen Norman Group recommends agreeing in advance on the people involved and the design goals.
- Ask for specific help. Figma recommends that the presenter says what they need: a flow review, a hierarchy check, a text review?
- Assign a note-taker. That lets the presenter listen without having to write everything down.
- Use turns. Figma suggests that each person speak for about two minutes in round-the-room format. Nielsen Norman Group proposes a round-robin format, with an example quota of two positive comments and one improvement per person.
- Close with agreements. End with what the presenter will change and what stays open.
NN/g lists sessions that run too long as a pitfall. Figma, for its part, caps each session at a maximum of two topics per hour.
How do you receive feedback without getting defensive?
- Before you respond, ask what goal the comment is trying to meet. Nielsen Norman Group recommends that critics frame feedback around design goals, not personal taste. If a comment has no goal, ask for one.
- Take notes, not justifications. Write down what was said. You can defend your decision later, if needed.
- Separate opinion from data. “This looks ugly to me” is an opinion. “Users could not find the button in testing” is data, even when it comes disguised as criticism.
- Ask for an example. If someone says the flow is confusing, ask which step loses people.
Figma also recommends being vulnerable: when the presenter shows it is fine to get things wrong, everyone else feels more comfortable speaking frankly.
When should you NOT run a critique?
- To decide the product or the roadmap. Figma is explicit that a critique is not the forum for product or roadmap decisions: it exists to improve the design.
- When the problem is about the person. A design critique is not a tool for assessing performance. The article on career plans and performance evaluation covers that difference.
- When there is nothing to show. Asking for feedback on an idea with no form only produces opinions about taste.
If you want to go deeper into the format of the session, see the design critiques page. For the people-management side, the people management page covers how to sustain these conversations on a team.
Example
Illustrative example: a junior designer presents a sign-up screen. The first comment is “I don’t like the flow.”
With a facilitator using SBI, the conversation changes:
- Question: what is the sign-up’s goal for this product?
- Answer: most users should finish account creation in under two minutes.
- Concrete feedback: “In testing, three of five people stopped at the postal code field (behavior). That makes sign-up longer and may lead them to abandon it (impact).”
- Agreement: the presenter tests two versions of the field and brings them to the next critique.
No comment about taste disappeared completely, but it now sits under a goal.
Common mistakes
- Giving feedback without a goal: “it looks better this way” does not say why.
- Judging the solution before understanding the problem.
- Giving only negative comments, which leaves the presenter not knowing what works.
- Taking feedback personally and answering with justifications instead of questions.
- Running a review when the session should have been a critique, or the reverse.
- Commenting on the person instead of the work.
Sources
- Nielsen Norman Group, Design Critiques
- Figma, Design critiques at Figma
- Center for Creative Leadership, Closing the gap between intent and impact
- Radical Candor, Our approach