User research is the systematic study of your target users. It replaces guesswork with evidence, ensuring that design decisions are grounded in actual behavior rather than assumptions. There are two broad categories: qualitative research (understanding why) and quantitative research (measuring what and how much).
User Interviews
Interviews are the most powerful qualitative research method. A well-conducted 30-minute interview can reveal insights that months of analytics data cannot.
Tips for effective interviews:
- Recruit the right people — Talk to actual or potential users of your product, not colleagues or friends who will be too polite to give honest feedback.
- Prepare a guide, not a script — Write 5 to 8 open-ended questions but be ready to follow interesting threads. Good questions start with "Tell me about..." or "Walk me through..."
- Avoid leading questions — Instead of "Don't you find it frustrating when...?" ask "How do you feel about that experience?"
- Record with permission — You will miss important details if you rely on notes alone. Review recordings to catch nuances you missed live.
A sample interview question set for a recipe app:
- How do you currently decide what to cook for dinner?
- Walk me through the last time you tried a new recipe.
- What is the most frustrating part of following a recipe on your phone?
- How do you keep track of groceries you need to buy?
Surveys
Surveys let you gather data from a larger audience. They are great for validating patterns you discovered in interviews. Keep surveys short — aim for 5 to 10 questions and a completion time under 3 minutes.
Survey best practices:
- Mix question types — Combine multiple-choice, Likert scales (1-5 agreement), and one or two open-ended questions.
- Avoid double-barreled questions — "Is the app fast and easy to use?" is really two questions. Split them.
- Use tools like Typeform or Google Forms — They handle distribution, collection, and basic analysis for you.
- Target 30+ responses minimum — Below that, patterns are unreliable.
User Personas
A persona is a fictional character that represents a key user segment. Personas synthesize your research into a reference document the whole team can use.
A good persona includes:
- Name and photo — Makes the persona feel real. "Sarah, 34, marketing manager" is more memorable than "User Type A."
- Goals — What is this person trying to accomplish? ("Plan healthy meals for a family of four without spending hours in the kitchen.")
- Frustrations — What blocks them today? ("Recipes require ingredients I don't have, and substitution suggestions are unreliable.")
- Behaviors — How do they currently solve the problem? ("Rotates the same 10 meals, occasionally screenshots Instagram recipes.")
- Context — When and where do they use the product? ("Mostly on her phone, while commuting or during lunch breaks.")
Limit yourself to 3 to 5 personas. More than that and the team will not remember any of them.
Empathy Maps
An empathy map is a quick collaborative tool that organizes what you know about a user into four quadrants:
| Says | Thinks |
|---|---|
| Direct quotes from interviews. "I never know what to cook." | Unspoken thoughts inferred from behavior. "Am I a bad parent for always ordering takeout?" |
| Does | Feels |
| Observable actions. Scrolls through recipes for 10 minutes, then gives up and orders pizza. | Emotional states. Overwhelmed by choice, guilty about food waste. |
Empathy maps work best as a team exercise after interviews. They align everyone on who the user is before jumping into solutions.
Choosing the Right Method
| Method | Best for | Time required |
|---|---|---|
| Interviews | Deep understanding of motivations | 1-2 weeks |
| Surveys | Validating patterns at scale | 3-5 days |
| Personas | Aligning the team on user segments | 1-2 days |
| Empathy maps | Quick synthesis after interviews | 1-2 hours |
Start with interviews to discover insights, validate with surveys, then synthesize into personas and empathy maps that guide your design decisions.