Design Critiques & Feedback
Part of the UI/UX Design Roadmap
In short
A good critique session turns six opinions into one clearer design. A bad one turns into a debate about favourite colours. The difference is how the session is run.
Structured sessions where a design is reviewed by peers — applying Phase 7's critique skills in a live group setting, both giving and receiving feedback productively.
Think of it like this
The team talk at the drinks break
In the drinks break, the captain doesn't let everyone shout at once. He says what the target is, asks the bowlers what's working, decides one change and sends them back. A design critique needs the same structure.
Watch it happen
Running a 30-minute critique
1/4The designer shares the goal, users, constraints and what kind of feedback they want today.
The big ideas
What you need to know
Ask for specific feedback
'I need feedback on the checkout flow, not visuals' focuses the session.
Keep it regular
A weekly critique slot makes feedback normal, not scary.
Have a facilitator
Someone other than the presenter keeps time and stops debates from going in circles.
Designer decides
Critique gives input. The designer and team decide what to act on, not the loudest person.
Save yourself the pain
Common mistakes
Oops
Presenting the work and asking 'thoughts?'
Do this instead
Share the goal and the kind of feedback you need. Open questions get scattered answers.
Oops
Turning critique into approval meetings with managers.
Do this instead
Keep critiques for improving the work. Approvals are a separate meeting with different people.
Your mission
Run a mini critique
Quick check
Why start a critique with a few minutes of silent review?
Go deeper
- 1Participate in or organize a design critique session, even informally with peers.
- 2Practice presenting your own work concisely: context, goal, and the specific feedback you need.
- 3Learn to receive critical feedback without becoming defensive — it's about the work, not you.
More topics at this stop
Working With Product Managers
Working With Engineers
Design Handoff Best Practices
Design QA (Reviewing Built Features)
Version Control for Design (Figma Branching)
Presenting Design Work to Stakeholders
Design Documentation
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
