Your design team and engineering team clash on user experience. How do you navigate the divide?

A clear definition of the value being sought after can be very useful in resolving such conflicts. Once the problem/opportunity that the solution aims to address is clearly defined, the user experience can be tailored accordingly so that it: - Addresses the main pain point. - Optimises for a fast delivery. - Accommodates potential technical limitations. - Encompasses measurable outcomes to maximise learnings. As long as the experience is derived from palpable logic/insights, and user needs are prioritised over chapter-based preferences, and different functions are encouraged to conduct positive communications internally, having such conflicts wouldn’t be of frequent occurrence in the first place.

Understand Issues: Engage in detailed discussions to grasp user experience concerns and technical challenges. Identify Core Conflicts: Recognize differing priorities or misunderstandings between teams. Acknowledge Objectives and Constraints: Understand each team’s goals and limitations. Facilitate Dialogue: Promote open communication to ensure both form and function are considered. Foster Collaboration: Encourage empathy and cooperation for a more efficient development process. By valuing both perspectives, you can create a product that is both aesthetically pleasing and technically robust. #ProductManagement #DesignThinking #Engineering #Collaboration #TechLeadership #UserExperience #ProductDevelopment #Teamwork #Innovation #TechIndustry

Navigating the divide between teams on UX requires fostering a collaborative environment and ensuring clear communication. Ex: In a Project Delivery Platform, the design team wanted a highly interactive and visually appealing dashboard for their app. However, the engineering team was concerned about the performance implications of such a design To navigate this divide,the teams conducted a joint workshop to prioritize key features, resulting in a compromise that balanced visual appeal with technical feasibility. They implemented a phased approach, starting with a simpler design and iterating based on user feedback & performance metrics. It not only improved the product but also fostered a more collaborative relationship between teams

Engaging in in-depth discussions with both teams helps uncover not only the user experience concerns and technical challenges but also the points of convergence and divergence in their priorities. Recognizing each team's goals and constraints is key to facilitating a productive dialogue that values both form and function in the final product. Clear communication and empathy are essential to harmonizing these distinct perspectives and achieving a balanced solution. Additionally, implementing regular cross-functional meetings and fostering a culture of collaboration can further enhance the integration of design and engineering efforts.

To effectively navigate a divide between design and engineering teams over user experience, begin by delving into the underlying issues. Apple addresses such conflicts by initiating thorough discussions with both teams. They aim to understand the user experience concerns articulated by the design team and the technical challenges highlighted by the engineering team. This comprehensive approach allows them to uncover the root of the conflict, often stemming from differing priorities or communication gaps. By acknowledging the objectives and constraints of each team, Apple facilitates a constructive dialogue that emphasizes the importance of balancing aesthetic appeal with technical feasibility in product development.

Establish a process that allows the design and engineering teams to collaborate and have clean hand-offs. Encourage the teams to meet regularly to hash out any areas of miscommunication. In addition, utilize technology platforms to clarify requirements and specifications outside of meetings. Products like Figma allow for team members to easily collaborate using comments. Promote this form of dialogue when meetings are not feasible.

Once the issues are identified, encouraging open dialogue is crucial. Facilitating meetings where both teams can present their viewpoints and listen without judgment is essential for promoting empathy and understanding. These discussions should be structured to focus on the project's overall goals rather than defending individual positions. Creating a safe communication space helps team members see beyond their perspectives, leading to innovative compromises and solutions that satisfy both design aspirations and engineering feasibility. Additionally, implementing tools for real-time collaboration and establishing a shared vocabulary can further enhance mutual understanding and cooperation.

Encouraging open dialogue between teams is crucial. Facilitate meetings where both teams can express their viewpoints without judgment. At Hackwhat, we found that structured discussions that focus on the project’s goals rather than personal preferences helped teams find common ground and respect each other’s contributions.

Design and engineering teams often have differing viewpoints on the best path for a product. This can lead to frustration and missed opportunities. By creating a safe space for open discussion, we can unlock the power of collaboration to achieve incredible results. Our shared goal is to provide the best user experience.

Encourage open communication. Schedule a joint workshop using Miro or Figma to brainstorm solutions. In one project, I facilitated a session where designers and engineers co-created wireframes. This not only built mutual respect but also resulted in a balanced design that was both beautiful and functional.

During clashes between design and engineering teams on user experience, the PM should solve the issue by using an effort vs. impact matrix to resolve them. It has four components; money pits, quick wins, big bets and fill-ins. Prioritizing quick wins first and the money pits at last is always preferred. For big bets and fill-ins, arrange for a meeting in order for each team to understand their schedules and issues. It is important to note that while some changes may not be feasible due to technical reasons or requirement of high effort, others can significantly improve the user experience just through minor adjustments .

Guide your teams to agree on what’s most important for the user experience and the product’s success. This might involve making tough decisions about which features are essential and which can be modified or postponed. Effective prioritization requires balancing user needs, business objectives, and technical realities. By setting clear priorities, you help both teams align their efforts toward a shared vision of the product, ensuring that everyone works together to achieve common goals efficiently and effectively.

As a product manager, guiding teams to agree on what is most critical for user experience and the product's success is essential. This often involves making difficult decisions about which features are essential and which can be modified or postponed. Effective prioritization requires balancing user needs, business objectives, and technical realities. By establishing clear priorities, you enable both teams to align their efforts toward a shared vision of the product. Additionally, regular reviews and updates on priorities can ensure that the team remains focused and adaptable to any changes or new insights that arise during the development process.

Establishing clear priorities is crucial to aligning teams. Reflecting on my experience, we once had to launch a product under tight deadlines, with limited capacity for both design and technical iterations. We utilized a framework to prioritize features based on user impact and feasibility. By involving both teams in this process, we ensured that everyone was on the same page regarding what mattered most to our users, streamlining efforts and reducing friction.

