User experience is the attitude or reaction a user has towards your product. It is the art of studying user behavior and psychology to provide them with an advanced experience.
User experience design is not just about the interface or the pixels on the screen. It is the culmination of every interaction a user has with your product—before, during, and after use. Your actual job as a product manager is to understand the user's behavior and psychology deeply, then combine that insight with your business goals and technical possibilities to create a superior experience.
If you miss this, your product risks being ignored, abandoned, or worse, disliked.
User intent is the foundation of UX design
The starting point for any UX effort is understanding why users behave the way they do. What motivates them? What are they trying to achieve? Where do their needs lie on the spectrum from explicit requests to implicit expectations?
You can map user observations along two axes:
-
Explicitness: How clearly does the user articulate their needs? Sometimes users say exactly what they want. Other times, their behavior implies needs they cannot or will not verbalize.
-
Specificity: How precise or general is their intent? Some users know exactly what they want; others are exploring or unsure.
This matrix helps you categorize user intent:
| SPECIFIC | GENERAL | |
|---|---|---|
| EXPLICIT | "I want to find a specific recipe." | "I want to browse recipes by category." |
| IMPLICIT | "I want to be inspired to cook something." | "I'm not sure what I want; help me figure it out." |
Understanding where your users fall in this matrix guides your design choices. For example, a user who explicitly wants "budget controls in online banking" must see those features clearly. But implicit needs—like feeling that money transfers are secure—require subtle design cues that build trust.
The trap many PMs fall into is designing only for explicit needs and missing the implicit ones that build loyalty.
The hierarchy of UX needs
One framework I use to prioritize UX investments is inspired by Maslow's hierarchy of needs. Users expect your product to meet certain foundational requirements before they appreciate enhancements.
The hierarchy looks like this (from bottom to top):
-
Site Availability
The digital page or app must be reliably available across devices. If your site is down or slow, users will leave immediately. This is non-negotiable. -
Usability
Users must be able to navigate easily. Buttons should be clear and responsive. Text must be legible—no bright pink text on a pink background. Confusing navigation or unreadable text drives users away. -
Supportive Features
These are "hand-holders" that guide users through tasks. For example, a floating reminder on the checkout page nudging users to complete their purchase. -
Confidence
Users should feel confident in your product. Amazon’s success partly comes from the trust users have built through reliable service, easy returns, and membership perks. This confidence encourages greater time and money investment. -
Desirability
These are the "delighters." Features that aren’t necessary but keep users engaged and coming back. Amazon’s dash buttons for frequently purchased items are an example—they simplify repeat buying and make users feel valued.
Good PMs ensure their product meets each layer before chasing the next.
Pick a product you use regularly in India — Swiggy, PhonePe, Flipkart, or any local app.
- Evaluate its availability: Does it load reliably across your devices?
- Check usability: Is navigation intuitive and text legible?
- Identify supportive features: Are there helpful nudges or guides?
- Consider confidence: Do you trust this product enough to spend time or money?
- Spot desirability elements: What features delight or surprise you? Write down which layers the product excels in and where it falls short.
The UX Honeycomb: six facets of user experience
Another way to break down UX is through the UX Honeycomb model, which highlights six critical qualities:
- Useful: Does the product fulfill a real user need?
- Usable: Can users interact with it easily and efficiently?
- Desirable: Does the design evoke positive emotions and appeal?
- Findable: Can users find what they need quickly?
- Accessible: Is the product usable by people with disabilities?
- Credible: Does the product inspire trust through quality and reliability?
This model reminds you that UX is multi-dimensional. For example, a feature might be useful but not findable, or desirable but not accessible.
Indian products must pay special attention to accessibility, given diverse user capabilities and device types.
Layers of user experience: from abstract to concrete
Jesse James Garrett’s Elements of User Experience framework breaks down UX into five layers:
-
Site Objectives & User Needs
Balancing product goals with what users actually want. -
Functional Specifications & Content Requirements
Deciding what content is needed and how to organize it. -
Information Architecture & Interaction Design
Structuring information and defining user interactions. -
Interface, Navigation & Information Design
Creating wireframes and flows that stakeholders understand. -
Visual Design
The final polish—the "icing on the cake" that attracts and delights.
Understanding these layers helps you communicate better with design and engineering teams and ensures nothing is overlooked.
Design review at an Indian fintech startup
Designer: “We've created wireframes focusing on easy navigation and clear calls to action.”
You (PM): “Good. How does this support our core user need for quick bill payments on low-end devices?”
Designer: “We've minimized images and optimized for slow networks to improve availability and usability.”
You (PM): “Perfect. Let's test this with users in Tier-2 cities to validate.”
The PM ensures design aligns with both user needs and business goals.
Bridging user needs with technical constraints
Measuring UX to drive better decisions
Measuring user experience is essential. Without data, you’re flying blind and guessing what users want.
There are two types of UX metrics:
-
External metrics: Reflect the environment around your product. For example, customer support ticket volume or offline visits.
-
Internal metrics: Reflect user interactions within your product. For instance, how often users hit the back button, or abandon forms.
If many users frequently click the back button, it signals they aren’t finding what they want. This insight guides where to improve navigation or content.
UX measurement aids leaner product management and better decision-making.
The trap of ignoring implicit needs and metrics
Many teams focus only on explicit user feedback or flashy features. They miss the implicit requirements that build trust and loyalty.
For example, users may never say “I want a secure payment experience,” but if your app shows no security cues, users will hesitate to transact.
Similarly, ignoring metrics like navigation paths or drop-off rates hides critical UX failures.
Your actual job is to connect these dots—explicit feedback, implicit behavior, and metrics—to deliver a cohesive, trusted experience.
Test yourself: The UX design trade-off
You are PM at a Series A Indian e-commerce startup. The engineering team wants to launch a new feature for personalized product recommendations. Usability tests show it slows page load times by 30%, causing a 15% increase in cart abandonment. Marketing insists it drives engagement. You have limited engineering bandwidth.
The call: How do you decide whether to launch the recommendation feature now? What metrics and user behaviors do you prioritize?
Your reasoning:
You are PM at a Series A Indian e-commerce startup. The engineering team wants to launch a new feature for personalized product recommendations. Usability tests show it slows page load times by 30%, causing a 15% increase in cart abandonment. Marketing insists it drives engagement. You have limited engineering bandwidth.
Your task: How do you decide whether to launch the recommendation feature now? What metrics and user behaviors do you prioritize?
your reasoning:
Where to go next
- If you want to learn how to talk to users effectively: User Research Methods
- If you want to translate user insights into design specs: Product Design & Prototyping
- If you want to measure product success with data: Metrics and KPIs
- If you want to understand accessibility in Indian products: Inclusive Design Principles />