Design critique is a structured session where a team gives focused feedback on work in progress — and it’s one of the cheapest, highest-leverage ways to raise design quality. Done well, it catches problems while they’re still easy to change. Done badly, it’s a demoralising round of opinions that makes the work worse and the designer defensive. The difference is almost entirely in how you run it.
Critique is the feedback loop at the heart of design operations. If quality keeps slipping through the cracks, a working critique is usually the fastest fix — faster and cheaper than another hire.
What is design critique?
Critique is feedback on work against its goals, not against personal taste. It’s not an approval meeting, and it’s not design-by-committee. The designer brings work in progress and a clear question; the group helps them see it more clearly and spot problems they’re too close to notice. Nobody redesigns it for them. The output isn’t a verdict — it’s a sharper next step.
Why design critique matters
Because it makes quality a habit instead of a hope. Problems caught in critique cost minutes to fix; the same problems caught after engineering has built them cost days. A regular critique keeps the whole team’s standard aligned, spreads good thinking, and stops small inconsistencies from compounding into an incoherent product. It’s the loop that turns a group of capable designers into a team that reliably produces good work.
How to run a design critique
A simple, repeatable format beats an elaborate one. Run it like this:
- Set the frame — the designer states the goal, the audience and the specific question they want feedback on
- Give people a moment to look — a few silent minutes to actually absorb the work before anyone reacts
- Feedback against the goal — the group responds to the stated question first, describing problems, not prescribing solutions
- Designer listens, then clarifies — they capture feedback without defending; questions come after
- Close with next steps — the designer summarises what they’ll act on, so the session ends in a decision, not a discussion
Keep it short and frequent — a focused 30–45 minutes weekly does more than a marathon review once a month.
Rules for good critique
- Critique the work, not the person — always about the design, never about the designer
- Tie every comment to a goal — “this makes the primary action harder to find,” not “I’d make it blue”
- Describe problems, don’t prescribe solutions — leave the fix to the designer; they own the work
- Ask before you assert — understand the intent before reacting to the result
- Separate critique from approval — nobody has to sign anything off; that’s a different meeting
Common critique mistakes
- Turning it into approval — when a verdict is at stake, honesty evaporates and so does the value
- Design by committee — the group redesigns the work instead of helping the designer see it
- Taste dressed up as feedback — preferences stated as facts, with no tie to the goal
- No goal set — without a stated question, feedback scatters and nothing lands
- Too rare, too high-stakes — infrequent reviews put too much weight on one meeting
Critique and design operations
A good critique doesn’t stand alone — it’s one gear in a larger machine. It works best alongside a design system (so feedback is about decisions, not re-drawing components) and real project management (so critique happens at the right moment, not too late to matter). Together they’re why a team with strong operations out-designs a bigger team without them — the same reason more designers won’t fix quality on their own.
Frequently asked questions
What is design critique?
Design critique is a structured session where a team gives focused feedback on work in progress, against the goals of the work rather than personal taste. It’s not an approval meeting and not a design-by-committee session — it’s a feedback loop that catches problems early, while they’re still cheap to fix.
How often should you run design critique?
Regularly and lightly beats rarely and heavily. A short, recurring critique — weekly for most teams — keeps feedback flowing while decisions are still open. The goal is a steady loop, not an occasional high-stakes review where too much rides on one meeting.
How do you give good design feedback?
Tie every comment to the goal of the work, not your preference. Ask what the designer is trying to achieve before reacting, describe the problem you see rather than prescribing a solution, and be specific. Good feedback makes the work better and leaves the designer clearer on what to do next.
What’s the difference between critique and design approval?
Critique improves the work; approval decides whether it ships. Critique happens while decisions are still open, is exploratory, and doesn’t need a verdict. Approval is a gate with an owner. Confusing the two turns critique into a nerve-wracking sign-off and kills the honest feedback that makes it valuable.