What Is User Research?
User research is the systematic process of understanding users - who they are, what they need, how they behave, and why. It's the foundation for data-driven product and design decisions, not assumptions.
Why It's Essential
1. Reduces Risk
- Validate ideas before building
- Avoid investing in features nobody wants
- Identify problems early and cheap
- Team understands real users
- Decisions based on real needs
- Aligns stakeholders
- Features that solve real problems
- UX optimized for users
- Higher adoption and satisfaction
- Superior market understanding
- Faster product-market fit
- Customer-centric culture
- Understand the problem space
- Identify opportunities
- Validate assumptions
- Test concepts
- Evaluate alternatives
- Optimize flows
- Usability testing
- Beta feedback
- Feature prioritization
- Satisfaction monitoring
- Feature usage analytics
- Continuous improvement
- Early discovery
- Problem exploration
- Deep understanding
2. Creates Empathy
3. Improves Product
4. Competitive Advantage
When to Do Research
Discovery Phase:
Design Phase:
Development Phase:
Post-Launch:
Qualitative Methods
1. Interviews
What They Are:
One-on-one conversations with users to understand experiences, needs, and motivations.
When:
How:
Preparation:
1. Define objectives
2. Identify participants (5-10)
3. Create interview guide
4. Prepare logistics (recording, notes)
Interview Guide (example):
Intro (5 min):
Thank you for participating
Explain purpose and duration
Request recording permission Background (10 min):
Tell me about your role
What does a typical day look like? Main Topic (30 min):
When did you last use [product/feature]?
Walk me through what you did
What was difficult/easy?
What would you want to be different? Wrap-up (5 min):
Anything else you want to add?
Thank you, next steps
Tips:
2. Contextual Inquiry
What It Is:
Observation and interview in natural usage context.
When:
How:
3. Focus Groups
What They Are:
Moderated discussions with 5-8 participants.
When:
Caution:
4. Diary Studies
What They Are:
Participants document experiences over a period.
When:
Setup:
5. Usability Testing
What It Is:
Observing users completing specific tasks.
Variants:
Moderated:
Unmoderated:
A/B Testing:
Protocol:
Intro:
Context and purpose
We're not testing you, we're testing the product
Think aloud Tasks (3-5):
Specific and actionable
"Find a product X and order it"
No hints on how Observation:
Where do they get stuck?
What's confusing?
Workarounds? Debrief:
Overall impression
What was difficult
What would you change
Quantitative Methods
1. Surveys
When:
Design:
Question types:
Closed-ended for quantification
Likert scales (1-5)
Multiple choice
Open-ended for depth Best Practices:
Max 10 minute completion
Clear, simple language
Logical flow
Mobile-friendly
Test before launch
Common Metrics:
NPS (Net Promoter Score):
"How likely are you to recommend...? (0-10)"
CSAT (Customer Satisfaction):
"How satisfied are you? (1-5)"
SUS (System Usability Scale):
10 standardized questions about usability.
2. Analytics
Behavioral Data:
Tools:
Key Metrics:
3. A/B Testing
When:
Process:
1. Formulate hypothesis
"Changing CTA color to green will
increase clicks by 10%"
2. Design variants
- Control (current)
- Treatment (change)
3. Run test
- Split traffic
- Sufficient sample size
- Statistical significance
4. Analyze results
- Winner or no difference
- Unexpected patterns
- Segment analysis
Research Operations
Recruitment
Methods:
Screener:
1. Demographics basics
2. Qualifying criteria
3. Disqualifying criteria
4. Availability
Incentive Guidelines:
Documentation
Note-Taking:
Research Repository:
Deliverables:
Synthesis
Affinity Mapping:
1. Write insights on sticky notes
2. Group by themes
3. Name clusters
4. Prioritize by frequency/impact
Framework Example:
Theme: Onboarding Confusion
Finding 1: 7/10 didn't understand step 3
Finding 2: "I wasn't sure what to do next"
Impact: High abandonment
Recommendation: Simplify, add progress indicator
Communicating Results
For Stakeholders
Executive Summary:
Full Report:
Storytelling
Structure:
1. Context: Why we did research
2. What we did: Methodology
3. What we learned: Key findings
4. What it means: Implications
5. What we should do: Recommendations
Tips:
Artifacts
Personas:
Journey Maps:
Empathy Maps:
Integration into Process
Discovery
Research:
Output:
Design
Research:
Output:
Development
Research:
Output:
Post-Launch
Research:
Output:
Common Errors
1. Confirmation Bias
Problem: Looking for what we want to find.
Solution:
2. Leading Questions
Problem: "Don't you think X is better?"
Solution:
3. Not Enough Participants
Problem: 2 interviews and conclusions.
Solution:
4. Research Theatre
Problem: Research just for show.
Solution:
5. Analysis Paralysis
Problem: Research never ends.
Solution:
Conclusion
User research isn't a luxury, it's a necessity. Investment in understanding users returns multiplied in better product, reduced rework, and competitive advantage.
Key principles:
Implementation steps:
1. Start with clear objectives
2. Choose appropriate methods
3. Recruit right participants
4. Execute and document
5. Synthesize and share
6. Act on findings
---
The DGI team offers user research and UX strategy services. Contact us to better understand your users.