How to Work with Designers Without Losing Your Mind (or Theirs)
Tips to work almost seamlessly with designers
Welcome to No BS Product Management, your weekly guide to mastering the product management journey—from breaking into the role to crushing it as a PM.
Every week, I tackle common challenges that PMs face by sharing straightforward advice, actionable tips, and proven strategies to navigate tough situations, win over stakeholders, and elevate your PM skills.
If you’re ready to stop guessing and start thriving in the world of product management, hit that subscribe button now! 🚀
If you’ve been a product manager for more than five minutes, you’ve probably experienced this tension: PMs and designers don’t always see eye-to-eye. While product managers live in a world of trade-offs, deadlines, and business goals, designers tend to live in the realm of ideals—crafting beautiful, seamless user experiences without always worrying about technical constraints or business realities.
And to be fair, they have a point. Designers have an innate ability to sense what users feel while experiencing the product. But this idealism, when left unchecked, can often clash with the PM’s pragmatic approach to solving problems. It’s not that PMs and designers are at odds; it’s that they speak slightly different languages.
So how do you build a productive, respectful, and collaborative relationship with designers? The answer lies in context, alignment, and a dash of influence.
Why PMs and Designers Often Clash
To understand why PMs and designers don’t always see eye to eye, it’s helpful to step into both their shoes for a moment. While they share the same ultimate goal—building a great product—their priorities, mindsets, and approaches often differ.
The PM Perspective
Product managers live in the world of trade-offs. Their job is to balance user needs, business goals, and technical feasibility while managing deadlines and resources. PMs are pragmatists by nature—always asking:
What’s the impact of this work?
Can we build this within our timeline and budget?
What’s the simplest solution to achieve the desired outcome?
To PMs, the focus is often on shipping a good-enough solution quickly, learning from user feedback, and iterating. They operate with constraints in mind, prioritizing outcomes over perfection.
The Designer Perspective
Designers, on the other hand, are the champions of the user experience. Their focus is on crafting interfaces and interactions that are intuitive, seamless, and delightful. They often think in terms of ideals:
How does this design make the user feel?
Does this interaction solve the problem beautifully?
What’s the best experience we can create?
Designers tend to approach their work with a hypothesis-driven mindset, fueled by user empathy. They’re less concerned with deadlines or business constraints and more focused on solving problems “the right way.”
The Tension Between PMs and Designers
Designers are driven by the desire to craft delightful user experiences. They think deeply about aesthetics, interactions, and how the product feels to the user. Meanwhile, PMs juggle business impact, technical feasibility, and deadlines—essentially, the cold, hard realities of building products.
This disconnect often leads to frustration:
PMs: “Why can’t we ship this faster?”
Designers: “Why are you compromising the experience for speed?”
Add to this the fact that designers often work on hypothesis-heavy mindsets, and you’ve got two teams with very different operating principles. But the truth is, this tension doesn’t have to be destructive—it can actually be productive if approached the right way.
So how do we deal with this? Below are 5 tips from my career, which I have learnt the hard way:
1. Give Designers Business Context Early and Often
Designers need to understand why they’re solving a problem before they can care about how they solve it. Too often, PMs hand over requirements without giving enough context about the business goals or constraints. When designers don’t see the bigger picture, they default to idealistic solutions that may not align with your priorities.
What to do:
Share the business context as early as possible: What are the goals? What’s at stake? Who are we designing for?
Bring designers into roadmap discussions or problem definition sessions, not just execution phases.
For example, instead of saying, “We need to improve signup conversion by 20%,” frame it as:
“Right now, 40% of users drop off on the signup page because the flow feels clunky. If we fix this, we’ll unlock X more users per month, which feeds into our acquisition goals.”
When designers understand the why, they’ll focus their creative energy on solutions that balance experience and impact.
2. Collaborate Early with Engineers
Designers don’t always have the best sense of what’s technically feasible. They might propose a stunning idea that engineers know is weeks or months of work. This disconnect leads to late-stage rework, missed deadlines, and frustration for everyone.
The solution? Early tech reviews.
Involve engineers early when reviewing design ideas so they can flag feasibility issues or offer alternatives.
Make it clear that engineers aren’t there to “shoot down” ideas but to co-create solutions with designers.
For example, a designer might propose a new animation-heavy interaction. Instead of outright saying, “This won’t work,” engineers can explain the technical trade-offs and suggest simpler alternatives that still meet the design goals. This approach prevents last-minute clashes and builds trust between teams.
3. Influence Designers to Embrace Experimentation
Designers tend to approach problems with a high degree of confidence in their instincts—and to be fair, they’re usually pretty good at predicting what will work for users. But the best solutions often come from testing and iteration, not from perfect designs on the first try.
Encourage designers to view their work as hypotheses, not final answers. This mindset shift makes them more open to experimentation, faster iterations, and small wins.
What works:
Use data to validate (or invalidate) design choices. For example, “Your idea for a cleaner homepage made sense in theory, but 60% of users now miss the CTA.”
Frame experiments as opportunities to learn, not to prove anyone wrong.
One thing I’ve found helpful: when a designer is attached to a specific solution, say, “Let’s test it! If it works, great. If not, we’ll learn what doesn’t work and why.” This takes the pressure off their ideas and reinforces a culture of collaboration.
4. Speak Their Language (Hint: It’s Not Just Metrics)
Designers care deeply about users, so if you want to influence them, tie your arguments to user outcomes—not just business goals.
For instance, instead of saying, “We need to cut this feature for launch to meet the timeline,” say:
“If we simplify this feature, we can get it into users’ hands faster and gather real feedback to improve it in the next iteration.”
PMs who focus on both business impact and user experience earn far more credibility with design teams. Remember, designers are not anti-business—they just want to ensure users aren’t forgotten in the process.
5. Treat Designers as Partners, Not Vendors
Nothing kills collaboration faster than treating designers like “executors” of your vision. Good design doesn’t happen in isolation; it’s the result of ongoing dialogue between PMs, designers, and engineers.
Ask for their input early and value their perspective.
Recognize their strengths: Designers often notice details about user behavior that PMs might overlook.
Instead of saying, “Here’s what I need you to design,” try:
“Here’s the problem we’re trying to solve—how do you think we can approach this?”
This small shift in framing goes a long way in building mutual respect.
The PM-Designer Sweet Spot
At the end of the day, PMs and designers are two sides of the same coin. PMs bring pragmatism; designers bring idealism. When these two forces work together, you get solutions that are both beautiful and impactful.
The sweet spot lies in:
Giving designers the business context to solve the right problems.
Bringing engineers in early to balance creativity with feasibility.
Encouraging experimentation and iteration, not perfection on the first try.
Speaking to user outcomes, not just metrics.
Treating designers as equal partners in the product development process.
So..
If you’re a PM who’s frustrated with designers, pause and ask yourself: Am I giving them the tools they need to succeed? Designers don’t want to make your life harder—they want to make the product better. With a little empathy, clear communication, and collaboration, you can turn a strained relationship into one of your strongest partnerships.
After all, the best products happen when pragmatism and idealism work together.