We hear this question far more often than you'd think.
From our conversations with over 3,000 designers in India - across Bangalore, Mumbai, Pune, Hyderabad, Chennai, and remotely from Canada, UAE, and Ireland - we estimate that at least 40% vocally express interest in moving toward product management at some point in their career. That's not a small number. Nearly half the designers we speak to are, at some level, thinking about this transition.
And why wouldn't they? It seems like a natural ladder. "Over the next five years, I want to be a product owner." "I want more decision-making power." "I want end-to-end ownership of the products I'm designing and building." These are things we hear constantly.
The Interaction Design Foundation calls UX-to-PM "a resounding yes" for a career move [2]. UX Planet describes it as "a natural step if you want more influence over product decisions" [3]. The internet is full of playbooks for making the switch.
But before we get to the how, I want to spend some time on a question that almost nobody asks: why?
First - Let's Get the Labels Straight
Before anything else, let's clear up something that causes a surprising amount of confusion - even among experienced professionals.
When people say "I want to become a product manager," they often mean different things. There are three roles that get conflated constantly, and understanding the distinction matters because each requires a fundamentally different skill set [4][5].
Product Manager.This is a strategic role. A PM owns the product vision, the roadmap, the prioritisation of what gets built and what gets cut. They don't manage people - they manage the direction of the product. They sit at the intersection of business, technology, and user experience, making decisions about what the product should become and why. Their job is to ensure that what the team builds delivers value to the customer and the business.
Product Owner. This is a tactical role, most common in Agile/Scrum environments. A PO manages the product backlog - the prioritised list of user stories and features that the development team works on sprint by sprint. They represent the voice of the customer within the development cycle. Where the PM thinks in quarters and years, the PO thinks in sprints and releases.
Project Manager. This is an execution role. A Project Manager coordinates timelines, resources, dependencies, and deliverables. They make sure the work gets done on time and within scope. They manage the how and when, not the what and why.
Here's the critical detail most people miss: the word "manager" in Product Manager doesn't carry people management power. Unlike a Design Manager or Engineering Manager, a PM typically has no one reporting to them. They don't control performance reviews, promotions, or team allocation. Their authority comes from influence, not hierarchy - which, ironically, is both the role's greatest appeal and its greatest frustration.
What a Product Manager Actually Does
Let me strip away the job descriptions and tell you what the day-to-day actually looks like.
A product manager manages the things that the overall product is supposed to deliver. They're not the business owner - they don't set the company strategy. They're not the technology expert - they don't write code or architect systems. They're the person who connects these worlds. Roadmaps, versioning, what gets delivered this quarter, what gets deferred to next, what customers are asking for and how those requests get prioritised against business goals.
To many cross-functional teams, this looks like a middleman role. And honestly, in poorly run organisations, that's exactly what it becomes - a relay station between business leadership and delivery teams. But when done well, the PM role is far more than that.
Consider four core capabilities of any organisation: operations, business, engineering, and design. A product manager can move through each of these with more ease than most specialists. They don't go deep - they go across. They understand enough about each domain to ask the right questions, identify the right trade-offs, and make informed decisions about priority.
But here's the nuance: nobody is born a deep generalist. You grow from one specialism to many, from depth to breadth. That's why you'll notice that some product managers are more business-oriented - because their origin was in business. Others lean technical - because they came from engineering. And others are more customer-centric and experience-driven - because they came from design.
When you look at it from that standpoint, almost anyone can become a product manager. The question isn't whether you can. It's whether you should.
The Question Nobody Asks: Why?
This is where I want to be direct, even if it's uncomfortable.
When a designer tells me they want to become a product manager, I always ask the same question: why?
The answers tend to follow a pattern. And most of them reveal that the desire isn't about product management at all - it's about something the designer feels is missing from their current role.
"I want more decision-making power." Design has decision-making power. Design managers, heads of design, chief design officers, chief experience officers - these are real positions with real strategic authority. The problem isn't that design doesn't have a leadership ladder. The problem is that at many Indian companies, that ladder is underdeveloped or invisible. We explored this reality in detail in The UX Career Ladder Is Broken in India - the ladder exists, but navigating it requires a different strategy than most designers expect.
"I want more ownership."You can have ownership in design. The question is whether your organisation gives it to you - and whether you've positioned yourself to demand it. Often, product managers struggle with ownership too. They have shallow knowledge across every function they work with, which means no one fully trusts their judgment in any single domain. They have positional authority but lack the depth to back it up. And they frequently find themselves fighting to justify their seat at the table - just like designers do.
"I want to work more closely with the business."That's what head designers, pre-sales designers, and design managers are supposed to do. If you're not doing it in your current role, the solution might be to redefine your role, not abandon your discipline.
"I want more influence over what gets built."Neither do most product managers - especially the ones who don't understand how technology actually works. Influence comes from credibility, not from a title.
I'm not saying these aren't real frustrations. They are. And for some designers, the frustration is genuine enough that product management is the right move. But for many - more than will admit it - the pull toward PM is really a pull away from a design career that feels stuck. And if the root cause is that your design career lacks growth, switching disciplines doesn't fix the root cause. It just relocates the symptom.
Let me be blunt about one more thing. The salary difference is real. PM roles in India often pay 20-30% more than equivalent design roles at the same level. That's not a gimmick - it's a market reality. But if money is the primary motivation, know what you're trading for it: you'll spend less time doing the work you trained for, more time in stakeholder management and alignment meetings, and your impact will be measured in roadmap delivery and business metrics rather than in the quality of the experience you built. For some designers, that trade-off is worth it. For many, it isn't - they just don't know that yet.
For the Right Reasons - Here's How to Actually Prepare
Now, for everyone who's genuinely thought this through - who understands what they're giving up, what they're gaining, and why product management is the right path for them - the preparation is both simpler and harder than you think.
Simpler because you already have half the skill set. As a designer, you understand users. You know how to research, synthesise, and translate insights into direction. You've worked cross-functionally. You've navigated ambiguity. These aren't small things - they're foundational PM skills. Harder because the other half - the half that makes or breaks a PM career - requires a genuine shift in how you think.
Show ownership beyond design delivery.
This is the single most important signal you can send. Before you ever apply for a PM role, demonstrate to your current leadership that you're willing to own not just the design delivery but the end-to-end delivery of a business requirement turned into a product need.
What does this look like? You stop waiting for the PM to define the problem and start bringing problems to the table - with supporting data, a proposed scope, and a recommended approach. You don't just hand off designs; you follow through to implementation, launch, and post-launch measurement. You start asking "did this work?" instead of "does this look right?" This isn't a small shift. It changes how your team sees you, how your leadership sees you, and how you see yourself.
Grow your vision from design consistency to business roadmap.
As a designer, your scope of vision is often the product experience - consistency, usability, delight. As a PM, your scope expands to the entire roadmap: what gets built this quarter, what gets deferred, what gets killed, and why. Start practising this now. Can you articulate your product's roadmap - not just the design portion, but the full picture? Do you know what the engineering team is prioritising and why? Do you know what the business team's revenue targets are for the next two quarters? If you don't, you're not ready for a PM role. Not because you lack the capability, but because you haven't yet developed the habit of thinking at roadmap level.
Build cross-functional knowledge - real knowledge, not surface awareness.
This goes beyond "I collaborate well with engineers." You need to understand, concretely:
What technology your engineering team uses and what its limitations are. What compliance requirements your product must adhere to - GDPR, RBI guidelines, industry-specific regulations. What's happening in your industry that affects product strategy - competitive moves, regulatory changes, market shifts. What your sales funnel looks like - how leads become customers, where they drop off, what the support team hears most often. How your marketing team positions the product and where that positioning diverges from the actual experience.
A survey of product professionals found that 57% of participants believe their PM is "still too tactical and not strategic enough" [1]. The PMs who avoid that trap are the ones who've built genuine depth across these domains - not just familiarity, but working knowledge.
Start influencing decisions with more than research findings.
As a designer, you typically influence through user research - "here's what users told us, here's what we observed, here's what we recommend." That's powerful, but it's one lens.
As a PM, you influence through a synthesis of user needs, business constraints, technical feasibility, and operational capacity. Start practising this now. When you present a recommendation, don't just ground it in what you learned from users. Ground it in what you know about your organisation's current operational capabilities, its engineering bandwidth, its revenue model, and its competitive position. This is the shift from "here's what's right for the user" to "here's what's right for the product given everything we know." That second statement is what product management sounds like.
Watch Out for These Catches
This is a long-term transition.You will have to demonstrate end-to-end ownership over months, possibly years, before anyone considers you for a PM role - especially if you don't have a PM title on your resume. That's uncomfortable for designers who are used to being valued for visible, tangible output. The ownership work is less visible and slower to compound.
Many PMs still don't understand what they're supposed to do.Almost 50% of product management teams fail to have a consistent or well-defined process [1]. You might transition into a role where the expectations are unclear, the organisation hasn't figured out what it wants from product management, and you end up doing what your boss wants rather than what the product needs. Be honest about whether you'd be walking into a PM-shaped hole or a PM-shaped opportunity.
The grass isn't as green as it looks.PMs spend enormous amounts of time in alignment meetings, stakeholder management, and priority negotiations. If what you loved about design was the craft - the research, the synthesis, the act of creating something - you will do significantly less of that as a PM. Some designers make the switch, realise they miss the work, and come back. There's no shame in that - but it's better to know it before you switch.
The title alone doesn't give you what you're looking for. If you want decision-making power, the title "Product Manager" doesn't automatically grant it. Just as "Design Manager" doesn't automatically grant strategic authority - as we explored in Design Leadership Is in Turmoil- the PM title faces the same inflation. There are PMs who shape strategy and PMs who take orders. The difference isn't the title. It's the person, the organisation, and the culture.
Or - Stay in Design and Build the Same Capabilities
Here's what I want to leave you with, and it's something that most UX-to-PM guides won't tell you.
Everything a good product manager does - cross-functional influence, business understanding, strategic thinking, roadmap awareness, stakeholder management - is available to you within design. You don't have to change disciplines to build these skills. You have to change how you operate within your discipline.
The best design leaders I've worked with - the ones at VP, Head of Design, CDO level - have all of these capabilities. They understand the business as well as any PM. They influence roadmaps. They speak the language of revenue, retention, and operational efficiency. They just do it while also maintaining the deep craft and user understanding that makes design irreplaceable.
The path isn't PM or bust. The path is: become the kind of designer who operates at a level where the PM distinction becomes irrelevant - because your influence, your ownership, and your strategic contribution already transcend the boundaries of your title. This is what the best senior designers are doing right now - we explored exactly what that looks like in The UX Job Market Has Changed. Your Strategy for Getting Noticed Hasn't.
That's the path we help designers build at Xperience Wave. Whether you ultimately move into product management or grow into design leadership, the preparation is the same: develop the ownership, the cross-functional fluency, and the business acumen that makes you indispensable - regardless of what your title says.
We're already en route with a couple of designers on exactly this journey. If you're considering it, talk to us. We'll help you figure out whether PM is actually the right move - or whether what you're really looking for is a design career that's finally operating at the level it should be. Book a strategy calland let's have the conversation.
Sources & References
- [1] WebinarCare / Product Management Statistics 2024. Survey of product management professionals. Findings include: 50% of PM teams lack consistent process; 57% of participants say PM is "still too tactical and not strategic enough"; organisations waste 12% of resources due to ineffective product management. https://webinarcare.com/best-product-management-software/product-management-statistics/
- [2] Interaction Design Foundation. (2026). "What Is Product Management?" Confirms UX-to-PM transition as viable, emphasising need for strategic thinking and business acumen. https://ixdf.org/literature/topics/product-management
- [3] UX Planet. (2025). "How to Transition from UX to Product Management in 2025." Describes UX-to-PM as "a natural step" for designers wanting more influence. https://uxplanet.org/ux-to-product-management-transition-2025-ec436aa9f635
- [4] Asana. (2025). "Product Manager vs Project Manager: Key Differences." Clear delineation of PM (strategic, what/why) vs Project Manager (execution, how/when). https://asana.com/resources/product-manager-vs-project-manager
- [5] Contentsquare. (2026). "Product Owner vs Product Manager: What's the Difference in 2026?" PM as strategic, PO as tactical - distinct but complementary roles. https://contentsquare.com/guides/product-management/product-owner-vs-product-manager/
Further Reading on Xperience Wave
- The UX Career Ladder Is Broken in India. Here's the Path That Actually Works
- What Each Level of the UX Career Ladder Actually Looks Like in India
- Design Leadership Is in Turmoil. And No One's Talking About It
- The UX Job Market Has Changed. Your Strategy for Getting Noticed Hasn't
- 5 Things Senior Designers Should Be Doing With AI - None of Them Involve Figma Plugins
About the Author
Shaik Murad is Co-founder and Head of Product & Design at Xperience Wave, a UX design studio based in Bangalore, working across designer mentorship, UX services for businesses, and a design community of 1,000+ designers.
- Murad, Co-founder & Head of Product & Design, Xperience Wave
