What Should You Test After a Design Review

•
5 min read

Design reviews often surface questions the team cannot settle internally. Here’s how to turn those questions into focused user tests.
Design reviews are great for catching inconsistencies, questioning decisions, and getting different perspectives on a piece of work. They are also very good at producing questions nobody in the room can answer with much confidence.
Will users notice this action? Does this label make sense? Is the new flow easier? Which of these two directions communicates the idea better?
I’ve been in plenty of reviews where those questions turn into another twenty minutes of discussion. Everyone has a reasonable opinion, but eventually you reach the limit of what looking at the design together can tell you.
That is usually a useful signal. Instead of trying to settle every open question inside the review, take a few of them into research.
Look for comments that predict user behavior
A design review can produce dozens of comments, and plenty of them can be handled by the team directly. Spacing inconsistencies, missing states, component usage, technical constraints, and accessibility issues do not all need a user study.
The comments I pay closer attention to are the ones that make a prediction about the user.
“People will probably click here first.”
“This label should be obvious.”
“I think users will prefer the simpler version.”
“They should understand what happens after this step.”
Those are useful because they already point toward something we can investigate. The next step is turning the comment into a clear research question.
“Will users notice this?” might become Where would you click first to start this task?
“Is this flow understandable?” could become Can users complete the task without getting stuck or taking an unexpected route?
That small shift makes the question much easier to test.

Test whether users know where to start
Questions about hierarchy and discoverability come up constantly in design reviews. We move a button, adjust a label, change the navigation, and then wonder whether the intended action is visible enough.
A First Click Test can be a very efficient way to investigate that. Give participants a realistic task and see where they go first. If most people head toward the intended action confidently, you have evidence supporting the direction. If they repeatedly choose something else, the design may be communicating a different path than the team expected.
You can learn a surprising amount before running a larger usability study, especially when the uncertainty is focused on the beginning of a journey.
Compare directions when the review is stuck between options
Sometimes a design review ends with two perfectly reasonable options still on the table. At that point, another round of internal voting usually does not add much.
A Preference Test can help when the decision is genuinely comparative, but the question needs to be specific. Asking users which design they “like” can leave you with little to work from afterward.
If the review is really about clarity, ask which version communicates the information more clearly. If the concern is scanning, frame the comparison around that. If you are comparing how confidently two versions communicate the next step, make that the focus.
This gives the preference some context and brings the result closer to the design decision the team is trying to make.

Test the full interaction when the question is bigger than one screen
A design can make perfect sense when everyone is discussing one screen at a time and still become confusing once someone has to move through the entire flow.
If a review raises questions about completing a task, understanding a sequence, recovering from a mistake, or moving between states, I would usually want to test the interaction itself. Prototype Testing lets the team put that flow in front of users before committing to development.
This is where behavior often reveals things that are hard to spot in a static review. People hesitate between steps, interpret labels differently, go backwards, or reach the right outcome through a route nobody on the team expected.
For us as designers, that is much more useful than another round of guessing how the flow will feel.
Keep some questions for a conversation with users
There are also review comments that point beyond usability.
Maybe the team is unsure whether people understand why a feature is useful. Perhaps a workflow technically works, but we do not understand what users expect from it. Or the review exposes a bigger question about how people currently solve the problem.
Those are good moments to step beyond clicking behavior. Useberry supports both unmoderated testing and moderated research, so the question can shape the type of study rather than forcing everything into the same format.
A focused usability test can show where someone struggles. A live interview gives you room to ask why they expected something different, follow an unexpected comment, and understand more of the context behind the behavior.
Come back to the next review with evidence
The next design review becomes much more productive when the team can replace a few assumptions with observations.
Instead of “I think this CTA is clearer,” you can say that participants consistently found it first.
Instead of debating whether a flow feels confusing, you can show where several participants hesitated and talk about what to change.
Research will not remove disagreement from design reviews, and I would not want it to. Good critique still depends on experience, judgment, constraints, and different perspectives. User testing gives some of those conversations a stronger foundation and helps us recognize which questions no longer need to be decided by the loudest opinion in the room.

Let the review tell you what to research next
I do not think every design review needs to end with a user test. I do think it is worth paying attention to the questions that keep resurfacing after everyone has shared their perspective.
If the team is debating what users will notice, understand, expect, prefer, or do, write the question down before the meeting ends. Decide how important the uncertainty is, choose the smallest useful test, and bring the answer back into the next iteration.
Over time, design reviews become a surprisingly good source of research questions. You just have to notice when the conversation has reached the point where another opinion is unlikely to answer them.

Take the questions your design review cannot settle to the people who can.
Turn open design questions into focused user tests and bring stronger evidence into the next iteration.

