A critique analyses whether a design meets its objectives. It is not a review for approval, and it is not a vote on taste.
Written as practical advice. Where a step rests on established research practice, the source is listed under References. Nothing here is a universal rule.
"This is for [user] trying to [task]. It is an early layout. I'd like feedback on the hierarchy and whether the primary action is clear. Visual polish is out of scope."
Show, do not defend. Long explanations pre-empt honest reactions.
Questions of understanding only, before any opinions.
Tied to the goal. The facilitator keeps it in scope and makes sure everyone speaks.
The presenter reads back what they heard and what they will look at. Nothing has to be agreed in the room.
Weak
What do you think?
Better
I'd like feedback on the information hierarchy and whether the primary action is clear.
Why. A specific ask gets specific feedback.
Weak
Yikes, that layout.
Better
I noticed the total sits below the fold. Someone checking the amount before paying may miss it.
Why. An observation and its impact can be acted on.
Weak
Make the button blue.
Better
The primary action reads the same weight as Cancel. Have you tried reducing the secondary one?
Why. A command ends the discussion. A question keeps it open.
Senior designer note“Critique the work against its goal, not against your taste.”
Reference