Your team and developers clash on design preferences in a mobile project. How can you find common ground?

Sometimes there actually is no conflict but it seems as though there is one (false dichotomy) - changing the perspective can help in such cases. Similarly, communicating the vision and bringing everybody back on the table, setting and reminding everyone on the shared goal can help to find mutually beneficial solutions which - in case of a true win-win - will be better than the ideas proposed by the opposing parties individually (for they might optimally complement each other).

Understanding each team's needs and constraints is crucial for avoiding conflicts. In a project where designers and developers clashed over a button animation effect, the author realized that both teams aimed for a smooth user experience but had different approaches. Through a brainstorming session, designers shared their ideal UI examples and developers explained the technical implications. The less resource-intensive animation was found, maintaining the design intent. This open exchange demonstrated how each team's priorities contributed to the project's success. By understanding each team's unique challenges and motivations, a solution was created that honored both design vision and technical feasibility.

Instead of a „why“ a better focus when designing products for humans to use should rather be „for whom“. Many proposals can be then exposed as nonsensical.

Fostering open dialogue in a project can help both teams feel heard without fear of judgment. In a previous project, a design team created a complex interface that developers found overwhelming. A meeting was held to address these concerns, encouraging open communication about what and why they wanted. Designers explained the impact of each visual detail on user experience, while developers explained how simplifying certain elements could improve performance and keep the project on schedule. This allowed for common ground and identified non-negotiable design features that could be adapted for efficiency. Regular dialogue fostered respect for each team member's expertise, leading to a collaborative mindset.

When one focuses on what a user actually would need and tries to provide him with just that, many potential conflicts in this regard can be avoided. When a user would love to see the stars, sometimes giving him a telescope is more suitable than a spaceship. Additionally, a good user research ought to give one a better basis to communicate essential features to distinguish them from nice-to-haves.

Effective compromise involves respecting each team's expertise and prioritizing aesthetics and functionality. In an app project, designers wanted a complex navigation structure, while developers were concerned about backend complexity and load times. After multiple discussions, a solution was found that simplified the hierarchy while maintaining the core visual appeal. Subtle transitions were added to preserve the designer's feel while minimizing codebase burden. This experience demonstrates that compromise isn't about giving up, but about finding a way for both sides to move forward with their vision. Collaboration can elevate both form and function.

Setting clear, shared goals is a powerful tool for unifying teams. In a project where designers focused on aesthetics and developers on performance, a goal-setting session was initiated to resolve disagreements. Goals included achieving a specific load time, maintaining a cohesive look across screens, and meeting accessibility standards. This shared language helped both teams understand each other's perspectives during design or technical debates. This aligned everyone, reducing friction and improving decision-making. When both teams worked towards a mutually agreed-upon outcome, debates turned into productive discussions about achieving success.