||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--|| ||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||-- --||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||--||
How to Handle UX Disagreements and Get Your Team Aligned
UX disagreements happen when stakeholders prioritise personal preferences or business goals over user needs. The fix is a shared "Design Success = User Success" mindset, backed by usability testing and collaborative design thinking exercises.
Every UX designer knows the feeling. You've spent weeks crafting a solution you're genuinely proud of, you present it to the room, and then someone says, "I was really hoping it would look cooler and more high tech. This seems a little boring to me." Just like that, the wind goes out of your sails.
Disagreements don't have to derail all of your hard work. Here's how to spot the warning signs, get everyone on the same page, and be the hero who guides your team to a successful product.
What Is the Number One Cause of UX Disagreements?
The top cause is prioritising business goals over user needs.
When your design process is driven by technology and engineering rather than by what users actually need, your product's success will always be limited. It might functionally work and be "good enough," but it will never be great because it doesn't address the "user" part of "user experience."
Think about two of the most famous theme parks of all time: Disneyland and Six Flags. Disneyland had a vision -- to create magical experiences for their guests. Every detail, from the layout and rides to the characters and music, was designed with that vision in mind.
Six Flags prioritised profits over the user experience. Their parks were popular for a few years, but because they were more focused on the business than on their guests, competitors caught up and drove them to bankruptcy in 2010.
Two seemingly similar products. Two very different outcomes. The difference? One focused on the business, the other focused on the user.
What Are the Warning Signs of UX Misalignment?
Differing UX opinions don't just create tense emails and awkward conversations -- they create bigger problems that affect the whole company. Sound familiar?
Why Are Sales and Usage Lower Than Expected?
Years ago, your founder identified a problem they thought tons of people could relate to. They spent thousands of dollars (maybe even millions) to build a solution and released it to the world with great anticipation.
"This is our golden ticket!" they thought. "People are going to love it."
But then... nothing. Sales numbers barely hit a fraction of the goal, and usage was low to non-existent.
Among other issues, there were probably differing opinions about the product's strategy and direction behind the scenes, which ultimately snowballed and led to disappointing performance.
Why Are Users Creating "Hacks" to Use Your Product?
Our team at Drawbackwards was working with a client to redesign a support tool originally built to help Customer Service Representatives manage incoming calls. When we sat with the reps to observe how they actually used it, the first thing we noticed was Post-It Notes stuck to their computer screens with instructions on how to complete tasks inside the tool.
The original designers may have thought the system was intuitive because it met their needs and they understood it like the back of their hand. But the average user couldn't find the information they needed when they needed it, so they designed their own hacks and shortcuts to get the job done.
This self-design style may allow users to complete their tasks, but its "minor" shortcomings add up to major problems, including lost time, higher costs, and unhappy customers.
Why Are Your Sprints Moving Slowly?
A sprint is a short work cycle (usually one to four weeks) that helps teams work quickly and effectively while allowing for adjustments and testing. Sprints slow down when there are disagreements about the project's goals or how they should be achieved, which puts deadlines and budgets at risk.
Sometimes that slowdown is a good thing -- the team is taking time to gather more information and make smart decisions. But when a project slows because of rework or team members spinning their wheels, it's a sign that the project -- and the product as a whole -- may be in danger.
How Can Design Thinking Help You Overcome UX Disagreements?
The irony of product design is that meeting long-term business goals is only possible when user needs are put first.
The first step is recognising the problem. If you can relate to the warning signs above, your team may be suffering from a lack of UX alignment. Here are three tactics to conquer differing opinions, get everyone on the same page, and lead your team to success.
Always Put Users First
When business goals are prioritised over user needs, your product will only go so far. The strongest Product Owners, designers, and business professionals know that "Design Success = User Success."
There may be many stakeholders and board members to please, but with this mindset, the end user is the Chairman of the Board -- the one "person" who brings everyone else together and ensures they're all working toward the same goal.
Tesla is the perfect example of a company that always puts users first. Elon Musk has a vision for Tesla's user experiences, and he can articulate the exact experience he wants customers to have. When he makes business decisions, he makes them based on what's best for the user, not what's most profitable, easiest, or most cautious.
Tesla's Model S includes Autopilot, a feature that uses sensors, a camera, radar, and digitally controlled brakes to automatically stop the car before crashing. Autopilot was celebrated as a new frontier in safety and convenience -- until a driver using it died in a fatal crash.
Musk could have immediately pulled the feature and gone into damage control mode to save the company's image and avoid a drop in sales. That would have been the easiest and most conservative route. Instead, he prioritised his customers and not only kept Autopilot, but made a bold statement that he still fully believes in its effectiveness and original purpose: to improve safety. "The probability of having an accident is 50% lower if you have Autopilot on," he said. "Even with our first version, it's almost twice as good as a person."
By staying true to his vision and putting users first, Tesla has -- and will continue to -- design products that change lives and grow their business.
The "Design Success = User Success" mindset can't stop at the CEO or executive level, though. This commitment to the user experience needs to permeate throughout the entire organisation so every person -- from Product Owners to Engineers to Customer Support Representatives -- is focused on the same thing: the user.
Conduct Usability Testing Before, During, and After Development
When a personal trainer coaches clients through a weight loss "project," they use a scale to objectively track progress and decide how to proceed. Usability testing serves the same role in design projects.
As we discussed in our two-part guide to usability testing, testing is a great way to move past differing opinions because it focuses on data, not personal preference. While many designers test their work after it's completed, testing before, during, and after development leads to the best results.
Without testing, everything is a hypothesis that invites subjective opinions about the outcome. Data removes the emotion, ensures the product is on the right track at every milestone, and increases the likelihood of success.
Sometimes, even when you have good data from usability testing, team members disagree on what the data means or what to do with it. Usability research should serve as a guide, not a rulebook. It points you in the right direction 80% of the way, which will help you design a product that's functional, usable, and comfortable. But completing the final 20% -- creating a product that's delightful and meaningful -- requires taking risks or putting your own spin on it. You need a distinct point of view about how the experience should be, and no rulebook can teach you that.
Show, Don't Tell
Humans learn best by doing. Instead of telling stakeholders and executives the right answers, show them how to find the answers themselves through design thinking exercises and workshops that encourage alignment.
Exercises and workshops are some of the most effective tools for building consensus because they get people involved, uncover insights that may not come out in everyday conversation, and make stakeholders feel more invested in product success.
Here are some of our team's favourite exercises. (See our article on empathy exercises for even more!)
-
Journey mapping: Map out each step of the user's journey and how they interact with your product over time and across channels. This is an amazing exercise for identifying and prioritising opportunities for improvement.
-
Empathy mapping: Empathy maps help teams better understand their users by brainstorming user feelings, influences, tasks, pain points, and goals. Repeat this exercise for a typical user in each of your customer segments, then refer to the empathy maps as a resource for user-focused decision making and identifying jobs to be done.
-
Pair sketching: Pair sketching brings together at least two stakeholders (designer + another designer, developer, user, subject matter expert, client, or other stakeholder) to join forces on a product sketch. This collaborative design approach makes it easy to share knowledge and iterate quickly to find the best solution.
Every UX Disagreement Is an Opportunity
Getting pushback may seem like an obstacle, but it's actually an opportunity to show your value. Whether you're an in-house designer pitching a small idea to a sceptical crowd, or Elon Musk designing products that are changing the world, you're bound to encounter someone who disagrees with you. It's how you overcome those hurdles that really counts.
With a "Design Success = User Success" mindset, an iterative process with multiple usability testing touchpoints, and an arsenal of collaborative exercises, you'll have the tools needed to be a seasoned design thinker who brings stakeholders together and creates products that guide your users and your company to greatness.
FAQ
What is the most common cause of UX disagreements on a product team? The most common cause is prioritising business goals over user needs. When design decisions are driven by internal preferences rather than real user behaviour and data, disagreements multiply and the product suffers.
How do you get stakeholders to agree on a UX design direction? Use collaborative design thinking exercises like journey mapping, empathy mapping, and pair sketching. These workshops get stakeholders involved in finding the answers themselves, which builds consensus and shared investment in the outcome.
Why does usability testing help resolve design disagreements? Usability testing replaces subjective opinion with real data. When the conversation shifts from "I think" to "users showed us," it becomes much easier to align on a direction.
How do you know if your team has a UX alignment problem? Look for these warning signs: sales and usage are lower than expected, users are creating workarounds to use your product, and sprints are consistently slowing down due to rework or unresolved disagreements rather than smart, deliberate decision making.
What does "Design Success = User Success" actually mean in practice? It means every design and business decision -- at every level of the organisation -- is evaluated against one primary question: does this serve the user? When the end user is effectively the Chairman of the Board, all the other stakeholders naturally start working toward the same goal.
Get Educated