A Better Critique Session Starts with One Shared Question

The most common critique mistake is asking, “What do you think?” A better critique session starts with one shared question, because an open invitation tends to produce a pile of unrelated preferences and leaves the designer to guess what matters.

That cost is easy to miss. Someone praises the color, another dislikes the type, and a third suggests a new feature; the work has been discussed, but its central uncertainty remains untouched. A focused question gives the group a subject, not a verdict.

What does a shared critique question do?

A shared question names the decision the team needs to understand. It might ask whether the layout makes the next action apparent, whether a package shape reads as portable, or whether a physical control is easy to distinguish by touch. Participants then report what they notice in relation to that question.

The question is not a disguised request for approval. “Do you like this?” invites taste, while “Which element draws your eye before you notice the instructions?” invites an observable account. That distinction does not make taste irrelevant; it keeps taste from pretending to be evidence about every other concern.

A useful question is narrow enough to focus attention and open enough to allow an unexpected answer. If it already contains the preferred solution, the critique becomes a vote on that solution rather than a way to inspect the problem.

How do you choose the question before the meeting?

Start with the designer’s live uncertainty, not with the easiest feature to comment on. Ask what decision is still unsettled and what the team could actually help clarify by looking at the work together.

Then make the uncertainty visible in a sentence. “Is the front panel clear?” may be too broad; “Can someone tell which side opens without turning the object over?” gives the group a specific reading to observe. The question should describe a concern, not tell participants what answer to produce.

Imagine a small team reviewing a cardboard package whose opening tab is easy to miss. The designer asks, “What do you think of the package?” and hears opinions about its color and shape. If the team instead agrees to ask, “Where does your eye go when you first look for a way to open it?” members can describe the tab’s visibility and the competing visual cues, giving the designer something concrete to reconsider.

Before inviting people, write down:

• The decision still open.
• The question the group will discuss.
• The part of the work participants should inspect.
• Any context they need in order to interpret it.

Keep the context factual and brief. A long defense of the design can steer the room toward the answer the designer hopes to hear.

How should the team agree on one question?

At the start, the designer states the question and the uncertainty behind it. The facilitator, if there is one, checks that everyone understands the same wording; participants can clarify terms before they begin offering opinions.

If the question is too broad, sharpen it together. “Is this working?” can become “Can a first-time visitor find the booking action from this screen?” If several questions compete, choose the one tied to the decision that most needs attention now. Put the remaining questions aside rather than trying to answer all of them in the same conversation.

Agreeing on a question does not mean agreeing on an answer. It means that a comment should help the group examine the same uncertainty. A participant who sees a separate issue can note it for later without redirecting the discussion.

What observations belong in the discussion?

Observations describe what someone notices in the work; interpretations explain what that detail might mean. Both can help, provided they are distinguishable. “The title is the first thing I notice” is an observation. “The title may be overpowering the instruction” is an interpretation that can be considered against the question.

General praise is pleasant but often difficult to use. “This feels polished” does not say what is communicating well. A more useful version might be, “I noticed the opening icon before the small label, so I understood where to start.” The comment identifies a cue and the response it prompted.

Likewise, replace free-floating taste with a reason connected to the question. “I don’t like that green” is a preference. “The green button blends into the surrounding panel, so I did not read it as the next action” links the reaction to a perceptible effect. The designer can then decide whether the concern fits the project’s goals.

For physical work, participants can describe what they can actually see, reach, distinguish, or understand in the room. Avoid turning an informal critique into a claim about how all users will behave. It is a discussion of the presented work and the observations available to that group.

How can a facilitator keep feedback tied to the question?

A facilitator can listen for comments that answer a different question and bring the group back without scolding anyone. “That may be useful; how does it connect to where attention goes first?” acknowledges the contribution while restoring the agreed focus.

Ask participants to point to the specific detail behind an interpretation. If someone says a form feels confusing, the facilitator can ask what they saw that led to that reading. The aim is not to cross-examine the speaker; it is to make the comment usable rather than leaving it as an unexplained verdict.

Give the designer room to listen before responding. Immediate explanations can close down discussion, even when they are accurate, because the group begins evaluating the explanation instead of describing its reading of the work. The designer can ask clarifying questions and take notes, then respond after the observation phase.

What if the team disagrees about what it sees?

Disagreement can reveal that the work communicates differently to different people, or that the question needs refinement. Record the competing observations before choosing between them. A split in the room is not a reason to average the answers into a bland middle.

Check whether participants are describing the same feature and judging it against the same goal. One person may be discussing legibility while another is discussing visual character. Those are different concerns; separating them makes the disagreement more informative.

If the group cannot resolve the issue from the presented work, say so plainly. The next move may be to revise the artifact or arrange a more focused review, rather than letting confidence settle the matter. A critique can identify an uncertainty without pretending to settle it.

How do you close a critique without turning it into a vote?

End by restating the observations that bear on the shared question, not by counting who liked the work. The designer can say which points seem relevant, what remains unclear, and what decision they will consider next. Participants can correct a misunderstanding, but they do not need to approve the designer’s choice.

Separate notes into useful categories: observed reactions, interpretations, and possible changes. This preserves the difference between what someone noticed and what they recommend doing about it. A suggestion may be worth considering, but it is not automatically the answer to the question.

Keep unresolved concerns visible for the next review. If the group surfaced a new question, give it its own discussion rather than quietly folding it into the current one. That small act prevents the original critique from dissolving into a general redesign meeting.

Which critique questions help with common design concerns?

What makes the next critique easier to use?

Write the agreed question at the top of the notes and keep observations beside it. That simple record helps the designer distinguish feedback relevant to this decision from comments that may matter elsewhere.

A better critique session is not the one with the most suggestions. It is the one where the designer leaves knowing what the group actually observed, which parts were interpretation, and what uncertainty still needs attention. Keep the shared question visible; it is cheaper than trying to reconstruct the discussion from a page of adjectives.