Switching from design or business analysis into product management
Designers and business analysts are two of the most common routes into product management, and for good reason. You already sit next to the product decisions. What’s missing is usually not skill, but proof that you can own the decision, not just inform it. Here’s what you already have, what to work on, and how to show it before you have the title.
Why designers and BAs make strong PMs
Product management is about deciding what’s worth building and making sure it works. Designers bring a deep understanding of users. BAs bring structure, data and the ability to get everyone aligned. Both are a big head start.
What you already have
If you’re a designer
- User empathy and research skills. You know how to find out what people actually struggle with.
- Prototyping. You can make an idea real and testable quickly.
- Discovery habits. You’re used to exploring the problem before locking in a solution.
If you’re a business analyst
- Requirements and process thinking. You can turn messy needs into something a team can build.
- Data skills. You’re comfortable digging into numbers to understand what’s happening.
- Stakeholder management. You already translate between the business and the delivery team.
The gaps to close
Get comfortable talking about revenue, retention and cost, not just usability. Tie your design work to a business metric.
Practise choosing between good ideas, and saying what you wouldn’t build and why.
Shift from documenting what stakeholders asked for to questioning whether it solves the real problem.
Move from “here are the options” to “here’s what I recommend, and why”. Ownership is the core of the PM role.
How to prove PM skills before you have the title
- Attach a goal to your current work. Agree what metric your next project should move, and report on it after launch.
- Run one problem from start to finish. Find a real user problem, frame it, propose a test and share the result.
- Write the strategy for your area. One page: the goal, the biggest problems, what you’d do next and what you’d stop.
- Volunteer for the trade-off conversations. Offer to lead a prioritisation session or a roadmap review.
- Tell your manager what you’re aiming for. Ask what they’d need to see before considering you for a PM role.
Reframing your experience for PM interviews
Lead each story with the problem and the result, then explain your part. Use your real numbers, or an honest before-and-after.
How ready are you to be a PM?
Take the free PM Readiness Score: ten quick questions, a score out of 100 and the area to work on first. Or get the LIFT guide, the framework behind everything on this page.
Frequently asked questions
Is it easier to move into PM from design or from business analysis?
Neither is easier across the board. Designers usually find the user side natural and need to build commercial skills. BAs usually find the structure natural and need to practise owning decisions.
Do I need to learn to code?
No. It helps to understand how software is built, but PMs aren’t expected to code. Being able to talk clearly with engineers about trade-offs matters more.
Should I take a junior or associate PM role?
Often yes, if it gets you the title and real ownership. Many career switchers start as an associate PM and move up quickly because of their background.
How do I get PM experience without the title?
Volunteer to own a problem end to end, set a goal for your work and report on it, and write a strategy for your area. That evidence counts in interviews.