When a team is divided on UX design, focus on the user. Testing ideas with real users or looking at data can show what works best. Back at Abitly, this was a practice we often used to align the team and move forward. Reminding everyone of the main goal—creating a great user experience—helped clear up disagreements. Building quick prototypes also brought ideas to life, making it easier to get everyone on the same page.

Hold a focused, neutral workshop to identify shared goals, then collaboratively test ideas with users and iterate based on feedback.

You bring the user in and do focused testing with them. If you can't get a user, or a realistic proxy, establish goals for the feature or flow, and evaluate which approach fulfills the goals the best.

In the project whole team has to be on same page. Here each person's thinking will be different. Based on Requirement/ Time to develop/ what is better solution to the client we can propose. All together will align the team on same page

Before diving into the specifics of design preferences, take a step back and align the team on the overall goals of the project. Ensure that everyone agrees on: User Needs: What problems are you solving for the user? What are the most important tasks the user needs to complete? Business Goals: What is the project trying to achieve from a business perspective? This could be increasing conversions, improving user engagement, or driving user retention. Technical Constraints: What are the technical limitations or opportunities

Assuming everyone is aware of the environment, goals, target audience, time to deliver… Their opinions can only differ if there are no hard facts to make a decision. So do testing (like A/B or others) because that will remove the guesswork. If thats not possible then ask some users. If thats not possible either, then do the hard way: the person most knowledgeable about it should decide and take responsibility, meaning that person needs to monitor the usage and it was the wrong decision then that person will initiate and manage the change of design.

Taking a step back first is wise advice I saw others suggest on this thread. The team needs to look at the project from the user's perspective, put themselves into the shoes of someone performing that job, and work from that perspective. This requires immersion in the job itself before this point of disagreement, to ensure that the design team has enough experience on the front line with real users to be able to put themselves in that mindset. This isn't a technical problem. In my experience, most teams have the technical expertise to develop almost any solution. It's a problem in having the team understand the user requirements on bone-deep level.

To find common ground in user experience design, facilitate a collaborative workshop where team members can openly share their perspectives and ideas. Use data-driven insights and user feedback to guide decisions and align on design priorities. Foster a culture of empathy and compromise, ensuring all voices are heard and respected.

Facilitate a collaborative discussion to align on user needs and project goals, using data and user feedback to guide decisions. Encourage brainstorming and compromise to incorporate diverse perspectives while maintaining design consistency.

Encourage the team to focus on the broader perspective, specifically the User Personas. For example, consider personas such as "Tech-Savvy Professionals", "First-Time Users", "Frequent Shoppers" and so. Emphasize how these users can have a delightful experience and identify the steps needed to make this experience seamless. By motivating the team to adopt this viewpoint, we can foster greater alignment and convergence within the division..