Why Every Designer Should Start Thinking Like a PM

Over the last few roles, I’ve realised it means much more than that.

I started my career in product design, focused largely on the experience: understanding users, designing flows, solving problems and making interfaces work. But somewhere along the way, I became increasingly interested in the decisions happening before the design ever reached Figma.

Why are we building this?
What problem are we actually solving?
What does success look like?
What are the business and technical constraints?
And perhaps most importantly, should we be building this at all?

That shift in thinking changed the trajectory of my career.

In my last role, I moved from being a designer into a Product Lead position. The transition wasn’t really as dramatic as the titles made it sound. I was already getting involved in product decisions, requirements, prioritisation, stakeholder conversations and figuring out what we should build and why. The title eventually caught up with the work.

And I’m seeing a similar thing happen again in my current role.

The more I think beyond the interface, the more opportunities I find myself having to influence the product itself.

That’s why I’ve come to believe that every designer should, at some point, develop a product mindset. Not because every designer needs to become a PM, but because understanding the product makes you a much stronger designer.

You start designing for outcomes rather than just screens. You become more comfortable challenging requests instead of simply executing them. You understand engineering trade-offs better. You can have more meaningful conversations with business and leadership because you understand the problem from more than one perspective.

You also start catching problems much earlier. A bad assumption discovered during a product conversation might take five minutes to correct. Discovering it after weeks of design and development is a very different problem.

For designers who want to build that muscle, start small. Sit in on roadmap conversations. Join stakeholder or sales calls. Ask why before how. Write a PRD for something you’re designing, even if nobody asked you to. Learn the metrics behind the product, not just the interface.

You don’t have to stop being a designer to think like a PM.

If anything, thinking like a PM can make you a better designer — and sometimes, without you even planning for it, it can change the kind of responsibility people trust you with.

So don’t wait for the PM title before you start thinking about the product.

Start with the questions. The title can come later.