What do you do if your application developers and user experience designers can't agree on design choices?

Often, developers are key partners in reality-checking in that they know what goes on in the application as well as in terms of feasibility and cost. Involve them as early, as often, and as deep as possible.

I would facilitate a collaborative discussion between the designers and developers. The designers will provide information from the user's perspective, and the developers will provide details on technical feasibility. Then each side may need to make trade-offs depending on the impact of the particular design choice. If it would create a significant impact on the user experience, then a technical workaround would be needed. If the impact is not critical, then we may prioritize a more technically feasible solution. However, keep in mind that small design compromises build up as design debt and making such compromises should not become a habit.

When developers and UX designers can't agree on design choices, better to open communication and find a middle ground. Encouraging both sides to share their perspectives can lead to understanding and compromise. And the ultimate goal is to create a product that serves the users best, balancing technical feasibility with a good user experience. Sometimes bringing in a neutral party like a product manager/owner can help make decisions that align with the project's overall vision. Also prototyping and user testing can offer valuable insights that guide the decision making process ensuring that both design and functionality meet user needs effectively.

Have a design authority kind of construct to ensure technical governance. Any conflict, they can look at the design independently with rationale and help everyone come to an agreement.

Go back to the discovery research and/or the data. If the answer isn’t in there, do more research or get more data. It doesn’t have to always be long, formal research. But “I think…” is hard to defend to execs when spending their money.

As a seasoned UX/UI Designer, my approach in such scenarios is to foster collaboration and find common ground. I initiate structured discussions where both developers and designers can express their perspectives openly. By focusing on user-centric principles and technical feasibility, we strive to identify solutions that align with project goals and constraints. Through iterative prototyping and user testing, we validate design choices while addressing any concerns raised by the development team. Ultimately, our shared goal is to create a cohesive and intuitive user experience that meets both user needs and technical requirements.

This is a real scenario, but there is nothing that cannot be solved by open communication. In this situation first and foremost is to understand the perspective of both the development team and the user. Identify the difference in their approach, in my experience at most places they are saying the same thing it's just they speak different languages(tech and functional), bridge the understanding gaps. Then for the remaining real gaps to be addressed by reviewing 1) requirement documents 2) if it's not in initial requirements it needs to go through a change cycle, feasibility assessment and acceptance ( within the delivery scope or extra time/money) 3) if it's in the initial requirements the assessment/ understanding tech view on the gaps

Collaboration is the key. Understanding the "why" on both sides is key so that both parties understand the rational behind each other opinions. Starting the conversation early in the process is also important so that you don't get too late in the process to find out about the disagreements. This is where agile development with members from UX and Dev helps a lot, and I speak from experience, having worked with different SLDC's. Last but not least start by sharing with the vision of the product and have the big questions addressed at start. That's the grand opening of the dialogue. As architects we can make a difference by painting the big strokes, act as facilitators and chime in our expertise along the way.

Simply being stern on your points, be it a designer or engineer, will not solve issues. The issues might not be as big as it seems. I've always tried to keep an open mind and collaborate with the developers to identify the root cause and find alternate ways to bring out the desired result.

Continuando: - Com os dados em m?os, eu iria separar em pequenos grupos de cada área (grupo de devs e grupo de designers). Após trazer a importancia e expectativa de colaborarem juntos, eu traria os dois grupos e faria dinamicas para criar o sentimento de time, com um objetivo em comum que precisa ser sanado.

One thing I would encourage is bringing in some customers and let them hear their debate and options. Often a customer will point out that neither is understanding the jobs they want to do and done well could create a useful third way that both teams engage in based on real user insight.

I would bring back to the table some design alternatives that were considered in earlier stages. Share usability testing and other results to support the chosen design. Make a case based on research. Additional brainstorming and new ideas should alway focus on the goal and go through the same validation process, so that the team will have all the information needed to choose the right design.

Make an MVP version of your design! MVP is an established strategy in an agile development process. Put basic functionality over your genius ideas and see how much you can strip away from your mocks. This does not mean that you have to throw away everything you just had to cut out. Keep it and make sure you make your case in the next development cycle.

