Design Critique, Without the Sting

If the words design critique alone are enough to make someone on your team tense up, the critique culture at that company has probably already drifted into something closer to a personal attack. A simple “I don’t think this works” can land as an assessment of the person, not the screen. Go too far the other way, though, and you get critiques where nobody wants to hurt anyone’s feelings, so real problems never get named. A good critique lives somewhere between those two extremes — sharp judgment about the work, paired with genuine respect for the person who made it.

1. Why critique starts to feel personal

The biggest cause is feedback exchanged with no shared standard, running purely on personal taste. “I wouldn’t have done it this way” isn’t a reason — it’s a preference, and arguing with someone’s preference turns into an emotional fight almost immediately. On top of that, most designers have poured real judgment and hours into a draft, so criticism of the work is easy to hear as criticism of themselves. If whoever’s running the critique doesn’t stay aware of that psychological distance, even the best-intentioned feedback lands as a wound.

2. Agree on criteria first, then split the roles

An effective critique starts by agreeing on what the session is actually evaluating today — before a single opinion gets shared. Usability, brand consistency, technical feasibility: the same screen can get a completely different verdict depending on which lens is on the table. The Interaction Design Foundation’s framing of design critique also treats conversation grounded in criteria, not emotion, as the core of the practice.

It also helps to split the roles clearly: the presenter answers questions instead of defending, and the person giving feedback states observations instead of verdicts. “I couldn’t find this button when I first looked at the screen” lands very differently from “this button doesn’t stand out” — same point, framed as personal experience instead of judgment, and suddenly much easier to hear. This habit of observation-first feedback also pairs well with using AI as a critique assistant: once a tool has already flagged the structural issues, people have more room to focus on observing rather than judging.

3. The trap of critique that only happens in text

With remote work and async collaboration now the norm, a lot of critique happens entirely through chat threads and inline comments. The problem is that text strips out tone and expression, so the exact same sentence can land far sharper depending on the reader’s mood that day. “Why did you do it this way?” might be a plain question — or it might read as a rebuke, and there’s no way to tell which from the words alone.

Text-based critique is safer when it’s deliberately spelled out a little more than feels necessary. Adding the context — “judging this against X standard” — instead of leaving only the conclusion gives the recipient far less room to misread the intent. For anything sensitive, switching from text to a short call is often the better call entirely.

4. Too often, too rare: finding the right cadence

How often critique happens shapes the culture just as much as how it happens. Run it every single day and the team never gets enough time to actually refine anything before showing it again, which builds fatigue fast. Save it all for one session near the deadline, on the other hand, and big problems surface at the exact point where they’re hardest to fix, which escalates conflict.

The right cadence shifts with the project stage, but a reasonable default is: more frequent early on, while direction can still swing widely, and more spread out later, once the work has settled into refining details.

Closing thoughts

Junior designers are usually unpracticed at both giving critique and receiving it. Teams that skip building this muscle often end up leaning hard on an implementation-stage QA checklist instead — and still miss the problems that should have been caught back at the draft stage.

Design critique is a collaboration aimed at making the work better — not a contest over who’s right. Start small: agree on just one standard before your next critique session, before anyone shares an opinion.