{"id":17556,"date":"2019-04-15T12:34:02","date_gmt":"2019-04-15T11:34:02","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=17556"},"modified":"2020-11-12T11:45:06","modified_gmt":"2020-11-12T11:45:06","slug":"managing-design-handover","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/managing-design-handover\/","title":{"rendered":"Managing Design Handover"},"content":{"rendered":"

This article is an excerpt from the Marvel eBook, The Book of Collaboration: Handoff Edition<\/a>.<\/em><\/p>\n

Many designers and developers hesitate at the idea of collaboration because it sounds like accepting compromises. Nowhere is this dilemma more apparent than when our workflows overlap and the design is ready for developers to begin building.<\/p>\n

<\/div>
<\/svg><\/div>

\u201cGreat products come from harmony between the design vision and technical details. Collaboration is the method for creating that harmony.\u201d<\/p><\/span><\/blockquote>\n

When designers deliver a complete design mockup to developers for implementation, both sides tend to view it as a competition; both sides are pushing for their own concerns and trying to avoid unnecessary compromises and wasteful rework.<\/p>\n

If the designer gets their way, the developer must make a sacrifice, and vice-versa. The designer wants to avoid major changes and is invested in seeing the design vision achieved accurately because it\u2019s better for the business and users. The developer wants to ensure the new implementation isn\u2019t adding technical debt or causing additional work, again because this is better for the business and users.<\/p>\n

\"\"<\/a><\/p>\n

\u201cDesigners and developers competing during this phase is a shame because both perspectives are important. Design and development concerns shouldn\u2019t compete\u200a\u2014\u200athey should support one another. Both teams are trying to create a great product, and all concerns should be welcome if they support that goal.\u201d<\/span><\/p>\n

This is why teams should change how they approach the transition from design to development. The old way is damaging and sets up unhealthy competition when everyone should be collaborating and supporting one another\u2019s goals.<\/p>\n

It\u2019s destructive to teamwork and removes important opportunities for both designers and developers to do their best work.<\/p>\n

The other downside is that when designers hand over source files so developers can take over the project, this implies that design work is done, which couldn\u2019t be further from the truth. Even the best design mockup can\u2019t foresee every technical challenge or hurdle during implementation.<\/p>\n

<\/div>
<\/svg><\/div>

\u201cA mockup is a plan, and even the best plans have to adapt.\u201d<\/p><\/span><\/blockquote>\n

Your team can remove common frustrations and conflicts by approaching this phase of each project differently.<\/p>\n

Build better products, in harmony<\/h2>\n

With this eBook, you\u2019ll find the frustrations and set-backs that occur during the design-to-development process highlighted and challenged with forward thinking solutions.<\/p>\n

Explore new ways to get cross-functional teams on the same page, every step of the way.<\/p>\n

Download the free eBook<\/a> \ud83d\ude80<\/p>\n

\"\"<\/a><\/p>\n

Further reading:<\/h3>\n