In this scenario, as a UX designer, I actively listen and seek to understand the developers' perspective. I then utilize brainstorming techniques to propose various solutions, always striving for better alternatives.Collaboration between UX designers and developers is essential for achieving optimal outcomes, as it allows for the synthesis of diverse perspectives and the creation of innovative solutions that address both user needs and technical constraints. By fostering open communication and embracing iterative processes, we can continuously refine and enhance the user experience.

Algumas maneiras de explorar alternativas seriam técnicas conhecidas: - Crazy 8 - DAKI - Journey Map (+ comentários de prós e contras)

Business may ask for UI for their convenience but it may not be possible all the time to build it as such There are situations where a technical conatraint can block building the UI Negotiate with business

Dando continuidade na linha de raciocínio, entendo que duas coisas s?o imprescindíveis: - Matriz CSD: Desde o início da coleta de dados, recomendo que esteja sendo feito a Matriz CSD, para que seja preenchido e sanado todas as lacunas durantes o pensamento de Design; - Matriz de Impacto x Esfor?o: Neste cenário seria colocar todos numa mesa e pontuar os ganhos, impactos, esfor?os e oportunidades que podemos alcan?ar ou n?o, com base em cada decis?o.

Após estressar a prioriza??o e suas possíveis solu??es, é tempo de levar isso adiante para os líderes, coordenadores, diretores ou algum C-level que esteja diretamente conectado com o quadro de decis?o. é importante como Designer e facilitador, munir nossos líderes com nossas pesquisas e know-how de mercado, para que eles venham tomar a decis?o mais acertada para a empresa.

Identify the goals, prioritize for business, technology. Put customers 1st and this will provide a clear guidance Work out which can bring more customer experience

An alternative strategy is to jointly commit to a specific approach, especially when time constraints prevent thorough testing of different ideas. It's crucial for both developers and UX designers to agree on a method that strikes a balance between immediate benefits and the ease of making changes later if needed. Choosing solutions that can be easily revised or reversed is advantageous. This approach promotes flexibility, and ensures the team makes progress, while allowing for adjustments if needed.

Use both high-fidelity mockups and low-fidelity prototypes for user testing. Get user input on various design possibilities to learn about their preferences and spot usability problems.

Data-driven methods are key in application development and UX design. 1. Foster effective communication boosts project success rates to 80% 2. Align teams with business objectives for a 57% higher chance of achieving ROI 3. Promote compromise for 35% higher likelihood of outperforming competitors 4. Prioritize user needs for significant returns (1:100) 5. Seek external input to increase success rates by up to 25% 6. Adopt iterative design approaches to reduce waste by 60% and improve productivity by 50%. 7. When everything fails make leadership decisions to align the team .

As a designer you should also ask yourself: Are such conflicts with the dev occur only occasionally or frequently? Try to learn from it and develop a strategy how to minimize them in the future. Do your own post mortem of what just happened and find out if you might need to learn more about a developer's workflows and challenges they're frequently facing. Often I've seen such tensions between developers and designers because neither side is willing to spend a few moments in the other ones shoes. This also means that you could be facing some attitude from the engineers. In such cases find a third party like a PM and discuss options of how to foster a better culture of mutual understanding.

Lo que hay que tener en cuenta a la hora de ejecutar y realizar cualquier producto digital, es que debe de ser deseable, viable y factible. Por eso tiene que haber un gran entendimiento y comunicación entre desarrollo y dise?o en la cocreación y en la toma de decisiones del dise?o. Todo ello en un equilibrio entre lo que los usuarios desean y los dise?adores dise?an, la factibilidad tecnológica en la que los desarrolladores la van a desarrollar y la viabilidad económica que sustente el producto.? Por lo cual, la pérdida de egos y una comunicación fluida entre ambos, pueden hacer que cada una de las partes implicadas ?lleguen al entendimiento sobre el dise?o, sabiendo que todos buscan lo mismo, lo mejor para el producto final.

UX designer is an expert in this domain and we can assume that he agreed his design with business owner, so programming competences arent capable of questioning this ?! An author of these questions should reconsider whether using AI algorithms mindlessly is a good idea. ??