<p>Published on <a href="https://blog.prototypr.io/how-to-collaborate-on-design-with-developers-8aac41991194?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Ruchi Goel </p>
<blockquote><p>Good design is about process, not product. — <a href="https://twitter.com/jaredsinclair">Jared Sinclair</a>, Designer and Developer at Bloglovin</p></blockquote>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jBaPdeh98ISNGiyA.jpeg"></p>
<p>But what if the process is at fault? How can it lead to a great User experience? How can the outcome be a user delight?</p>
<p>Considering design and development as two different phases of product cycle, is where the problem lies. If designers and developers are in sync right from the beginning till shipment, then everything gets simpler and the process becomes transparent. Why only designers and developers, in fact the <a href="https://blog.prototypr.io/how-to-achieve-pixel-perfect-front-end-practically-bd990390588">whole team should be on the same page from start to end</a>.</p>
<p>As <a href="https://twitter.com/levie">Aaron Levie</a> (CEO at Box) mentions “<strong>Does it better</strong>” will always beat “<strong>Did it first</strong>”. It clearly advocates the fact that ‘Ease of use’ for users is the ultimate goal.</p>
<p>Thus discussing the facts/ ideas and collecting feedback at every stage is crucial. Although this structured and transparent process always reduces rework and wasted efforts/resources. But when we are starting with it, it may appear as a longer and complicated path but trust me, it’s actually not.</p>
<p>Now the next few questions that surround our mind include — What’s the right process to do it? How should designers communicate design to developers? How to make the process more effective?</p>
<p>Before answering this I would like to mention the pain points which are not addressed when <a href="https://blog.zipboard.co/making-designer-developer-collaboration-easier-adc13e94bc7d">designers and developers</a> work as segregated entities.</p>
<ul>
<li>Design is about senses and dimensions which designers understand the best. Developers have a completely different perspective to see things as compared to designers. But for creating a good user experience it’s necessary that the views of both parties should be aligned.</li>
<li>Usually we consider it enough if only designers understand the design intent as they are designing the product. But we forget it’s the developers who bring design to life. So it’s equally important for the developers too to understand the design intent.</li>
<li>Design is an iterative and evolving process. It’s not a static entity which can be perfected once and for all. There is always room to improve and refine.</li>
<li>Design is about elements. Each element has its own purpose.And each team member should be aware of this purpose in order to do justice with the design.</li>
<li>Due to lack of understanding of each other’s domain; it leads to unnecessary back and forth loops. This results in lot of wasted bandwidth and stretches the QA process to much longer than it should actually be.</li>
</ul>
<h4><strong>How to resolve this?</strong></h4>
<p>Sharing design with developers is not limited to sharing specs, assets, mockups, interactions etc, it also includes understanding the design intent and behaviour for every segment of the application.Clarity of design is integral to each and every phase of the design cycle, be it ideation, wireframing, mockup or prototyping. Thus designers and developers should work as a team to find an optimum solution.</p>
<p>To create best user experiences designers and developers should be open to ideas and cross-collaboration.They should let themselves educate each other. Designers should try to evaluate the design in terms of coding efforts and developers should try to understand the basic design ideology. Cross functional knowledge and dynamic approach really helps.</p>
<blockquote><p>‘Never stop learning’ is the key essence.</p></blockquote>
<p>“I believe that tightly-knit, small, cross-functional teams have a much better chance of delivering value and delight to users.”- <a href="https://blog.zipboard.co/the-design-life-of-a-product-designer-interview-with-matej-latin-dfc8ab920a6">Matej Latin</a></p>
<h3>Some good practices that put you a step closer include :</h3>
<h4><strong>User Testing and Design Validation</strong></h4>
<p>While designing for any web project, design job does not end with finalizing the design. Until the design is shipped the team owns it and should strive for creating the best user experience. For improving user experience, user testing and design validation play an important role. You need to be sure about the usability of the design. Tools that can help you with this include — <a href="http://zipboard.co/">zipBoard</a>, <a href="http://notableapp.com/">notable</a>, <a href="https://usabilla.com/">usabilla</a> etc.</p>
<p>“We invite our developers to sit in on user testing and hear user feedback and if they can’t make it to the actual test they have access to all the videos to watch when they have the time. We also send them clips of important feedback as well so that their time isn’t too consumed by unhelpful feedback”.- <a href="https://uxdesign.cc/how-designers-work-with-developers-7552be5e40e9">Ben Peck</a></p>
<h4><strong>Say no to assumptions and talk about processes</strong></h4>
<p>Designers and developers have their own assumptions about the product. To leave no room for any discrepancies they should <strong>start communicating as early as possible</strong> and nail the core of the problem right from the beginning. Also, if developers know the whole ideology behind the design; then while working in collaboration with designers, they can come up with a better solution. That does not compromise either the design efforts and/or the dev efforts. Designers create design but developer’s inputs while designing can result in a robust design which saves crucial time when creating the end product.Course correction at the initial stage helps mitigate later issues which require more time and effort.</p>
<h4><strong>Keep design consistent and progressive</strong></h4>
<p>Web development is not a one time thing. It’s never done. It keeps growing and evolving everyday. So final design should consider everything, be it different screen sizes, browsers, network speed, OS, geographical locations(lingo options), sets of prospective users etc.</p>
<p>Also, both designers and developers need to understand that they cannot control every pixel. There always exist some dynamic data and the application should be optimized for that. If few pixels of change break the design then it’s not a good design.Good design is not the good interface only, the code behind should also be clean and modular. Good code maintenance is a great boon in the long run.</p>
<blockquote><p>Don’t push yourself for perfection rather stay committed to simplicity, reliability and scalability.</p></blockquote>
<h4><strong>Design keeping development in mind</strong></h4>
<p>If design decisions aim at making the code modular, reusable and consistent then the design ought to have a clean and simple UI. Basic knowledge of HTML and CSS on the designers end can be really advantageous.Some standard practices designers should use include-</p>
<ul>
<li>Reuse same components and views wherever possible.</li>
<li>Maintain consistent color palette, icons etc. or even better if you can build a design system right from beginning.</li>
<li>Use grids and have breakpoints keeping in mind the design responsiveness.</li>
<li>Design in 1x, so that much time is not wasted in computing and knowing margins, padding etc.</li>
</ul>
<h4><strong>Developers should try to understand design intent and motivations</strong></h4>
<p>It’s not the designers only who need to make efforts to make the process effective. Developers too need to step out of their comfort zone. Few things developers can do in this direction are-</p>
<ul>
<li>Read about latest design trends and if possible try to attend design conferences to understand how design impacts customers.</li>
<li>Have some basic knowledge about graphic design, so as participate actively in design discussions.</li>
<li>Get involved while brainstorming for design so that you can straightaway tell what can be developed and what can’t. Thus reducing wasted design efforts.</li>
<li>Try and evaluate the created HTML according to the customer needs.</li>
</ul>
<h4><strong>Design handoff</strong></h4>
<p>Design handoff does not completely define sharing design with developers but is an integral part of it. Now when the design is finalized at designers end, every minute detail about each state/element of design needs to be transferred to the developers. Keeping in mind the iterative nature of design, sharing this huge amount of information for each iteration can be a tedious job. Designers find it difficult to compile all the info and developers fail to maintain it well. A better solution would be to use a dedicated tool for this purpose like <a href="https://zeplin.io/">Zeplin</a>, <a href="https://avocode.com/">Avocode</a>, etc.</p>
<h3><strong>Conclusion</strong></h3>
<p>Having said that all, I’m not at all advocating that development takes priority over design. I just want to emphasize that, to create great user experiences design and development need to go hand in hand, not as isolated processes. As good design attracts users, good code at the backend hooks users to the application. Thus none can sustain without the other. Thus you need to work as a team and collaborate on the design. Don’t just share the assets and measurements pixel by pixel but share the design completely i.e. every aspect of design, right from the possible ideas and approaches to the final prototypes.</p>
<p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%252F%253Fenpose&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=8aac41991194" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://blog.prototypr.io/how-to-collaborate-on-design-with-developers-8aac41991194">How to collaborate on design with developers?</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


How to collaborate on design with developers?

Top Stories