How to work with PMs who like to design 💪


Welcome back. No matter how stressful your week may get, just remember: There’s no way it’s as stressful as the week the engineering team at CrowdStrike is having (you can read about the chaos right here). Life is all about perspective, huh?

—Tommy (@DesignerTom)


The Wireframe:

  • The Venn diagram of PMs and designers
  • What PMs need to know about design
  • Some great UX jobs

Navigating the PM x Designer Overlap

If you’ve ever lived with a roommate, partner, or really anyone…you know things run more smoothly when everyone knows their role: toilet paper buyer, dishwasher unloader, Netflix curator, etc.

Design-focused teams are no different: We can do our best work when it’s clear who’s supposed to do what and when. But? That’s not always easy to accomplish.

Enter: the designer x PM dilemma. These days, there is more overlap than ever between the job descriptions of designers and PMs. In fact…

  • Over 50% of PMs surveyed by creator (and fellow PM) Aakash Gupta said they wireframe.
  • But when I reviewed 30 PM job listings recently, only one mentioned design output…compared to 30 design jobs that required it.
  • Often, PMs are tasked with championing a user-centric approach and establishing a product vision—roles that can blur responsibilities between them and designers.

Navigating this dynamic can be tricky, but it doesn’t have to be a minefield. Today, I’m running you through my tips for understanding ownership, collaborating effectively, and working with your team…instead of against it.

Let’s get into it.

Starting here: Succeeding on an empowered team requires mapping out core roles and responsibilities. I like this breakdown from Aakash →

But there’s an important caveat: This split should never be one-size-fits-all. It’s an evolving back and forth between designers and PMs to determine what works for your team and your needs.

Next up: Once you’ve gotten a feel for the right breakdown for your org, it can be helpful to put yourself in your counterpart’s shoes. Since most UX Tools readers are designers, we’re going to focus on how designers can think like PMs to better engineer for cohesion.

I loved the responses from PMs on Shreyas Doshi’s question on X, “What do you wish designers understood better about product management?” Here are some standouts →

  • “Users are not always customers—b2c best practices aren’t necessarily appropriate in a b2b context.”
  • “There are times for pragmatism. There are times for boldness. Don't let the pragmatic decisions of today deflate the boldness of your designs for tomorrow. We need design to always aim higher.”
  • “Minimum Viable Products—how to slice the design into the bare minimum needed vs. extra features down the line.”
  • “A better sense for the feasibility of the various things they are proposing and why some things might be too expensive to build than others.”

On the flipside: I hear from PMs who want to close the gap between a designer's idealism and their business context all the time. If PMs and designers spent a little more time openly talking about how each other could be most empowered to do good work…imagine what kind of products design teams could be shipping.

And maybe we could shrink some of the distances between PMs and designers as seen here:

No matter what your role is, though, understanding how to function on a unique team will always be a crucial skill. Trust me—I haven’t always had it.

Six years ago, I was the first design hire for a PM who had been designing. He handed me wireframes with pre-decided information architecture and user flows. At the time, I saw this as an overstep. Initially, I handled it poorly by getting defensive, creating friction, and working in isolation. What I should have done, though?

  • I should have leveraged his interest in wireframing to benefit our collaboration instead of getting defensive about my role.
  • I should have earned his trust by enhancing his ideas in ways he couldn't instead of creating unnecessary speed bumps.
  • I should have built stronger bridges for his input, such as creating teardowns of similar products and discussing what he liked about them, instead of putting myself in a silo.

We all live and learn, and I’m proud to say that I’m much more adept at bridging gaps between PM and design team members today than I was back then. As far as I’m concerned, making your team work well is about three core elements of effective collaboration:

  1. Leveraging PM interest: Instead of seeing PM wireframing as an intrusion, view it as a starting point for deeper collaboration. Use their wireframes to understand their vision and suggest enhancements that align with design best practices.
  2. Building trust: Show PMs how you can elevate their ideas. Work together on refining wireframes and turning rough sketches into polished designs. This will help build mutual respect and trust.
  3. Creating structured feedback loops: Establish regular check-ins and collaborative sessions where both parties can share ideas and feedback. This ensures that both the design and product visions are aligned and that there are no surprises later in the process.

When you master this collaborative dance, PMs and designers can become the strongest duo on the team. By leaning into each other's strengths and working towards a shared vision, you can create products that are not only user-centric but also innovative and successful.


TOGETHER WITH FRAMER

Designing a Website 🤝🏻 Building a Website

If you’re a designer tasked to create and publish visually stunning websites, there’s a tool for that. If you want to boost creativity while speeding up the overall web development process, you need Framer—no coding required.

The next best no-code website builder for designers, Framer:

  • feels and works like Figma and other design tools you know
  • lets you publish your design as a real website in seconds
  • supports breakpoints, animations, and even a whole CMS

Plus, you can even import designs from Figma using our Figma-to-Framer plugin so you don’t have to start from scratch.

Are you ready to learn how Framer can streamline your web development process? Learn more now.


News, Tools, and Resources: Knowing Your Role

Got a great tool, podcast episode, idea, or something else? Hit reply and tell me what’s up.


The UX Tools Job Board

Hiring for a design role, or know someone who is? Submit it here to hit the inboxes of 75k+ talented designers.


Thanks for reading! Do you have any tips for working with PMs who design? Hit reply and let me know.

Enjoying this newsletter? Let us know here.

UX Tools

UX Tools is a weekly deep dive into the tools and trends shaping how we build products. Each week, Tommy (@DesignerTom) breaks down emerging tools, analyzes industry shifts, and shares practical insights drawn from 15+ years shipping products. Join 80k+ builders, makers and designers getting deep analysis and tool discoveries that help you build better products, faster.

Read more from UX Tools

Welcome back. We're combining this week's Leaks issue with a lookback at what we learned on the streets of Config. We're one week removed from Figma's largest feature announcement, and the dust has settled. In fact, most of the design industry has moved onto talking about Airbnb's new design (with mixed reviews), Google's impressive Material 3 launch, or Bungie's alleged design theft. But behind the glossy announcements and fancy demo videos, there's something bigger happening that I can't...

Welcome back. It’s Config week, I’m flying out today, and we’re deep in party planning mode for Detach. But I had to hit send on this. Friday’s leak of Inflight was one of our most opened issues of the year. So today, we’re going deeper - not just on the tool, but the problem it’s trying to solve: Feedback still sucks in 2025. Even for good teams. Even for my team, working on the UX Tools redesign and survey right now. Here’s what we’re learning, and why Ridd’s Inflight is onto something...

Welcome back. Recently, I've noticed a shift. It started as a gut feeling: the apps I remember most aren’t the smartest. They’re the strangest. The most emotionally tuned. The ones that feel handcrafted when everything else starts to blur. These interfaces aren’t just challenging best practices, they’re often rebelling against them. While most teams optimize for speed and scale, a few are quietly chasing something else: depth. They’re not adding features, they’re adding weight. And it’s not...