By Joshua Kraus

How Designers and Developers Can Learn to Like Each Other

By Joshua Kraus

History is filled with legendary rivalries. Ali vs. Frazier. Tesla vs. Edison. Coyote vs. Road Runner.

But the rift between designer and developer eclipses them all. While both disciplines are necessary to create an effective application, the working relationship is often an uneasy one, fraught with conflict and misunderstanding.

Designers, for example, are miffed when they feel the developer isn’t honoring their vision. Developers, on the other hand, are irritated when the designer delivers an unworkable model. Designers can seem overly nitpicky, while developers can come across as small minded.

The Root Of The Problem

The designer/developer schism is rooted in each party’s misunderstanding of the other’s mindset and discipline.

A designer is tasked with envisioning how something will look, feel, and behave, but they’re not responsible for executing that vision. Thus, their design might be unfeasible or impractical.

A developer must translate a designer’s vision into a working product, even if that means altering, trimming or rejecting part of that vision due to technical constraints.

This can be frustrating for the developer, especially if they mistake a designer’s unrealistic demands as a sign of disrespect to the developer’s craft.

When all these wires get crossed, the relationship suffers, and so does the end product. But designers and developers are not fated to butt heads forever. Here is how the two can cultivate stronger, more productive relationships.

Empathize With Each Other

Ah empathy, sympathy’s more exhausting cousin.

To empathize with another person is to see the world through their eyes. And no, it doesn’t require invasive surgery.

A designer should try to empathize with a developer’s technical capabilities and limitations. Developers can create some pretty marvelous things, but they’re not gods. A website that simulates what it’s like to ride a dragon through the Horsehead Nebula might sound wonderful, but the technical demands of such a project may be a smidge too high.

Designers also need to empathize with a developer’s unique working situation. While a developer may have the technical prowess to build something, factors such as time and budget can put a stop to their plans.

Meanwhile, a developer must empathize with a designer’s priorities. Web designers aren’t artists so much as they are problem solvers, and if they’re being too nitpicky or too fanciful, it’s not for the sake of preserving their artistic integrity; it’s because they believe the developer’s changes or rejections will negatively affect the end product.

It’s important to remember that it’s a designer’s job to be nitpicky. There is a rainbow of difference between purple and blue violet; an ocean between 40px and 44px.

Good designers are detail-oriented by nature. Their goal isn’t to give developers a hard time, it’s to create the best product.

Understand The Basics Of Each Other’s Discipline

Empathizing with one another is a great start, but the best designer/developer relationships are forged when each party understands the basics of the other’s discipline.

A good designer should be familiar with the capabilities and limitations of web development essentials, such as JavaScript, HTML and CSS.

For example, to a designer with very little development knowledge, changing a drop down box to multi-select check boxes might not seem like such a big deal, but to a developer, it might shake the project’s very foundation.

A designer who understands basic web development principles will also know that:

  • It’s rarely necessary to design things in 300dpi. Stick with the web-friendly 72dpi unless told otherwise.
  • Including five different fonts in a design might look great, but most web fonts cost money and have large file sizes. Default to standard fonts when possible.
  • Using 20px for the margin-top in one spot, then switching to 25px somewhere else can severely complicate the development side of things. Same goes for different font sizes and colors.
  • Things that are easy in Photoshop such as type on a path are not well-suited to browsers.

But the road goes both ways. A good developer should familiarize themselves with design basics such as color theory, alignment and navigation models.

Understanding how each aspect of a design contributes to the overarching goal of the site can give developers a greater appreciation for the smaller details they would have otherwise dismissed. Aesthetic choices which can appear arbitrary may actually serve an important purpose. Something that seems like mere decoration may actually be a crucial design element.

Communicate Better

Miscommunication is the well from which so many problems spring. While empathy and understanding are a necessary first step, engaging in accurate and meaningful communication is paramount to a successful relationship. By the way, bookmark this article if you ever need marriage advice.

Good communication is about honesty and education. Rather than stew silently at their respective desks, designers and developers need to clearly and respectfully explain why something can’t be done, or why that something absolutely needs doing. Only then can they begin to resolve the issue.

For example, a developer may start fuming after receiving multiple designs that are technically unfeasible, but if that developer doesn’t communicate to the designer the exact nature of the problem, those fumes will reach hazardous levels.

A designer may propose a feature they know is difficult to implement, but rather than drop it in the developer’s lap and walk away, perhaps the designer wants to work with the developer to solve the problem together. If the designer doesn’t communicate this to the developer right away, the developer is going to assume the worst.

Developers should also consider defining the technical requirements of the project as early as possible. This way, the designer is aware of factors like resolution and screen size, site architecture and application flow, which can cut down on potential problems down the road.

Ongoing Collaboration

If the designer hands over their work and skips town, that’s not a relationship, it’s an assembly line.

Rather than remain completely independent from each other, designers and developers should engage in ongoing collaboration. Questions will arise, errors will accumulate and ideas will evolve. Talking through new developments ensures that each party is on the same page, and that the solution will be attacked from all angles.

