small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

Still can’t get a UX job? Give up.

large_featuredImage

medium_featuredImage

small_featuredImage

thumbnail_featuredImage

Sticking to UI/UX trends is a losing strategy

<p><a href="http://ift.tt/2pVXsbB">uxdesign.cc &ndash; User Experience Design &mdash; Medium</a> | Rishabh Saxena <img alt="" src="http://ift.tt/2qCu8U0"></p>
<h4>A round up from interviews on how product designers collaborate with developers</h4>
<p>Products revolve around people and even on the development front, a major part of a product designer’s workflow is collaborating with people, especially developers. Whether it is discussing features, or brainstorming on design, or providing feedback on prototypes — productive collaboration is a key ingredient for a successful development and design team. To create a successful product, the entire team has to be on the same page and in sync.</p>
<p>There are many tools — some visual based, others task based — also dedicated to design collaboration such as <a href="http://zipBoard.co">zipBoard</a>, <a href="http://invisionapp.com/">InVision</a>, <a href="https://slack.com/">Slack</a> and <a href="https://zeplin.io/">Zeplin</a>. In light of this, we spoke to some product designers about what their collaboration cycle with developers is like.</p>
<blockquote><p>How do you collaborate with developers?</p></blockquote>
<h4><a href="https://twitter.com/benpeck">Ben Peck</a></h4>
<p>Ben Peck is product design director and has worked with brands like Nike, Needle, The North Face, Oakley and Adidas. He is also the co-founder of Front Conference, a product design and management conference held in Utah.</p>
<p><img alt="" src="http://ift.tt/2pW9kKF"></p>
<p><em>“</em>We sit with all our developers and talk with them everyday. We’re constantly working together as we design to gauge technical feasibility, timelines, capabilities and to stay up on the latest technological advancements. After designing, prototyping and testing solutions we’ll have a more official review with all the dev leads as a final sign off before it gets into development so everyone is on the same page. We do a pretty good job not having too many group meetings to stay as productive as possible. We have as many over the shoulder conversations as we can unless we see that it’s necessary to bring everyone together.</p>
<blockquote><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.</p></blockquote>
<p>When designs have been tested and approved we use a tool called <a href="https://zeplin.io/">Zeplin</a> to hand over the designs to the developers. It’s a simple tool to allow developers to pull all the assets and specs for the design without needing to ask us a lot of questions, need documentation or own Sketch. Our developers have found it very useful in getting what they need with the least friction.<em>”</em></p>
<h4><a href="http://ift.tt/2qC4Bdp">Matej Latin</a></h4>
<p>Matej Latin is lead UX/UI designer at Auto Trader. He is also involved with projects such as Better Web Type and Gutenberg — A Web Typography Starter Kit.</p>
<p><img alt="" src="http://ift.tt/2pW9iCx"></p>
<p><em>“</em>I find collaboration with developers daunting and exciting at the same time. My first official job was at a bank in a very corporate working environment. There I’d be told by someone what needs to be done and I had to get it done with the IT department. But 9 times out of 10, I was rejected and told that it couldn’t be done. I soon learned that developers don’t like to be told what to do and how exactly to do it. Later I took my coding skills to the next level and it helped me a lot in improving my communication with developers. Now I prefer to work very closely with developers. Whatever company I work for, I always advocate for lean and agile methodologies.”</p>
<blockquote><p>I believe that tightly-knit, small, cross-functional teams have a much better chance of delivering value and delight to users.</p></blockquote>
<h4><a href="http://ift.tt/JOmBJR">Dan Saffer</a></h4>
<p>Dan Saffer is a product design leader. He has worked with Mayfield Robotics, Jawbone and Smart Design. He is also the author of four books on design.</p>
<p><img alt="" src="http://ift.tt/2pW55Pu"></p>
<p>“Extremely closely. We have developers and engineers going out with us when doing user research.</p>
<blockquote><p>We sit in on sprint planning and help write <a href="http://ift.tt/16LMdgM?">Jira</a> tickets so that the right features get built in the right order, the right way.</p></blockquote>
<p>We’re constantly going back and forth on <a href="https://slack.com/">Slack</a> to discuss features and implementation.”</p>
<h4><a href="http://ift.tt/1MgYr8k">Phillipe Hong</a></h4>
<p>Phillipe Hong is a UI/UX designer, Art Director and Front-developer. He has worked with brands across the board like L’Oreal, Nespresso, Michelin and Schneider Electrics.</p>
<p><img alt="" src="http://ift.tt/2pWb4DE"></p>
<p>“I like to work with devs, and as a designer, I think it’s essential to be able to communicate with devs when you’re designing.”</p>
<blockquote><p>I use Zeplin to send my design to devs, but I’m still struggling to find a way to give feedback to them. May be zipBoard can solve this problem for us.</p></blockquote>
<h4><a href="http://ift.tt/2qCpgxR">Faruk Ates</a></h4>
<p>Faruk Ates is a product designer at Quantifind and has previously worked at Apple, Edyt and Apture. He is also the creator of the open source tool Modernizr.</p>
<p><img alt="" src="http://ift.tt/2pVXDUk"></p>
<p>“It’s a really great collaboration for me because I’m a former back– and front-end developer myself, so we speak the same “language” when we discuss concerns like performance, features, ideas, technology stacks, and so forth.</p>
<blockquote><p>I’ve always advocated for designers to understand at least enough about the technology stack they’re designing; for that they can have clear and useful discussions with developers about all the aspects of the product.</p></blockquote>
<p>Every day in my own job, I’m reminded of the tremendous added value it brings.”</p>
<h4><a href="http://ift.tt/2qCu72o">Gabor Lenard</a></h4>
<p>Gabor Lenard is a Digital Product Designer, currently building <a href="http://zenvite.com/">Zenvite</a> — a platform to create smart invitation pages.</p>
<p><img alt="" src="http://ift.tt/2pVNjM6"></p>
<p>“We discuss ideas at the whiteboard. Then we need to elaborate and formalize the results. Developers expect clarity, ​thoroughness and a coherent vision from me. So I have the responsibility to think through the problems and special cases before delivering user stories, wireframes or mockups.”</p>
<blockquote><p>I always put a lot of effort into coming up with good drawings, even for purely conceptual ideas because they are powerful and people tend to refer to pictures even if there’s a text with more details. Another good method is formulating everything from the user’s perspective in “first-person” narrative: this makes it easier to understand the people, the product is made for.</p></blockquote>
<h4><a href="http://ift.tt/2qCijx1">Michael Lee</a></h4>
<p>Michael Lee is a Product Designer at <a href="https://www.sunrun.com/">Sunrun</a>. He has also worked as Design Producer at Google and Product Designer at Chatous &amp; BayLaunch.</p>
<p><img alt="" src="http://ift.tt/2pW56Ty"></p>
<blockquote><p>I collaborate with developers by clearly communicating my designs through words and via software such as <a href="https://zeplin.io/">Zeplin</a> and by making prototypes the developers can access and see my designs in motion.</p></blockquote>
<p>“I also do regular checkins and design reviews to make sure everything is going according to plan.”</p>
<h4><a href="http://ift.tt/1K0n2jo">Nikkel Blaase</a></h4>
<p>Nikkel Blaase is a digital product designer at <a href="https://www.xing.com/">Xing</a>. He is the founder of <a href="http://ift.tt/2oSMpMh">Design Made For You</a> studio and has also created Unstuck Map.</p>
<p><img alt="" src="http://ift.tt/2qC92oP"></p>
<p>“First of all, I consider user experience design as the responsibility of the whole product team, not only the designer. This is why I think designers are also enablers for design.</p>
<blockquote><p>Usually, product becomes more successful when developers work with the user’s experience in mind.</p></blockquote>
<p>Besides that, I prefer to sit closely to the developers, so that we can easily discuss layouts and technical restrictions, or can make fast decisions. Communication is a key factor when it comes to collaboration with developers.”</p>
<h4><a href="http://arlojamrog.com/">Arlo Jamrog</a></h4>
<p>Arlo Jamrog is a Senior product designer at <a href="https://www.strava.com/">Strava</a>, a social network for athletes. With fifteen years of experience Arlo has worked with different teams on design and development of projects ranging from record labels to architecture firms to leading advertising agencies.</p>
<p><img alt="" src="http://ift.tt/2pVOMSG"></p>
<p>“It depends on the developer, but the thing I think what matters the most as a designer working with developers is being able to articulate why your design decisions are made.</p>
<blockquote><p>If as a designer you don’t understand your own process and aren’t able to communicate it, you won’t be able to rally anyone around your thinking and a lot will get lost in translation.</p></blockquote>
<p>Another thing I like to do is ask developers to review my design work while it’s in progress. Oftentimes they’ll have a better understanding of data, edge cases and a familiarity with other parts of the system that I may have missed.”</p>
<h3>Final Thoughts</h3>
<p>A Product Designer is the champion of users and their needs. <a href="http://ift.tt/2qCvbmM">Working effectively with developers</a> and the entire team is extremely important to ensure a smooth and cohesive development process. Whatever tools a product designer may use to work with developers, the entire team has the responsibility of working in tandem and this can be ensured by the <a href="http://ift.tt/2kRDxZn">product manager</a>. The key is clear communication and building a coherent philosophy about the product that everyone on the team understands.</p>
<p>You can read all the interviews in full <a href="http://ift.tt/2qCroG5">here</a>.</p>
<p>If you enjoyed this article, <a href="http://ift.tt/2pW57qA">find more of my writings on Medium</a>, where I write about front-end design, user experience and places to look for inspiration.</p>
<p><iframe src="http://ift.tt/2iFGGW9" width="800" height="400" frameborder="0"><a href="http://ift.tt/2h0f00F">http://ift.tt/2h0f00F</a></iframe><img src="http://ift.tt/2qCv9eE" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="http://ift.tt/2pVVjN7">How Designers Work With Developers</a> was originally published in <a href="https://uxdesign.cc">uxdesign.cc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


How Designers Work With Developers

How Designers Work With Developers

A round up from interviews on how product designers collaborate with developers

Top Stories