Managing Design Handover

Drive consistency, strengthen communication and transform the design-to-development process

This article is an excerpt from the Marvel eBook, The Book of Collaboration: Handoff Edition.

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.

“Great products come from harmony between the design vision and technical details. Collaboration is the method for creating that harmony.”

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.

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’s better for the business and users. The developer wants to ensure the new implementation isn’t adding technical debt or causing additional work, again because this is better for the business and users.

“Designers and developers competing during this phase is a shame because both perspectives are important. Design and development concerns shouldn’t compete — they should support one another. Both teams are trying to create a great product, and all concerns should be welcome if they support that goal.”

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’s goals.

It’s destructive to teamwork and removes important opportunities for both designers and developers to do their best work.

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’t be further from the truth. Even the best design mockup can’t foresee every technical challenge or hurdle during implementation.

“A mockup is a plan, and even the best plans have to adapt.”

Your team can remove common frustrations and conflicts by approaching this phase of each project differently.

Build better products, in harmony

With this eBook, you’ll find the frustrations and set-backs that occur during the design-to-development process highlighted and challenged with forward thinking solutions.

Explore new ways to get cross-functional teams on the same page, every step of the way.

Download the free eBook 📚

Writing for Marvel. Writing for fun. Eating everywhere, all the time.

Related Posts

We’re really (really) excited about bringing User Testing to your prototyping experience in Marvel. It’s a game changer for your workflow and enables anyone in your team to spin up a user test and validate prototypes with users, stakeholders and colleagues, in just a few clicks. We’re getting closer to the public release, and following our last preview on how… Read More →

One of the lesser known features of Marvel, but one that saves minutes and hours of manual work is our support for hotspot templates by using Symbols in Sketch when syncing your prototypes. Here’s a typical use case – you are working on an iPhone prototype which has 3 buttons in the Tab Bar which appears in the footer on… Read More →

Why the time has come for disruptors in the financial industry Many factors play into this, but the big ones are changes in regulation and technology. Regulation, especially in the UK, has encouraged competition in retail banking for a few years now — and more changes are on their way in the form of required open banking APIs, for example…. Read More →