{"id":9988,"date":"2014-06-05T22:10:51","date_gmt":"2014-06-05T20:10:51","guid":{"rendered":"https:\/\/usersnap.com\/?p=9988"},"modified":"2025-10-01T08:44:07","modified_gmt":"2025-10-01T06:44:07","slug":"designers-venus-developers-mars","status":"publish","type":"post","link":"https:\/\/usersnap.com\/blog\/designers-venus-developers-mars\/","title":{"rendered":"Designers are from Venus, developers from Mars"},"content":{"rendered":"\n

Every good web team should have at least one designer and one developer. I think we can all agree this is out of the question. Of course, you will need to have other \u201ctitles\u201d to keep everything going, but today we will focus on these two because we think we can help you make them more efficient without hacking their comfort zone.<\/p>\n\n\n\n

We know that because we are a team<\/strong> of designers and developers and we are using<\/strong> the same approach. It helps us work better together, be more efficient and have fun at the same time.<\/p>\n\n\n\n

What is the problem anyway?<\/h2>\n\n\n\n

If you are running an agency or a web project team you probably heard conversations like this one:<\/p>\n\n\n\n

\"Designer<\/figure>\n\n\n\n

<\/p>\n\n\n

Try Usersnap for Your Project<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

<\/p>\n\n\n\n

I am sure you have similar misunderstandings<\/strong> in your own team. The problem is that the designer is approaching the problem differently compared to the programmer.<\/strong><\/em><\/p>\n\n\n\n

For him\/her moving a layer 3 pixels left is 11 milliseconds, but for example, this can be 30 min of work for a developer and usually, he\/she will use the same words – \u201cmove this layer 3 px left, please\u201d. There is no such thing like layer for the programmer.<\/p>\n\n\n\n

On one hand, you\u2019ve got the designer\u2019s creativity and thinking about the details and on the other hand is the way how the programmer thinks about a problem and what is his\/her approach to finding a solution.<\/p>\n\n\n\n

Let\u2019s not go deeper but this is a problem and we know how to easily solve it.<\/p>\n\n\n\n

The Solution<\/h2>\n\n\n\n
\n

I\u2019ll keep telling you how we actually solve issues<\/strong> like that in our team and in our clients\u2019 teams.<\/p>\n<\/blockquote>\n\n\n\n

Please read carefully because this is how you can solve your communication issues<\/strong>, make your team more efficient and ultimately have 8 man-hours more per week. That\u2019s a whole day!<\/p>\n\n\n\n

We are using something called \u201cvisual annotated screenshots\u201d in order to help designers and developers to be on the same page.<\/p>\n\n\n\n

Instead of \u201cCan you move this (pointing at your monitor) 3 pixels to the left?\u201d how about this?<\/p>\n\n\n\n

\"can-you-move-these-3px-to-the-left-pleas\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

The designer<\/strong> can show what exactly he\/she needs, using the tools that any designer is familiar with.<\/p>\n\n\n\n

The developer<\/strong> will get a bug report in the project management system you are using with all the necessary details, plus:<\/p>\n\n\n\n