User Research
What Is User Research in Software Development?
User research studies how people use software, what they need, and where they struggle. It replaces assumptions with evidence before teams design, build, or change websites and apps. UX research examines product experience, market research studies audience demand, and product analytics measures behavior at scale.
The Four Types of User Research
These are two overlapping lenses, not four project stages.
| Type | Answers | Methods | Use it when |
|---|---|---|---|
| Qualitative | Why and how? | Interviews, usability tests | Exploring a confusing workflow |
| Quantitative | What and how many? | Surveys, analytics | Measuring a suspected issue |
| Attitudinal | What do users say? | Interviews, surveys | Learning expectations |
| Behavioral | What do users do? | Observation, event data | Validating real usage |
How User Research Works
Start with a product decision, not a vague request for feedback.
- Frame a specific decision.
- Identify relevant participants.
- Select a suitable method.
- Run sessions or collect data.
- Group evidence into patterns.
- Prioritize findings by impact and confidence.
- Turn findings into requirements or user stories.
- Validate the shipped change with users and product data.
Common User Research Methods and When to Use Them
| Method | Best use | Evidence and limit |
|---|---|---|
| Interviews | Discover goals | Detailed accounts, but self-report can mislead |
| Usability testing | Find task friction | Observed failures, but small samples |
| Surveys | Measure sentiment | Broad responses, but shallow context |
| Analytics review | Locate drop-off | Behavioral patterns, not reasons |
| Card sorting | Organize navigation | Label preferences, not final design proof |
| Diary studies | Study long-term use | Repeated context, but participant effort is high |
| A/B tests | Compare live variants | Outcome differences, not user motivation |
Benefits of User Research
Research gives product and engineering teams shared evidence.
- Reduces usability problems before wider release.
- Clarifies unmet needs and accessibility barriers.
- Improves prioritization when requests compete.
- Supports tradeoffs with observed evidence.
- Tests whether a solution solves the intended problem.
Practical Limits of User Research
Research informs judgment. It does not guarantee product success.
- Biased recruitment can distort findings.
- Leading questions can produce unreliable answers.
- Small studies should not be overgeneralized.
- Stated preferences may differ from real behavior.
- Teams must obtain consent and protect participant data.
- Research cannot replace security, performance, or technical testing.
From Research Finding to Software Requirement
If new users abandon account setup because they do not understand why a phone number is required, the finding can become a user story: “As a new user, I need a clear explanation before sharing my number.” Acceptance criteria may require a purpose statement, an optional skip path, and completion analytics. A follow-up usability test checks comprehension. A finding is evidence, not an automatic feature request.
User Research for Apps Built with Emergent
Research notes can become workflow requirements for a prototype or production app. With an AI app builder, builders can describe workflows and collect feedback with an AI survey and quiz builder. They can add login user accounts for tested flows and learn how to get their first users. Emergent helps turn validated needs into a testable full-stack app.
on Emergent today

