When developers resist making design changes, it's important to understand why. They don't have time or they misunderstand your goals. Start with a frank conversation. Explain how the change will improve the product. Don't insist on a solution. Offer alternatives, taking the developer's opinion into account. Compromise can lead to better results than rigidly imposing a concept. Create a collaborative environment where developers feel that their ideas are valued. It is important that everyone is on the same page and working to improve the product, not in conflict.

Breaking through developers' resistance to design feedback requires a blend of empathy, collaboration, and clear communication. Start by understanding their concerns are they facing technical constraints, unclear guidelines, or simply feeling their expertise is being challenged? Frame feedback as a shared goal rather than a directive: How can we make this work within the constraints? Involve them early in the design process to build ownership and reduce friction. Use data-driven reasoning to support design decisions, making it less about opinion and more about user experience. Most importantly, foster mutual respect when designers and developers see each other as partners, resistance turns into problem-solving.

Creating a receptive feedback culture means making feedback a collaborative conversation. Invite developers to co-create solutions, share context on user impact, and use concrete examples to illustrate design choices. Empathize with technical challenges, encourage open dialogue, and celebrate successes together.

- Align feedback with shared goals. Highlight how design enhances usability and efficiency. - Speak their language. Tie design feedback to performance, scalability, or user experience. - Involve them early. Collaboration from the start reduces friction later.

One approach I believe would be beneficial is to "Frame feedback as a conversation." The idea is to move away from a top-down, directive style and foster an open, two-way dialogue. Instead of presenting feedback as simply identifying what’s wrong, encourage discussions about design decisions. For instance, you could ask, "What’s your take on this design choice from a technical standpoint?" or "How do you think this approach will affect the development process?" This turns feedback into a collaborative conversation rather than just a critique.

As an Android developer, I break through resistance to design feedback by framing it as a conversation, showing empathy for technical challenges, and providing specific, actionable suggestions. I encourage a receptive feedback culture by actively listening, asking questions, and clarifying design choices, fostering a collaborative environment where feedback is valued and implemented.

Para romper la resistencia de los desarrolladores a los comentarios sobre el diseño, es clave aplicar estrategias que fomenten la colaboración y el entendimiento: ✅ Claridad y especificidad → Explicar el impacto del diseño en la experiencia del usuario con ejemplos concretos. ✅ Enfoque en el usuario final → Relacionar el feedback con la funcionalidad y usabilidad del producto. ✅ Feedback constructivo → No solo señalar problemas, sino proponer soluciones viables. ✅ Consideración de viabilidad técnica → Adaptar sugerencias a las limitaciones del código y recursos disponibles. ✅ Capacitación en diseño centrado en el usuario → Mostrar cómo la usabilidad mejora la eficiencia del desarrollo.

Conocer su lenguaje ayuda a poder comunicarse mejor con ellos y expresarse correctamente, también es bueno dar más de una opción considerando sus capacidades y tiempos. Siempre es bueno no estar cerrado y abrirse a escuchar lo que tienen que decir.

Es esos casos es emplear la comunicación efectiva y así se entiende las ideas en el contexto a debatir y se nutren los participantes de los intercambios de comunicación y conceptos que se puedas abordar