I'm going to recommend a step earlier - invite Design and Engineering to all user testing. Ensure they hear the context and feedback directly from users. By consistently being included in user testing, they build up knowledge on the top jobs to be done (problems) customers are seeking. This involvement flows into to being involved in subsequent stages of the product development process. Popping in and out of phases creates a patchwork of swiss cheese approach that is full of holes. Fill the holes will direct input from users.

This collaborative problem-solving process often leads to creative solutions that neither team might have considered independently. By fostering an environment where both design and engineering inputs are valued, you not only resolve current conflicts but also build a stronger foundation for future collaboration. Additionally, implementing joint workshops and using design thinking methodologies can further enhance this collaborative spirit and lead to more innovative and well-rounded solutions.

Get creative with compromise. Propose A/B testing different approaches using tools like Optimizely. In a previous project, we tested a minimalist design versus a feature-rich one. Data-driven results eased tensions and guided our final decisions.

Finding common ground often requires exploring various solutions. In a challenging project, we created cross-functional teams with representatives from both design and engineering. This collaborative approach led to innovative solutions that satisfied both aesthetic and functional requirements. Encouraging team members to brainstorm together can lead to breakthroughs that might not emerge in isolated settings, fostering a spirit of collective problem-solving.

Even the best teams have healthy disagreements. When design and engineering have different approaches, we, as product managers, will need to make the final call. Our decisions will always prioritize what's best for our users and the product's success, drawing on the valuable insights from both teams. Most importantly, we'll clearly explain the reasoning behind the decision, so everyone understands the "why" even if it differs from their initial preference. This transparency builds trust and keeps the team moving forward together, united by a common goal.

There are times when making decisive calls becomes necessary, especially when consensus cannot be reached. When faced with these situations, prioritize the best interests of users and the product, informed by insights from both teams. It's crucial to transparently explain your reasoning to ensure understanding, even among those who may disagree. This approach fosters respect and maintains trust within the teams, essential for navigating through tough decisions while keeping everyone aligned towards achieving shared goals.

Clashes and differences in opinions are part of Product Management. Varying opinions results in constructive discussions and the selection of solution that works best for the organization and the customer. As Product Managers, it is our role to facilitate the discussion and direct the team to a solution and gain consensus.

As a product manager, there will be times when you need to make decisive calls if consensus cannot be reached. These decisions should be made with the users' and the product's best interests in mind, while incorporating insights from both teams. It's crucial to explain your reasoning transparently to ensure that even those who disagree understand the rationale behind it. This approach helps maintain respect and trust within the teams, even when difficult decisions are necessary. By demonstrating a commitment to fair and thoughtful decision-making, you foster a collaborative environment where all team members feel valued and heard, which is essential for long-term success.

Making informed decisions is key. During a product launch, conflicting views on a core feature led us to develop a decision matrix that weighed user value, technical feasibility, and business impact. This structured approach helped us make balanced decisions that were data-driven and transparent. Ensuring that the decision-making process is inclusive and well-documented helps build trust and accountability across teams.

Execution is key. Implement chosen solutions and review them regularly in retrospectives. Tools like Trello can help track progress. During one sprint, we discovered a minor tweak in the UI significantly boosted user engagement. Regular reviews ensure continuous improvement.

Once decisions are made, implementing and reviewing them is vital. I recall an instance where we introduced a new feature based on a compromise between design and engineering. We closely monitored its performance and gathered user feedback, which was shared with both teams. This iterative process not only validated our decisions but also provided valuable insights for future projects. Regular reviews help teams learn and adapt, ensuring continuous improvement.

I believe that this is truly about teams understanding where they are most effective and also what is their core area of expertise. I love to use analogies and in this case I would say that just because the mechanic knows how to make the car run it doesn’t mean they are going to know the best experience for the driver even if the core experience is to get from A to B safely and comfortably, you need to utilize your teams strength and sometimes you have to remind them of what those strength really are

I believe every team wants the product to be the best, leveraging their expertise to provide the best suggestions on how the product can bring the greatest value to users. In my experience, engineering and design teams sometimes have different perspectives. My approach is to actively listen, allowing them to voice their concerns and interpreting the meaning behind their words. I strive to find solutions that address their concerns while explaining how these solutions can best serve users. I also emphasize that everything can be iterated upon. Also it's crucial to show respect and appreciation for their considerations and their willingness to strive for the best user experience.

Two ways to organically create alignment between engineering and design on user experiences, is dogfooding and user test/interview shadowing. Dogfooding, or actively using the product throughout the development process, is an effective and fast method to look at the product through the lens of the users. It's best to set up a block of time for design and engineering team members (and stakeholders if possible!) to go through specific areas/features one-by-one. Another method is to have both teams shadow user testing, either by watching recordings or real-time sessions. These methods will create more empathy between the teams and a shared understanding of the users, reducing conflict and creating consensus on the user experience.

Fostering a culture of empathy and collaboration is crucial. Arrange cross-functional team-building activities. In my experience, casual interactions, like Friday game nights, can break down barriers and build trust. Remember, it’s not just about resolving conflicts but building a cohesive team that values each other’s contributions.

When your design team and engineering team clash on user experience, bring them together for an open discussion. Encourage each team to share their concerns and perspectives to foster mutual understanding. Focus on the common goal of enhancing user experience and use data and user feedback to guide decisions. Work towards a compromise that incorporates key elements from both teams. Keep communication open with regular check-ins to ensure everyone stays aligned and any issues are addressed promptly. This approach helps bridge the divide and promotes effective teamwork towards a unified goal.