• Anthony Short, almost 5 years ago

    Everyone has mentioned good points already, but here's a few others that might help.

    Do some user research. Nothing works better than data proven the design is better. If you can show your designs with and without the changes to an audience quickly, you can prove that a slight animation actually increases usability. But be prepared to be wrong.

    Create a design system if you don't already have one. Developers understand the need for systems that solve many problems. If they understand the design system they'll be able to implement it knowing that it will be used again and again. Get them to help design the system too so they understand the decisions for the type and spacing scale.

    If they just don't care about getting the finer details right – spacing, type, color – then you're going to have a hard time getting past that. Creating a design system can help, but you'll need to have a front-end developer on the team who cares about those details.

    Try to relate your concerns with problems they understand. I've often related design quality to code quality. Engineers have linters, formatters, and best practices. They're often pretty OCD about it. The same way they do code reviews, they should be doing design reviews. The same way they have tech debt from corners cut, there's design debt from corners cut. There's common ground there.

    Finally it can come down to your influence of the team. Small things like speaking confidently, standing tall, and being assertive shows people that they can't just take the easy way out and that this is important. Make sure your arguments for change are strong and you're not just doing it because "it looks cool". Don't sacrifice the details that you can't necessarily measure for impact.

    Also, don't think of it as "dealing" with developers. They have concerns and some of them will probably be important. The team needs to work as a unit. Without that you'll always run into issues.

    2 points
    • Account deleted almost 5 years ago

      "If they just don't care about getting the finer details right – spacing, type, color – then you're going to have a hard time getting past that. Creating a design system can help, but you'll need to have a front-end developer on the team who cares about those details."

      EXACTLY. Why no one seems to see that it's the devs that need to work on their cooperative skills, too??? So are they just machines to write code or do they want to be integrated into the proces? If they want to be integrated, they need to follow some rules. If I want to talk about coding, I have to respect THEIR rules. If they want to talk about creation, they need to respect the designer's rules.

      0 points