(Yes, We’re Turning the Tables This Time)
Last month, we shared a post about what developers wish designers knew. Now it’s time to flip the conversation.
Because as much as we developers love to joke about logo-final-FINAL-v3.png and mysterious button-like shapes with no annotations, the truth is, designers have a few frustrations of their own — and they’ve got receipts.
To gather some real-world perspective, we reached out to our designer community, including a shoutout to the incredible creatives in the Freelance Rockstars Facebook Group led by Julie Cortés.
If you’re a freelancer looking to grow your business, sharpen your communication skills, and surround yourself with smart, supportive people — you’ll want to check it out.
Here’s what designers had to say — and how we can all do better.
Design Is More Than “Making It Pretty”
Good designers don’t just make things look nice. They’re building entire systems that:
- Support usability and hierarchy
- Guide the eye toward key conversion points
- Create consistency across screens and platforms
When developers make small changes like swapping a font, resizing graphics, or adjusting spacing “just to make it work,” it can unravel the logic behind the whole visual experience.
Alicia White of Alicia in the Wild
Our take: Clean builds start with clear communication. Don’t assume. Ask.
Pixel-Perfection Isn’t the Goal — But Precision Still Matters
Designers know the web isn’t print. Things will shift, stack, and reflow across breakpoints. But there’s a difference between responsive adaptation and a build that only vaguely resembles the mockup.
Designers want:
- Consistent spacing and alignment
- Proper font sizes and hierarchy
- Colors and visuals that reflect brand and accessibility standards
Jen Rarey of Rarified Creative
Our take: Pixel-perfection is unrealistic. Pixel-respect isn’t.
Designers Need Communication Too
Designers don’t love surprises — and neither do devs. The earlier both parties can collaborate on how things work, the better. Especially when it comes to UX behavior and platform constraints.
Tom Byer
This isn’t just sass — it’s a real breakdown in collaboration and expectations. Whether it’s tools, UX limitations, or platform constraints, devs and designers need to open the door to clearer conversations.
Our take: This isn’t about saving time — it’s about protecting the integrity of the design and the user experience.
Accessibility and Usability Are Shared Responsibilities
Designers think about legibility, contrast, type hierarchy, and button accessibility from the very beginning. Developers are responsible for upholding those choices during the build.
Changes to styles, spacing, or functionality can unintentionally reduce readability or accessibility.
Our take: If a design doesn’t work for web or accessibility standards, it’s a conversation — not a silent substitution.
Respect the Creative Process
Just like developers have systems and standards for writing clean, functional code, designers have a process for building intentional visual frameworks. “Quick tweaks” often have ripple effects.
When developers make changes without understanding the visual logic, the result feels disjointed — and sometimes unrecognizable from the original design.
Our take: Designers aren’t trying to be difficult. They’re trying to keep the product cohesive. Collaborate instead of overriding.
The Bottom Line: Collaboration Wins
Whether you’re on Team Design or Team Dev, the goal is the same:
A clean, functional, well-branded, user-friendly site.
Designers aren’t trying to micromanage. Developers aren’t trying to ignore the design. Most frustrations come from unclear expectations and missing communication.
So talk early. Talk often. Work together. Respect each other’s zones of genius. That’s how great websites get made.
Want a dev team that actually loves working with designers?
👉 Let’s talk.