What I Learned from 50 Design Critiques

I have sat through fifty design critiques in the past two years — some brilliant, some brutal, most somewhere in the middle. I have facilitated critiques for teams of three and teams of thirty. I have been the presenter sweating through a review of work I knew was unfinished, and I have been the senior designer struggling to articulate why a layout felt wrong without resorting to "I just don't like it." Through all of these sessions, I have developed a conviction that critique is the most important skill a design team can cultivate, and also the most neglected. We teach designers to use tools, to think in systems, to conduct research — but we rarely teach them how to talk about each other's work in a way that makes it better.

The first distinction I had to learn was the difference between critique and feedback. Feedback is reactive and personal: "I like it," "It feels off," "Can you make the logo bigger?" Critique is structured and analytical. It starts with observation, moves to interpretation, and arrives at evaluation. When someone in a critique session says "I don't like the color," they have skipped three essential steps. What they should say is: "The color palette uses warm tones throughout, which creates an informal, friendly mood. Given that this is a banking application aimed at high-net-worth clients, that mood may conflict with the brand's positioning around trust and sophistication. Consider whether a cooler palette might better serve the intended audience." That is the difference between noise and signal.

Design review in progress — sticky notes and strong opinions

I formalized this into a framework I call DAIE: Describe, Analyze, Interpret, Evaluate. In the Describe phase, you say only what you see — no judgments, no suggestions. "There is a large hero image, a centered headline in serif type, and a single call-to-action button below the fold." In Analyze, you examine the relationships: "The headline and the image compete for attention because they have similar visual weight." In Interpret, you infer intent: "It seems like the goal is to create an emotional first impression before driving the user to sign up." In Evaluate, you finally assess: "The emotional impact works, but the CTA may be too far from the entry point for users who arrive with high intent." This sequence forces participants to build a shared understanding before jumping to opinions, and it has transformed the quality of every critique I have run since adopting it.

The shift to remote work fundamentally changed how I think about critiques. In-person sessions had a natural energy — the whiteboard, the sticky notes, the ability to read body language and gauge when the presenter was overwhelmed. When my team went async-first in 2023, I was initially skeptical. But I discovered that asynchronous critique, when done well, produces more thoughtful and equitable feedback. The loudest voice in the room no longer dominates. Introverted designers who would never speak up in a live session write paragraphs of incisive commentary when given time to think. We now run critiques as annotated Figma files with a 48-hour comment window, followed by a 30-minute synchronous debrief to resolve disagreements. The quality of the feedback improved dramatically, and participation became nearly universal.

Async critique on Figma — comments replacing meetings

What critique has taught me most, though, is about my own blind spots. After fifty sessions, I can see patterns in the feedback I receive. I consistently under-invest in mobile layouts. I reach for animation as a crutch when the static design is not strong enough. I default to center-aligned text even when left-alignment would improve readability. These are not flaws I could have identified alone — they are visible only through the accumulated perspective of dozens of thoughtful colleagues. Critique culture also varies significantly between design communities. In Seoul, where I spent three years, critique tends to be indirect and consensus-driven. In San Francisco, it is more confrontational and individual. Neither approach is superior, but understanding these cultural norms is essential for facilitating sessions across distributed teams. The best critiques I have run borrowed from both traditions: the directness of American design culture tempered by the respect for group harmony that I learned in Korea.

The facilitator is the unsung hero of any critique session. A good facilitator sets the rules, manages time, redirects vague feedback into structured observation, and protects the presenter from pile-on dynamics. I have seen facilitators save sessions that were devolving into arguments, and I have seen the absence of facilitation destroy team trust in a single afternoon. If I could change one thing about design education, it would be to make critique facilitation a required course. The tools will change. The pixels will change. But the need to talk about work honestly and constructively — that endures.