Good user experience is not just design — it’s understanding what your users really want and making it easy for them to get it.
User experience is not a checkbox or a phase in development. It is the core of how your product delivers value and keeps users coming back. The trap I see most PMs fall into is treating UX as a design handoff — a task for the design team alone. That is not your job. Your actual job is to understand user intent and behavior deeply, then work with your design partners to create an experience that feels seamless, trustworthy, and useful.
The difference between a product that users tolerate and one they love often comes down to how well the PM integrates UX thinking into every step of the product lifecycle.
Design thinking is your lens to user intent
Design thinking is not just a buzzword — it is a practical approach to solving problems by centering on the user’s experience and needs. It helps you move beyond surface-level requests to uncover what users actually want, often things they can’t articulate explicitly.
The five stages of design thinking are: empathize, define, ideate, prototype, and test. As a PM, your role is to ensure these stages are not skipped or rushed.
- Empathize: Talk to users, observe their behavior, and listen to their pain points. Use interviews, shadowing, and analytics.
- Define: Synthesize what you learned into clear problem statements that capture explicit and implicit needs.
- Ideate: Generate a broad set of solutions without judgment. Encourage creativity.
- Prototype: Build low-fidelity versions of your ideas — wireframes, mockups, or clickable flows.
- Test: Validate your prototypes with real users and iterate based on feedback.
The PM owns making sure the team stays grounded in user intent and behavior, not just stakeholder opinions or feature requests.
Design kickoff meeting at a fintech startup in Mumbai
Design Lead (Anjali): “Users say they want a dashboard with all their transactions.”
You (PM): “That’s the explicit need. But what’s the core problem they’re trying to solve? Is it tracking expenses, budgeting, or something else?”
Design Lead (Anjali): “Good point. Let’s dig into user interviews and see what patterns emerge.”
The team agrees to focus on understanding user intent before locking down features.
The difference between delivering a feature and solving a user problem
User journey mapping aligns teams and surfaces gaps
A user journey map is a visual representation of every step your user takes to accomplish a goal with your product. It captures their actions, thoughts, emotions, and pain points across the entire experience.
Mapping journeys helps your team:
- Break down complex workflows into manageable pieces.
- Identify moments of friction or confusion.
- Understand emotional highs and lows that affect user satisfaction.
- Create a shared mental model across product, design, engineering, and stakeholders.
Journey maps become the foundation for prioritizing features and improvements. They prevent the “blind men and elephant” syndrome — where each team sees only a fragment of the user experience and pulls in different directions.
Choose a key task your product supports (e.g., booking a ride on Ola, ordering groceries on BigBasket). Write down each step a user takes, including pre- and post-interaction phases. For each step, note the user’s goals, emotions, and pain points. Share your map with a peer or your design team to get feedback.
The PM’s role in prototyping and testing
Prototyping is not just the designer’s domain. As a PM, you need to ensure prototypes serve the right purpose and that testing yields actionable insights.
- Help define clear hypotheses for what the prototype should test.
- Work with design to choose the right fidelity: paper sketches, clickable wireframes, or high-fidelity mockups.
- Recruit representative users for testing, focusing on real user segments — not just internal stakeholders.
- Frame test questions to probe usability, desirability, and comprehension.
- Analyze feedback with an eye on the core user problem, not just superficial likes or dislikes.
Remember, testing is not a “yes/no” vote on a design. It is a learning opportunity to refine your understanding of user needs and iterate towards a better solution.
Accessibility and inclusivity are non-negotiable
In India, your product’s UX must work for a diverse user base — different languages, literacy levels, devices, and abilities.
Make accessibility a first-class concern:
- Support multiple languages and scripts, considering regional nuances.
- Design for low bandwidth and older hardware.
- Ensure color contrast and font sizes accommodate visual impairments.
- Provide alternative navigation for users with motor disabilities.
- Use clear, simple language that reduces cognitive load.
Ignoring accessibility means losing large swaths of potential users and failing your core job as a PM: delivering value to all customers.
Collaborating with UX designers: partnership, not handoff
Your relationship with designers is a partnership. The PM brings user insights, business context, and prioritization; designers bring expertise in interaction, information architecture, and visual design.
Best practices:
- Involve designers early in problem definition, not just after requirements are “done.”
- Share user research findings openly and discuss implications together.
- Respect design decisions but challenge assumptions with data or user feedback.
- Co-own the success metrics for the user experience.
- Protect design time from constant scope changes and distractions.
The honest truth about UX metrics
UX metrics are often vague or vanity-driven — “time on page,” “clicks,” “bounce rate.” These don’t tell you whether users are truly achieving their goals.
Focus on metrics that reflect user success and satisfaction:
- Task completion rate: Did the user finish what they came to do?
- Error rate: How often did users make mistakes or get stuck?
- Time on task: How long did it take to complete a key action?
- User satisfaction (CSAT/NPS): How do users feel about the experience?
- Retention and engagement: Are users coming back and using your product regularly?
Use qualitative feedback alongside quantitative data to get the full picture.
Test yourself: The confusing checkout
You are PM at a Series A ecommerce startup in Bangalore. User feedback shows that many customers abandon their cart at the payment screen. The design team proposes adding multiple payment options and a progress bar. Engineering warns that adding options will delay launch by 3 weeks.
The call: What do you prioritize to improve checkout UX, and how do you balance speed to market with usability?
Your reasoning:
You are PM at a Series A ecommerce startup in Bangalore. User feedback shows that many customers abandon their cart at the payment screen. The design team proposes adding multiple payment options and a progress bar. Engineering warns that adding options will delay launch by 3 weeks.
Your task: What do you prioritize to improve checkout UX, and how do you balance speed to market with usability?
your reasoning:
Field exercise: Empathy mapping your user
Take 20 minutes to create an empathy map for your primary user segment. Divide a page into four quadrants: Says, Thinks, Does, Feels.
- Says: What users say about their needs and frustrations.
- Thinks: What users might be thinking but not saying openly.
- Does: The actions users take related to your product or problem.
- Feels: The emotions users experience during the journey.
Use user interviews, support tickets, or your own experience to fill in each quadrant. Share this map with your design partner to align on the user mindset.
Where to go next
- Deepen your user research skills: User Research Methods
- Learn about product discovery frameworks: Product Discovery Techniques
- Build effective product requirements: Writing PRDs
- Understand design principles for PMs: Design Principles for Product Managers
PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, Amazon, and dozens of other companies.