UX Researcher
1. Persona Generation
Data Requirements
[{
"user_id": "user_1",
"age": 32,
"usage_frequency": "daily",
"features_used": ["dashboard", "reports"],
"primary_device": "desktop",
"tech_proficiency": 7,
"pain_points": ["slow loading", "confusing UI"]
}]
Archetypes
| Archetype |
Signals |
Design Focus |
| Power User |
Daily use, 10+ features |
Efficiency, shortcuts, customization |
| Casual User |
Weekly use, 3–5 features |
Simplicity, guidance, progressive disclosure |
| Business User |
Work context, team use |
Collaboration, reporting, admin |
| Mobile-First |
Mobile primary device |
Touch-friendly, offline, speed |
Validation
- Show persona to 3–5 real users: "Does this sound like you?"
- Cross-check with support tickets
- Verify against analytics data
2. Journey Mapping
Scope Definition
| Element |
Define |
| Persona |
Which user type |
| Goal |
What they're trying to achieve |
| Start |
Trigger that begins journey |
| End |
Success criteria |
| Timeframe |
Hours / days / weeks |
Typical B2B SaaS Stages
Awareness → Evaluation → Onboarding → Adoption → Advocacy
Each Stage Contains
Stage: [Name]
├── Actions: What does user do?
├── Touchpoints: Where do they interact?
├── Emotions: How do they feel? (1–5)
├── Pain Points: What frustrates them?
└── Opportunities: Where can we improve?
Opportunity Priority Score
Score = Frequency × Severity × Solvability
3. Usability Testing
Research Question Design
| Vague |
Testable |
| "Is it easy to use?" |
"Can users complete checkout in <3 min?" |
| "Do users like it?" |
"Will users choose Design A or B?" |
| "Does it make sense?" |
"Can users find settings without hints?" |
Method Selection
| Method |
Participants |
Duration |
Best For |
| Moderated remote |
5–8 |
45–60 min |
Deep insights |
| Unmoderated remote |
10–20 |
15–20 min |
Quick validation |
| Guerrilla |
3–5 |
5–10 min |
Rapid feedback |
Success Metrics
| Metric |
Target |
| Completion rate |
>80% |
| Time on task |
<2× expected |
| Error rate |
<15% |
| Satisfaction |
>4/5 |
Task Design
SCENARIO: "Imagine you're planning a trip to Paris..."
GOAL: "Book a hotel for 3 nights in your budget."
SUCCESS: "You see the confirmation page."
Progression: Warm-up → Core → Secondary → Edge case → Free exploration
4. Research Synthesis
Coding Data
Tag each data point:
[GOAL] — What they want to achieve
[PAIN] — What frustrates them
[BEHAVIOR] — What they actually do
[CONTEXT] — When/where they use product
[QUOTE] — Direct user words
Clustering
Group users by behavioral patterns → identify segments → size each segment:
| Cluster |
Users |
% |
Persona Priority |
| Power Users |
18 |
36% |
Primary |
| Business Users |
15 |
30% |
Primary |
| Casual Users |
12 |
24% |
Secondary |
Extracting Findings
For each theme:
- Finding statement
- Supporting evidence (quotes, data)
- Frequency (X/Y participants)
- Business impact
- Recommendation
Prioritization
| Factor |
Score 1–5 |
| Frequency |
How often does this occur? |
| Severity |
How much does it hurt? |
| Breadth |
How many users affected? |
| Solvability |
Can we fix this? |
Quick Reference: Research Methods
| Question Type |
Method |
Sample Size |
| "What do users do?" |
Analytics, observation |
100+ events |
| "Why do they do it?" |
Interviews |
8–15 users |
| "How well can they?" |
Usability test |
5–8 users |
| "What do they prefer?" |
Survey, A/B test |
50+ users |
| "What do they feel?" |
Diary study |
10–15 users |
Usability Issue Severity
| Level |
Definition |
Action |
| 4 — Critical |
Prevents task completion |
Fix immediately |
| 3 — Major |
Significant difficulty |
Fix before release |
| 2 — Minor |
Causes hesitation |
Fix when possible |
| 1 — Cosmetic |
Noticed, not problematic |
Low priority |
1---2name: ux-researcher3description: UX research toolkit: data-driven persona generation, customer journey mapping, usability testing frameworks, research synthesis. Use when planning user research, creating personas, mapping journeys, or validating designs.4---56# UX Researcher78---910## 1. Persona Generation1112### Data Requirements1314```json15[{16 "user_id": "user_1",17 "age": 32,18 "usage_frequency": "daily",19 "features_used": ["dashboard", "reports"],20 "primary_device": "desktop",21 "tech_proficiency": 7,22 "pain_points": ["slow loading", "confusing UI"]23}]24```2526### Archetypes2728| Archetype | Signals | Design Focus |29|-----------|---------|--------------|30| Power User | Daily use, 10+ features | Efficiency, shortcuts, customization |31| Casual User | Weekly use, 3–5 features | Simplicity, guidance, progressive disclosure |32| Business User | Work context, team use | Collaboration, reporting, admin |33| Mobile-First | Mobile primary device | Touch-friendly, offline, speed |3435### Validation36- Show persona to 3–5 real users: "Does this sound like you?"37- Cross-check with support tickets38- Verify against analytics data3940---4142## 2. Journey Mapping4344### Scope Definition4546| Element | Define |47|---------|--------|48| Persona | Which user type |49| Goal | What they're trying to achieve |50| Start | Trigger that begins journey |51| End | Success criteria |52| Timeframe | Hours / days / weeks |5354### Typical B2B SaaS Stages5556```57Awareness → Evaluation → Onboarding → Adoption → Advocacy58```5960### Each Stage Contains6162```63Stage: [Name]64├── Actions: What does user do?65├── Touchpoints: Where do they interact?66├── Emotions: How do they feel? (1–5)67├── Pain Points: What frustrates them?68└── Opportunities: Where can we improve?69```7071### Opportunity Priority Score7273**Score = Frequency × Severity × Solvability**7475---7677## 3. Usability Testing7879### Research Question Design8081| Vague | Testable |82|-------|----------|83| "Is it easy to use?" | "Can users complete checkout in <3 min?" |84| "Do users like it?" | "Will users choose Design A or B?" |85| "Does it make sense?" | "Can users find settings without hints?" |8687### Method Selection8889| Method | Participants | Duration | Best For |90|--------|--------------|----------|----------|91| Moderated remote | 5–8 | 45–60 min | Deep insights |92| Unmoderated remote | 10–20 | 15–20 min | Quick validation |93| Guerrilla | 3–5 | 5–10 min | Rapid feedback |9495### Success Metrics9697| Metric | Target |98|--------|--------|99| Completion rate | >80% |100| Time on task | <2× expected |101| Error rate | <15% |102| Satisfaction | >4/5 |103104### Task Design105106```107SCENARIO: "Imagine you're planning a trip to Paris..."108GOAL: "Book a hotel for 3 nights in your budget."109SUCCESS: "You see the confirmation page."110```111112Progression: Warm-up → Core → Secondary → Edge case → Free exploration113114---115116## 4. Research Synthesis117118### Coding Data119120Tag each data point:121- `[GOAL]` — What they want to achieve122- `[PAIN]` — What frustrates them123- `[BEHAVIOR]` — What they actually do124- `[CONTEXT]` — When/where they use product125- `[QUOTE]` — Direct user words126127### Clustering128129Group users by behavioral patterns → identify segments → size each segment:130131| Cluster | Users | % | Persona Priority |132|---------|-------|---|-----------------|133| Power Users | 18 | 36% | Primary |134| Business Users | 15 | 30% | Primary |135| Casual Users | 12 | 24% | Secondary |136137### Extracting Findings138139For each theme:1401. Finding statement1412. Supporting evidence (quotes, data)1423. Frequency (X/Y participants)1434. Business impact1445. Recommendation145146### Prioritization147148| Factor | Score 1–5 |149|--------|-----------|150| Frequency | How often does this occur? |151| Severity | How much does it hurt? |152| Breadth | How many users affected? |153| Solvability | Can we fix this? |154155---156157## Quick Reference: Research Methods158159| Question Type | Method | Sample Size |160|---------------|--------|-------------|161| "What do users do?" | Analytics, observation | 100+ events |162| "Why do they do it?" | Interviews | 8–15 users |163| "How well can they?" | Usability test | 5–8 users |164| "What do they prefer?" | Survey, A/B test | 50+ users |165| "What do they feel?" | Diary study | 10–15 users |166167---168169## Usability Issue Severity170171| Level | Definition | Action |172|-------|------------|--------|173| 4 — Critical | Prevents task completion | Fix immediately |174| 3 — Major | Significant difficulty | Fix before release |175| 2 — Minor | Causes hesitation | Fix when possible |176| 1 — Cosmetic | Noticed, not problematic | Low priority |