How to bridge design and development

Updated: Oct 22, 2019

If you've ever had the opportunity to work alongside a designer and a developer, the first thing you'll notice is how different they are from each other. A designer and developer think very differently from each other and for good reason. The designer creates solutions and the developer builds an end product. Unfortunately at times these teams can become dysfunctional. What the designer wants. What the developer wants.

So the question remains, how do you bridge the gap? And why should you care?

What you should do

Designers and developers tend to stay within their own silos and hardly address engaging with the other team unless they absolutely have to. Because they know that the language between them will be different and difficult. Especially having to communicate the end desire. So I would encourage to get outside of your comfort zone and go spend more time outside of your silos. Get involved with the other persons work, pair up more often.

What you shouldn't do

Don't try to avoid the other teams engagements or conversations. It will stop you first from learning and secondly from potentially contributing to a greater picture in the end product. Remember both designer and developer have the same common goal but their immediate goals might appear different. A designer goal isn't to code JavaScript and developer doesn't want to design in a software like Adobe XD. But they are more aligned than they realise.

For more help on this topic, schedule a time with us on our Book Online.


Your white label digital agency in small, repetitive & common tasks

Hire us as your next white label digital agency service and become more productive!

Or hire me as your front-end freelancer.




Milford, Northshore. Auckland.

New business

Copyright Agility Cycle 2019. All rights reserved.

+64 21 025 666 25