Experienced product teams value user research, as they should, but new entrants are often misled by famous quotes that seem to dismiss it.
User development is one of the most important things you will do as a product manager. It is the first phase in the lifecycle of a new feature or product — the moment you discover who your users really are and what problems they face. Without this foundation, everything else — product definition, implementation, launch, and evaluation — is guessing.
Today’s users are more diverse than ever. Even within a seemingly homogeneous demographic, the needs and behaviors vary widely. Use cases evolve continuously, and new services disrupt old models. Pain points that were once hidden become visible and urgent.
This lesson demystifies user development for you and shares actionable tips to do user research faster and smarter. You will learn how to find your users, understand their needs, and develop user models that guide your product decisions.
Why user research is non-negotiable
Two famous quotes often cause confusion:
“If I’d asked customers what they wanted, they would have said a faster horse.” — Henry Ford (supposedly)
“It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.” — Steve Jobs
These statements are sometimes used to dismiss user research altogether. “Well, Jobs didn’t do it!” is a common retort.
Let me be direct: Experienced product teams value user research, as they should. The new entrants who disregard it based on these quotes are misled.
User research is critical because:
- You will talk to customers and users every day — not just once.
- Your goal is to learn who to build for, not just what to build.
- You need to test assumptions, challenge biases, and discover unmet needs.
User research is a foundational technique that underpins every product decision you make.
The challenges of user research in practice
Everyone agrees user research is important; very few actually do it consistently. Why?
- It is time consuming.
- Outcomes are difficult to interpret.
- There are many techniques, which can be complicated to navigate.
In practice, you must balance research rigor with business constraints. The real world demands speed and efficiency.
Product team weekly sync, Mumbai-based fintech startup
You (PM): “We need to understand why onboarding drop-off is so high. Let’s schedule user interviews.”
Engineering Lead: “We don’t have bandwidth for lengthy interviews right now — sprint deadlines are tight.”
Marketing Head: “Analytics show the drop-off, but I’m not sure what questions to ask users.”
You (PM): “Let’s do short, focused sessions with a small set of users early mornings — breakfast works better here. We’ll keep it to 30 minutes max.”
This is how real teams balance constraints and still get meaningful user insights.
The challenge of fitting user research into a busy product schedule
You do not need to conduct 100 interviews or run complex surveys. Instead, prioritize techniques that give the biggest insight per unit time. For example, in-depth interviews with a small, representative sample often yield more actionable findings than broad but shallow surveys.
What user development actually means
User development is the process of discovering and understanding your users deeply. It involves:
- Discovering who your users are.
- Identifying their problems and pain points.
- Understanding their needs, behaviors, and current workflows.
This knowledge shapes your product’s value proposition and feature set.
User development is not a one-time task. It is ongoing — you keep refining your understanding as new data and feedback come in.
User research goals in the discovery phase
When you start user development, your goals are:
- Discover the customer or user.
- Discover the problems they face.
- Understand their needs, behaviors, and current ways of working.
You are not yet deciding what to build. You are building a knowledge base to inform those decisions.
The risk of designing for yourself
One of the biggest traps is assuming your own preferences and experiences reflect your users’. You are not your users.
You need to design for their needs, not yours. Otherwise, the product will miss the mark.
What user research captures
User research uncovers:
- Goals — What users want to achieve.
- Attitudes — How users feel about their tasks and tools.
- Motivations — Why they do what they do.
- Mental models — How users think about their problems.
- Relationships — Who influences or affects their decisions.
- Pain points — Frustrations and blockers they face.
- Environment — Physical and social context of use.
- Processes — Steps they follow to complete tasks.
Understanding these dimensions helps you create products that fit real user contexts.
Why you must focus on specific user types
If you design for everyone, you end up pleasing no one.
Good products focus on specific user types. You identify segments and archetypes that share attributes and needs.
User archetypes and personas
We use archetypes and personas to model user types.
- Archetypes are broad roles or models. For example, Joseph Campbell’s Hero archetype or the Wise Mentor.
- Personas are specific instances of archetypes, fictional but grounded in research, representing real user groups.
Personas give you a clear target to aim for when making product decisions.
Examples of archetypes from popular culture
| Archetype | Description | Example from "Harry Potter" |
|---|---|---|
| The Hero | The main character driving the story | Harry Potter |
| The Wise Mentor | Provides guidance and wisdom | Dumbledore |
| The Enemy | The antagonist or main obstacle | Voldemort |
| The Threshold Guardian | Challenges the hero at the start of their journey | Quirrell |
| The Shape-Shifter | Ambiguous character with unclear loyalties | Snape |
| The Trickster | Comic relief, offsets tension | Ron Weasley |
These archetypes help you think about different user roles in your product.
What personas are not
Personas are often confused with:
- Market segments (broad groups based on demographics).
- Stereotypes or cultural clichés.
- Average users (the mythical “average Joe”).
- Roles in meetings or teams (e.g., leader, facilitator).
Personas are research-based, nuanced representations of user groups with shared goals and behaviors.
Example personas for a B2B SaaS product
| Persona | Description |
|---|---|
| Owner Ollie | Small business owner, wears many hats, wants easy tools to grow sales and simplify operations. |
| Marketing Mary | Marketing director focused on brand presence and reports for the CEO, prefers stable, easy-to-use software. |
| Enterprise Erin | VP Marketing at a large company, manages strategic initiatives, values integrations and customization. |
Each persona guides product decisions differently.
What details to capture in personas
When you build personas, capture:
| Category | Examples |
|---|---|
| Demographic | Age, gender, education, location |
| Behavior | Hobbies, media preferences, interests |
| Goals | What they want to achieve with your product |
| Sacrifices | What they are willing to give up or tolerate |
This helps you understand motivations and constraints.
How to get started with user development
- Talk to users every day. Make it a habit, not a one-off.
- Focus on learning who to build for, not just what to build.
- Use a mix of qualitative and quantitative methods.
- Be prepared to challenge your assumptions and biases.
- Keep your research lean and focused to fit real constraints.
Field exercise: Build your first personas (10 min)
- Pick a product you use regularly (Swiggy, Razorpay, Meesho, or your own company’s product).
- Write down 3 distinct types of users who use this product.
- For each user type, note their goals, pain points, and behaviors.
- Give each user type a name and a brief description.
- Use these personas to think about what features matter most to each.
Slack chat: Planning user interviews at a Bangalore fintech startup
From the field: User research tips from Pragmatic Leaders training
Test yourself: User development prioritization at a Series A SaaS startup in Pune
You are a PM at a Pune-based Series A SaaS startup. You have three competing demands: the CEO wants a feature demo for a big client next week, engineering requests user feedback before finalizing designs, and sales wants quick fixes for onboarding issues. You have two weeks and limited bandwidth.
The call: How do you prioritize your user development activities, and how do you communicate your plan to stakeholders?
Your reasoning:
You are a PM at a Pune-based Series A SaaS startup. You have three competing demands: the CEO wants a feature demo for a big client next week, engineering requests user feedback before finalizing designs, and sales wants quick fixes for onboarding issues. You have two weeks and limited bandwidth.
Your task: How do you prioritize your user development activities, and how do you communicate your plan to stakeholders?
your reasoning:
Where to go next
- If you want to learn detailed user research methods: User Research Methods
- If you want to translate user insights into product strategy: Product Vision and Strategy
- If you want to develop your skills in crafting user personas: User Personas and Segmentation
- If you want to practice stakeholder communication: Stakeholder Management for PMs