The actual job is to create a shared vision of the user experience that aligns every team — design, engineering, QA, and business — around what really matters.
Product management is not just about features or specs. It is about deeply understanding the user’s experience and making that the north star for every decision. The trap most PMs fall into is treating user research as a checkbox instead of the foundation of product development.
The actual job is to build a shared mental model of the user journey that bridges teams with different goals and expertise. Without this, teams operate in silos, success metrics fragment, and the product becomes a collection of disconnected features instead of a coherent experience.
India’s product ecosystem is maturing—companies like Razorpay, Meesho, and Swiggy succeed because they obsess over the end-to-end user journey, not just the technology or marketing. You can do the same by mastering the tools and mindset of user-focused product management.
The trap of fragmented understanding
Different teams see the product through different lenses:
- Engineering focuses on technical feasibility and sprint deliverables.
- Design looks at flows, interfaces, and aesthetics.
- Business teams think about revenue, KPIs, and customer acquisition.
- QA focuses on quality, bugs, and test coverage.
Without a unifying view, these perspectives become fragmented and sometimes conflicting.
The blind men and the elephant syndrome applies here: each team understands only a part of the user experience, never the whole.
Your job is to create artifacts that force conversations and build an aligned mental model. This alignment is not a luxury — it is essential for fast, coherent product delivery with minimal rework.
User journey mapping: the backbone of shared vision
A user journey map is a visual representation of the steps a user takes to accomplish a goal with your product or service. It captures the user’s actions, emotions, pain points, and opportunities at each stage.
Journey maps are effective because they:
- Make complex processes memorable and easy to grasp
- Highlight gaps and friction points in the experience
- Serve as a decision-making tool for prioritization and design
- Create empathy by centering the user’s perspective
- Align cross-functional teams around a common narrative
When to create a user journey map
- Existing problem: When a user journey already exists but you need to understand it better and identify pain points.
- New problem: When you are exploring a new user segment or use case, and you want to visualize their context and needs.
Example: Razorpay’s onboarding journey
Razorpay’s product team uses journey maps to understand the onboarding flow for new merchants. They document each step — from sign-up, document submission, KYC verification, to first payment acceptance. This map reveals where users drop off, what confuses them, and what support they need.
Exercise: Start your own journey map
Pick a product you use daily — it could be Swiggy, PhonePe, or a local service. Write down the steps you take from start to finish to complete a task (e.g., ordering food, paying a bill).
- List each step in sequence.
- Note your emotions or frustrations at each step.
- Identify any moments where you hesitate or need help.
- Share this map with a peer and discuss what could be improved.
From journey maps to personas and empathy maps
A persona is a semi-fictional character representing a key user segment. It synthesizes demographics, goals, behaviors, and pain points.
Empathy mapping complements personas by capturing:
- What users say (their explicit feedback)
- What users think (their motivations, fears)
- What users do (their behavior patterns)
- What users feel (emotions and frustrations)
Together, these tools deepen your understanding of users beyond data points.
Example: Meesho’s reseller persona
Meesho’s core user is a tier-2/3 reseller who often has limited English skills and low digital literacy. The team builds detailed personas and empathy maps to design vernacular content and simple workflows that resonate deeply with these users.
User stories and job stories: translating user needs into features
A user story is a short, simple description of a feature from the user’s perspective. It follows the format:
As a [user type], I want to [action], so that [benefit].
User stories keep teams focused on the outcome, not just the output.
Job stories offer a complementary approach by focusing on context and motivation:
When [situation], I want to [motivation], so I can [expected outcome].
The role of epics
An epic is a large user story that can be broken down into smaller, actionable user stories or tasks. Epics help organize work at a higher level of abstraction.
Example user story map
Imagine a user story: "As a checking account holder, I want to deposit checks with my mobile device, so that I don’t have to go to the bank."
The story map breaks this down into:
- Logging in
- Starting the deposit
- Taking a picture of the check
- Entering transaction details
- Confirming the deposit
Each step becomes a user story with acceptance criteria, ready for sprint planning.
Coordinating teams through sprint ceremonies and backlog management
User stories feed into the product backlog, a prioritized list of features and requirements. Managing this backlog effectively is essential for smooth sprint execution.
Key ceremonies include:
- Sprint Planning: Decide what stories enter the sprint, balancing priority and team capacity.
- Daily Standups: Track progress and unblock issues.
- Sprint Review: Demonstrate completed work and gather feedback.
- Sprint Retrospective: Reflect on what worked and what didn’t to improve future sprints.
Protecting the sprint like your life depends on it
As a PM, you need to shield the sprint from scope creep and shifting priorities that cause rework and burnout. Clear communication about the user problem and acceptance criteria helps keep everyone aligned.
Example: Swiggy’s sprint discipline
Swiggy’s product teams emphasize sprint discipline to deliver customer-impacting features reliably. They use journey maps and user stories to ensure every sprint item ties back to user value.
The PM’s role in unblocking development and ensuring quality
Beyond defining what to build, the PM must proactively unblock development by clarifying requirements, resolving dependencies, and facilitating communication.
You must also work closely with QA and testing teams to incorporate user feedback and ensure the product meets expectations.
This includes:
- Understanding technical fundamentals relevant to your product
- Participating in scrum ceremonies actively
- Planning releases and coordinating cross-team dependencies
- Ensuring minimum rework by defining clear acceptance criteria upfront
The importance of continuous user feedback loops
User research is not a one-time activity. Continuous feedback is critical to validate assumptions and iterate rapidly.
Lean user research methods include:
- Guerrilla usability testing
- Remote prototype testing
- In-depth interviews with representative users
- Analytics-driven hypothesis validation
India’s diverse markets require you to be creative and resourceful in gathering meaningful user insights cost-effectively.
Bringing it all together: a user-focused product delivery cycle
- Define personas and map user journeys.
- Translate user problems into epics and user stories.
- Prioritize the backlog based on user impact.
- Collaborate closely with design, engineering, and QA.
- Protect sprint scope and unblock teams.
- Collect continuous user feedback and iterate.
This cycle keeps the product grounded in real user needs and aligned across functions.
Meeting scene: Aligning teams on a new feature
Sprint planning meeting at a fintech startup in Bangalore
You (PM): “We’ve mapped the user journey for our new payments flow. The biggest friction is in the OTP verification step, where 30% drop off.”
Design Lead: “We can prototype an OTP auto-fill feature to reduce friction.”
Engineering Lead: “Auto-fill requires changes to the mobile SDK and backend. It will take 2 sprints.”
QA Lead: “We’ll need to test across different devices and network conditions to avoid false negatives.”
You (PM): “Let’s prioritize OTP auto-fill in the next sprint and prepare a test plan with QA. I’ll update the backlog with user stories and acceptance criteria.”
The team leaves with a clear, shared understanding of the problem, solution, and next steps.
Without this alignment, teams would build features that don’t solve the real user pain.
Judgment exercise
You are the PM at a Series A Indian healthtech startup building a patient appointment booking app. User research shows patients frequently abandon booking due to confusing insurance verification steps. The design team proposes simplifying the UI, but engineering warns that backend insurance API integration is unstable and will take 3 months to stabilize. The CEO wants a quick fix to reduce drop-offs immediately.
The call: How do you prioritize and communicate your plan to leadership and the engineering team?
Your reasoning:
You are the PM at a Series A Indian healthtech startup building a patient appointment booking app. User research shows patients frequently abandon booking due to confusing insurance verification steps. The design team proposes simplifying the UI, but engineering warns that backend insurance API integration is unstable and will take 3 months to stabilize. The CEO wants a quick fix to reduce drop-offs immediately.
Your task: How do you prioritize and communicate your plan to leadership and the engineering team?
your reasoning:
Slack chat: Translating user feedback into user stories
From the field: Talvinder’s reflection on user focus
Where to go next
- Develop your product vision and strategy: Product Vision and Strategy
- Master user research techniques: User Research Methods
- Learn to write effective user stories and prioritize backlogs: Backlog Management and Agile Planning
- Understand metrics for user engagement and retention: Metrics and KPIs