Ongoing collaboration also pushes each party to their fullest potential. You may not always agree, but a little conflict challenges everyone involved to work harder, aim higher and think more critically.


By setting aside egos and walking a day in the other’s shoes, designers and developers can build the trust, rapport and respect necessary for any relationship to thrive. Talk through issues rather than assume the other is incompetent. Learn the basics of each other’s discipline in order to plan ahead and ask the right questions.

Designers and developers, with your powers combined, simulating what it’s like to ride a dragon through the Horsehead Nebula may just become a reality. And no, of course I didn’t write this article solely in the hope of inspiring someone to create said simulation. That would be ridiculous.

  • sizenz

    Isn’t it about time that “designers” code their own front-ends and become what is now commonly called a Front-end Engineer? Are Engineers not in fact Designers? and Engineers do actually develop websites. I do understand that aesthetic design work does need to be done but design work for websites goes way past making things look pretty, it involves designing around known technologies.

    Anyone who only wants to design pretty looking pictures should stay in print and leave web design to people who understand and can develop their own designs in beautifully crafted HTML and CSS first and then use another Web Designer who specializes in more technical front-end engineering to do the things they aren’t able to do themselves. If this is the case then there should be no designer developer problems as designers are developers and developer are designers.

    Design: form follows function.

  • Craig Buckler

    Good designers who understand front-end development are rare.

    Would you trust someone to design a car or bridge without a solid foundation in aerodynamics and physics? Yet companies expect graphic designers to design web sites because … “it’s just pictures and text isn’t it”?

    Similarly, good programmers are rare and those who understand design are rarer.

    Collaboration and communication is key but that can break down when one party becomes responsible for the other’s training.

  • valzyb

    The suggestions are good, about doing your front-end code. However, that is not always the reality. Many times I have offered to give developers code and was told to do a photoshop layout. So, I think the problem does lie in clear communication. Or, the timelines need to have design built into the process. Something like this: Meeting 1 – Photoshop layout and discussion, Meeting 2 – Front-end code prototype and discussion, Meeting 3 – Discuss any challenges implementing back-end code.

    • Kenneth Davila

      I prefer a designer gives me a comp image or a layout instead of HTML and CSS. Usually the designers I work with have bad HTML and CSS skills. They understand it but when I look at what they do in SASS and how verbose the HTML is, I go and clean it up because I don’t want that in my front-end. I think designers should understand the technology, but they shouldn’t use it. It’s very difficult to do cognitive and logical thinking at the same time, if not at all impossible. Design is by nature a cognitive approach, programming and development is a logical approach. This is why the two sides will always bump heads. I say designers should work within tools and methodologies that feed that cognitive side and allow developers the engineering freedom to take that comp/wire-frame and use their tools and a design inspired style guide to make it happen. If designers want to become more proficient with HTML and CSS they’ll end up spending less time on layout alignment, use of negative space, grid spacing and all the small details that make a design polished. I see a lot of cookie cutter design work out there because the art from web design is gone since designers want to code HTML and CSS. Also leave the javascript alone, that’s nice you found a cool plugin but an engineer should make those decisions on what code goes into production.

  • Great post but I have to admit that it feels weird that it isn’t coming from an actual Web Designer/Developer.

    Simon Ramsay I 110% agree that designers should code their own front-ends, but I wouldn’t call someone that does it an “engineer”. I have to admit, it sounds flattering tho :)

    Anyone who only wants to design pretty looking pictures should stay in print and leave web design to people who understand and can develop their own designs in beautifully crafted HTML and CSS…

    Boy, couldn’t agree more. Can’t stand shortsighted designers that want to be in the web design space without wanting to learn HTML and CSS… or worse, improve the little they already know. What a waste of knowledge.

    Craig Buckler, Indeed good designers who understand front-end development are rare. Funny thing is when someone (managers mostly) bumps into one they can’t process that the person is very much capable of doing both very well. Saddening if you ask me.

    Haven’t met the first that truly appreciates such talent (maybe just one person).

    And to be more on-topic, as a designer that understands HTML and CSS very well, I have never, ever, had a single experience with fellow web developers/programmers where we can’t communicate, or can’t understand each other, or can’t collaborate together. I’m knowledgeable in what I know: web design and HTML/CSS. And can pretty much “go at it” (in good terms obviously) with any developer/programmer at any time when it comes to those topics. Maybe they see me as knowledgeable and don’t see a reason to argue any decisions I make on the design and the implementation of that design.

    Actually, I have more friction with other designers than I have with developers/programmers. Weird.

  • Actually good designers who understand front-end development are “NOT” rare, because I am one of a Front-end Web Developer (HTML, CSS/LESS, JavaScript, AJAX, JSON, Gulp and as well as PHP) who translated from Graphic/Print design background. I have capability to translate designer mock-up into web-base coded prototype, and from prototype to production environment.

    As long as the person who has passionate about what is he/she willing to do, something is possible. It’s just about the matter of time and efforts. Please do not judge too early.

Get the latest in Entrepreneur, once a week, for free.