How UX Teams Can Address Client Feedback Without Derailing a Project
Design reviews are some of the most important—and sometimes most challenging—moments in any product development project.
Whether you're presenting wireframes, prototypes, or polished visual designs, stakeholder feedback can either strengthen the work or stall momentum. The key isn't avoiding feedback; it's knowing how to address it constructively.
In edTech, the challenge is often amplified. Products frequently serve multiple audiences, including students, teachers, caregivers, school leaders, and administrators. Each stakeholder brings unique priorities, perspectives, and expectations to the table.
At Backpack Interactive, we've spent years helping organizations navigate the design process, from early discovery through final implementation. Along the way, we've encountered a handful of common responses during design reviews. More importantly, we've developed strategies for turning those moments into productive conversations that keep projects moving forward.
Here are five types of feedback we encounter regularly—and how we address them.
1. "Will Our Users Really Go for This?"
This is one of the most valuable questions a stakeholder can ask.
When clients challenge whether users will embrace a particular design direction, it's an opportunity to return to the foundation of the project: user research.
Strong design decisions aren't based on trends, assumptions, or personal preferences. They're informed by a deep understanding of user behaviors, goals, motivations, and pain points.
That's why we spend so much time during discovery and UX planning getting to know the people who will ultimately use a product. By the time visual design begins, we've already gathered insights through stakeholder interviews, user research, competitive analysis, analytics reviews, or usability testing.
When we worked with WNET on the Mission US platform, our team designed an experience for middle and high school students that reflected the types of digital experiences they already enjoyed outside the classroom. Research into gaming conventions, content discovery patterns, and student expectations influenced everything from navigation choices to calls-to-action and multimedia placement.
When questions arise during design reviews, we connect those decisions back to the research and goals established earlier in the project. Rather than defending a design preference, we're able to explain how specific choices support user needs and business objectives.
The strongest design conversations happen when feedback is grounded in evidence rather than opinion.
2. "I Don't Know What This Is."
Not every stakeholder speaks the language of UX.
Design teams spend their days working with wireframes, prototypes, user flows, design systems, and interaction patterns. For clients, however, these deliverables may be entirely new.
Confusion during a design review doesn't mean something has gone wrong. It usually means more context is needed.
Wireframes, for example, are intentionally low-fidelity. They're designed to communicate structure, hierarchy, and functionality—not visual polish. A stakeholder who expects a finished design may struggle to understand what they're looking at.
That's why presentations matter.
During design reviews, we don't simply show screens. We explain:
- What stage of the process we're in
- What decisions have already been validated
- What areas are still being explored
- How users will interact with the experience
- Which interactions aren't visible in static designs
Animations, transitions, hover states, and responsive behaviors often can't be fully communicated in a flat mockup. Walking stakeholders through these interactions helps bridge the gap between what they're seeing and what users will ultimately experience.
Most importantly, we encourage questions. Creating space for clarification early prevents misunderstandings that can create larger challenges later in the project.
3. "Should We Add..."
Few things spark new ideas like seeing a product begin to take shape.
As stakeholders review designs, it's common for new features, functionality, and enhancements to come to mind. While these ideas can be valuable, they can also introduce scope creep and distract from the core user experience.
When new feature requests emerge during design reviews, we encourage teams to pause and evaluate them through a strategic lens.
Questions we often ask include:
- Does this support a primary user need?
- Does research indicate demand for this functionality?
- Does it help users accomplish a key task?
- Is there a simpler solution?
- Is this a future roadmap item rather than a current priority?
Often, what appears to be a design challenge is actually a product strategy conversation.
Returning to wireframes, user journeys, and project goals helps teams evaluate new ideas within the broader context of the experience. It also ensures that decisions remain focused on solving user problems rather than adding complexity.
The best products aren't the ones with the most features. They're the ones that make it easiest for users to accomplish what matters most.
4. "This Approach Just Doesn't Feel Right."
Some of the most important feedback is also the most difficult to interpret.
Stakeholders don't always have the language to explain why a design isn't resonating with them. Sometimes the feedback is simply, "Something feels off."
That's okay.
In fact, subjective reactions often reveal valuable insights when explored thoughtfully.
Instead of immediately defending a design direction, we ask follow-up questions:
- What specifically feels off?
- What expectation isn't being met?
- What would you expect to see instead?
- What concern does this raise about the user experience?
- Which audience are you thinking about?
These conversations help transform vague reactions into actionable feedback.
Sometimes the issue stems from an unmet user expectation. Other times it reveals a business priority, organizational constraint, or stakeholder concern that hasn't yet surfaced.
Our role is to listen carefully, uncover the underlying issue, and determine whether the solution lies in the design itself, the product strategy, or the way the work is being communicated.
When feedback becomes more specific, better solutions emerge.
5. "I Like It, But I'm Not Sure My Boss Will."
This type of feedback usually points to a larger challenge: stakeholder alignment.
When key decision-makers aren't involved throughout the design process, even strong solutions can face resistance late in the project.
That's why stakeholder engagement shouldn't begin at the final presentation. It should happen throughout discovery, strategy, UX planning, and design.
By involving decision-makers early, teams create shared ownership and reduce the likelihood of major surprises later.
Design presentations also serve an important purpose beyond showcasing work. They provide an opportunity to revisit the journey that led to the proposed solution.
A successful presentation connects the dots between:
- User research findings
- Business goals
- Product requirements
- UX decisions
- Design recommendations
When stakeholders understand how and why decisions were made, they're more likely to support those decisions internally and advocate for the work with other leaders.
Alignment doesn't happen by accident. It's built through transparency, collaboration, and consistent communication throughout the project.
Great Design Feedback Leads to Better Products
Feedback is an essential part of the design process.
The most successful product teams don't view stakeholder feedback as an obstacle to overcome. They view it as an opportunity to strengthen ideas, uncover blind spots, and build alignment around shared goals.
Whether you're presenting early wireframes, interactive prototypes, or polished visual designs, productive conversations start with empathy, curiosity, and a commitment to user-centered decision-making.
When research guides the discussion and stakeholders understand the reasoning behind design decisions, feedback becomes less about personal preference and more about creating the best possible experience for users.
That's when projects move forward—and products become stronger as a result.
Sean Oakes
Sean has over 20 years of interactive design and account management experience. In 2000, Sean founded SOS, a specialized creative studio based in Brooklyn, NY. He has set the creative vision for the highly regarded firm; the power of thoughtful design and delightful user experience to enable better teaching, learning, and communication.
Sean is a graduate of the Rhode Island School of Design. His work has been recognized by The Webby Awards, Communication Arts, SXSW Interactive, Business Week, The Smithsonian, and Apple.
