How to ask for design feedback that moves the work forward

Tell reviewers what is open for discussion

Before the meeting, explain the user, task, evidence, constraints, and current stage. Say what is already fixed and why, and what can still change. A rough navigation concept should not spend its entire review on icon polish. A final production review should not quietly reopen the entire product strategy without acknowledging the impact on time and scope.

Ask a question tied to the task

Replace “Do you like it?” with “Can a first-time user understand which action will send the invitation?” or “Which of these two structures makes the account status easier to interpret?” Invite reviewers to explain the basis for their feedback. A preference, an accessibility concern, a technical dependency, and an observed user problem each deserve different treatment.

Show alternatives with their tradeoffs

Present two plausible approaches and explain what each optimizes. One may reduce the number of screens while increasing the amount of information shown at once. Another may add a step but make a consequential action easier to understand. Do not present an obviously weak alternative merely to make your preferred option look inevitable. Ask what evidence would change the decision.

Separate the observation from the proposed fix

A reviewer might say, “Make the button red.” Ask which problem they are trying to solve. They may be concerned that the primary action is hard to find. Record that concern, then consider contrast, placement, wording, spacing, and other options. This keeps the critique focused on the experience while leaving room for design judgment. Do not dismiss a concern simply because its first proposed solution is weak.

Keep a short decision log

For each substantial comment, capture the issue, evidence, consequence, decision, owner, and next action. Label suggestions that require research. Summarize what changed and what did not, with reasons. A critique is not a vote in which the largest number of opinions wins. The responsible team needs to weigh user needs, business requirements, accessibility, feasibility, and uncertainty.

Use a 30-minute meeting structure

Spend five minutes on the context and decision, five on the walkthrough, ten on focused feedback, five comparing options, and five assigning next actions. This is a suggested format, not a rule. Send the material beforehand when possible and offer an asynchronous way to contribute. Make room for quieter participants and avoid using seniority as a substitute for evidence.

Try this invitation

“We are reviewing the first-use invitation flow for team owners. Today we need to decide how to explain when invitations are sent. Please focus on comprehension, recovery, and missing states. The account permission model is fixed for this release. We have two options and need to identify what should be tested next.” For an outside perspective, a UX Decision Review provides annotated findings and a focused working conversation about one journey.

Keep exploring

A better-looking redesign is a hypothesis. Here is how to test it.

How to prioritize UX friction without giving your product a made-up score