Why “Looks Good” Isn’t Particularly Useful Feedback
Design reviews aren’t about deciding whether everyone likes a design. They’re an opportunity to question the thinking behind it, bring in different perspectives, and make sure decisions stay connected to user needs and product goals. Sometimes the team agrees. Sometimes we don’t. Both can make the work stronger.
There are two words you can say during a design review that sound positive but aren’t particularly helpful: “Looks good.”
It’s nice to hear, of course. But when we’re trying to understand whether a design actually solves the right problem, we need to go a little deeper.
Why does this interaction work this way? What does the user need at this point? Are we making an assumption? What happens in a different scenario? Is there a simpler way to accomplish the same thing?
At Pepperplane, design reviews give us space to ask those questions while the work is still evolving. After spending hours thinking through a flow, certain decisions can start to feel obvious. Another perspective can help us notice what we’ve missed, challenge an assumption, or simply confirm that the thinking holds up.
“Looks good’ isn’t particularly useful feedback.”
What We Bring to a Design Review
A design review isn’t simply putting a screen in front of the team and asking what everyone thinks. The designer brings context: the problem we’re solving, who we’re solving it for, what we’ve learned so far, the constraints we’re working within, and where there are still questions.
That context matters because a screen can’t be evaluated meaningfully in isolation. Something may look perfectly reasonable on its own but make much less sense when you consider the broader workflow or what the user is trying to accomplish.
The goal isn’t necessarily to present finished work for approval. It’s to share enough of the thinking that the team can help make it stronger.
The Questions Matter More Than Personal Preference
Design feedback can become subjective very quickly.
“I don’t like that.”
“I’d put this over here.”
“I think this version looks better.”
Instead, we try to bring the conversation back to the user and the problem. Does the user have enough information to make this decision? Is this consistent with the rest of the experience? Are we adding unnecessary complexity? What happens when something goes wrong?
Sometimes the most valuable feedback isn’t a proposed solution at all. It’s a question that exposes something we haven’t considered.
“What happens if they don’t have this information?”
“Why does the user need to make this decision now?”
“Could they arrive here another way?”
Those questions give us something much more useful than preference. They help us evaluate whether the reasoning behind the design actually holds up.
What Happens When We Disagree
Designers won’t always see a problem the same way, and that’s useful. When we disagree, the goal isn’t to determine who has the stronger opinion. We return to what we know. What are users trying to accomplish? What did we learn during research? What are the business goals? Are there technical constraints? Is there an assumption we still need to validate?
Sometimes that leads to a clear answer. Other times, we explore more than one direction or realise we need additional information before making the decision.
And importantly, not every piece of feedback automatically becomes a revision. Feedback gives the designer another perspective to consider, but decisions still need to make sense within the context of the product and the problem we’re solving.
How Design Reviews Change the Work
Sometimes a review results in a small adjustment. A hierarchy becomes clearer, an unnecessary step disappears, or an edge case gets addressed before development begins. Other times, one good question causes us to rethink a larger part of the experience.
Not every improvement creates a dramatic before-and-after. Some of the most valuable changes can look surprisingly small to the person using the product. What matters is that the experience becomes clearer, more consistent, or better suited to what users actually need.
Why We Review Work Before It's Finished
Design reviews are most useful while there’s still room to explore. If designers wait until everything is polished before sharing it, changes become harder and more expensive. Bringing work into the conversation earlier means we can challenge an interaction, explore another direction, or uncover a missing scenario before too much has been built around it.
That requires an environment where people can challenge the work without making the conversation personal. The objective isn’t to prove someone wrong or find flaws for the sake of it. It’s to give the team the best chance of getting the product right.
What This Looks Like at Pepperplane
At Pepperplane, Design Reviews are one of the ways we keep the work collaborative. Designers share work while it’s still evolving. We ask questions, challenge assumptions, explore alternatives, and connect decisions back to users, business goals, and the broader product experience. When useful, developers and stakeholders can bring additional context that helps us look at the problem from another perspective.
Sometimes a review confirms that we’re heading in the right direction. Other times, it changes the work. Both are useful because the point isn’t to find something wrong with every design. It’s to make sure the thinking behind it is strong enough to move forward.
Final Thought
The best design feedback isn’t always the feedback that gives you an answer. Sometimes it’s the question that makes you reconsider an assumption, the disagreement that reveals something you haven’t validated, or another designer noticing the one thing you’ve stopped seeing after staring at a workflow for hours.
That’s what makes Design Reviews valuable. They’re not about deciding whether something “looks good.” They’re about making sure the design makes sense for the people who will eventually use it and if all we ever heard was “looks good,” we’d probably be missing some very useful conversations.
Ready to Build Better Products Together?
Looking for a UX partner who can bring clarity to your next project? We’d love to chat.
Book a discovery call and let’s build something remarkable together.