Designer vs Engineer
The engineer — designer relationship is not one that needs to be fraught with stress and tension. If you are clear from the outset, set out expectations and shared goals, and find ways of collaborating that work for both of you, and communicate effectively from the start, the process could even, dare we say it, be an enjoyable, fruitful and satisfying one!
- Introduce systematization and define every step of the process.
- Designers need to think beyond just delivering the design itself.
- Designers should spend more one-on-one time with engineers.
- Engineers should be familiar with basic fundamentals of designs.
- Designers should act as a supervisors and have much more eligibility in making crucial decisions.
Read the article: UI design implementation guideline for engineers (and designers)
Good communication is key in pretty much any relationship, so it makes sense that it’s a requirement for a smooth design-to-dev handoff.
Communication breakdowns can result in all kinds of issues and misunderstandings—even in different interpretations of the same goals, which can lead to confusing or downright bad UX. And no product team has time for that.
Common problems caused by a bad designer-developer communication are:
- Unnecessary, multiple feedback loops between designers and developers;
- Unexpected quality assurance issues, or QA issues that are more time-consuming than anticipated;
- Inability to leverage overlapping skills ;
- Failure to properly take advantage of new tools that would likely make collaboration easier.
Read full article: A Comprehensive Guide to Executing The Perfect Design-to-Development Handoff