UX Researcher & Designer
Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
Table of Contents
Trigger Terms
Use this skill when you need to:
- "create user persona"
- "generate persona from data"
- "build customer journey map"
- "map user journey"
- "plan usability test"
- "design usability study"
- "analyze user research"
- "synthesize interview findings"
- "identify user pain points"
- "define user archetypes"
- "calculate research sample size"
- "create empathy map"
- "identify user needs"
Workflows
Workflow 1: Generate User Persona
Situation: You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
Steps:
Prepare user data
Required format (JSON):
[
{
"user_id": "user_1",
"age": 32,
"usage_frequency": "daily",
"features_used": ["dashboard", "reports", "export"],
"primary_device": "desktop",
"usage_context": "work",
"tech_proficiency": 7,
"pain_points": ["slow loading", "confusing UI"]
}
]
Run persona generator
# Human-readable output
python scripts/persona_generator.py
# JSON output for integration
python scripts/persona_generator.py json
Review generated components
| Component |
What to Check |
| Archetype |
Does it match the data patterns? |
| Demographics |
Are they derived from actual data? |
| Goals |
Are they specific and actionable? |
| Frustrations |
Do they include frequency counts? |
| Design implications |
Can designers act on these? |
Validate persona
- Show to 3-5 real users: "Does this sound like you?"
- Cross-check with support tickets
- Verify against analytics data
Reference: See references/persona-methodology.md for validity criteria
Workflow 2: Create Journey Map
Situation: You need to visualize the end-to-end user experience for a specific goal.
Steps:
Define scope
| Element |
Description |
| Persona |
Which user type |
| Goal |
What they're trying to achieve |
| Start |
Trigger that begins journey |
| End |
Success criteria |
| Timeframe |
Hours/days/weeks |
Gather journey data
Sources:
- User interviews (ask "walk me through...")
- Session recordings
- Analytics (funnel, drop-offs)
- Support tickets
Map the stages
Typical B2B SaaS stages:
Awareness → Evaluation → Onboarding → Adoption → Advocacy
Fill in layers for each stage
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?
Identify opportunities
Priority Score = Frequency × Severity × Solvability
Reference: See references/journey-mapping-guide.md for templates
Workflow 3: Plan Usability Test
Situation: You need to validate a design with real users.
Steps:
Define research questions
Transform vague goals into testable questions:
| 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?" |
Select method
| 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 |
Design tasks
Good task format:
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."
Task progression: Warm-up → Core → Secondary → Edge case → Free exploration
Define success metrics
| Metric |
Target |
| Completion rate |
>80% |
| Time on task |
<2× expected |
| Error rate |
<15% |
| Satisfaction |
>4/5 |
Prepare moderator guide
- Think-aloud instructions
- Non-leading prompts
- Post-task questions
Reference: See references/usability-testing-frameworks.md for full guide
Workflow 4: Synthesize Research
Situation: You have raw research data (interviews, surveys, observations) and need actionable insights.
Steps:
Code the 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
Cluster similar patterns
User A: Uses daily, advanced features, shortcuts
User B: Uses daily, complex workflows, automation
User C: Uses weekly, basic needs, occasional
Cluster 1: A, B (Power Users)
Cluster 2: C (Casual User)
Calculate segment sizes
| Cluster |
Users |
% |
Viability |
| Power Users |
18 |
36% |
Primary persona |
| Business Users |
15 |
30% |
Primary persona |
| Casual Users |
12 |
24% |
Secondary persona |
Extract key findings
For each theme:
- Finding statement
- Supporting evidence (quotes, data)
- Frequency (X/Y participants)
- Business impact
- Recommendation
Prioritize opportunities
| 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? |
Reference: See references/persona-methodology.md for analysis framework
Tool Reference
persona_generator.py
Generates data-driven personas from user research data.
| Argument |
Values |
Default |
Description |
| format |
(none), json |
(none) |
Output format |
Sample Output:
============================================================
PERSONA: Alex the Power User
============================================================
📝 A daily user who primarily uses the product for work purposes
Archetype: Power User
Quote: "I need tools that can keep up with my workflow"
👤 Demographics:
• Age Range: 25-34
• Location Type: Urban
• Tech Proficiency: Advanced
🎯 Goals & Needs:
• Complete tasks efficiently
• Automate workflows
• Access advanced features
😤 Frustrations:
• Slow loading times (14/20 users)
• No keyboard shortcuts
• Limited API access
💡 Design Implications:
→ Optimize for speed and efficiency
→ Provide keyboard shortcuts and power features
→ Expose API and automation capabilities
📈 Data: Based on 45 users
Confidence: High
Archetypes Generated:
| Archetype |
Signals |
Design Focus |
| power_user |
Daily use, 10+ features |
Efficiency, customization |
| casual_user |
Weekly use, 3-5 features |
Simplicity, guidance |
| business_user |
Work context, team use |
Collaboration, reporting |
| mobile_first |
Mobile primary |
Touch, offline, speed |
Output Components:
| Component |
Description |
| demographics |
Age range, location, occupation, tech level |
| psychographics |
Motivations, values, attitudes, lifestyle |
| behaviors |
Usage patterns, feature preferences |
| needs_and_goals |
Primary, secondary, functional, emotional |
| frustrations |
Pain points with evidence |
| scenarios |
Contextual usage stories |
| design_implications |
Actionable recommendations |
| data_points |
Sample size, confidence level |
Quick Reference Tables
Research Method Selection
| Question Type |
Best Method |
Sample Size |
| "What do users do?" |
Analytics, observation |
100+ events |
| "Why do they do it?" |
Interviews |
8-15 users |
| "How well can they do it?" |
Usability test |
5-8 users |
| "What do they prefer?" |
Survey, A/B test |
50+ users |
| "What do they feel?" |
Diary study, interviews |
10-15 users |
Persona Confidence Levels
| Sample Size |
Confidence |
Use Case |
| 5-10 users |
Low |
Exploratory |
| 11-30 users |
Medium |
Directional |
| 31+ users |
High |
Production |
Usability Issue Severity
| Severity |
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 but not problematic |
Low priority |
Interview Question Types
| Type |
Example |
Use For |
| Context |
"Walk me through your typical day" |
Understanding environment |
| Behavior |
"Show me how you do X" |
Observing actual actions |
| Goals |
"What are you trying to achieve?" |
Uncovering motivations |
| Pain |
"What's the hardest part?" |
Identifying frustrations |
| Reflection |
"What would you change?" |
Generating ideas |
Knowledge Base
Detailed reference guides in references/:
| File |
Content |
persona-methodology.md |
Validity criteria, data collection, analysis framework |
journey-mapping-guide.md |
Mapping process, templates, opportunity identification |
example-personas.md |
3 complete persona examples with data |
usability-testing-frameworks.md |
Test planning, task design, analysis |
Validation Checklist
Persona Quality
Journey Map Quality
Usability Test Quality
Research Synthesis Quality
Related Skills
- UI Design System (
product-team/ui-design-system/) — Research findings inform design system decisions
- Product Manager Toolkit (
product-team/product-manager-toolkit/) — Customer interview analysis complements persona research
1---2name: "ux-researcher-designer"3description: "UX research: personas, journey maps, usability test plans, synthesis. Use whenever the user asks who their users are or why they struggle."4metadata:5 source: https://skillmd.com/skills/alirezarezvani/ux-researcher-designer6---78# UX Researcher & Designer910Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.1112---1314## Table of Contents1516- [Trigger Terms](#trigger-terms)17- [Workflows](#workflows)18 - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)19 - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)20 - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)21 - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)22- [Tool Reference](#tool-reference)23- [Quick Reference Tables](#quick-reference-tables)24- [Knowledge Base](#knowledge-base)2526---2728## Trigger Terms2930Use this skill when you need to:3132- "create user persona"33- "generate persona from data"34- "build customer journey map"35- "map user journey"36- "plan usability test"37- "design usability study"38- "analyze user research"39- "synthesize interview findings"40- "identify user pain points"41- "define user archetypes"42- "calculate research sample size"43- "create empathy map"44- "identify user needs"4546---4748## Workflows4950### Workflow 1: Generate User Persona5152**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.5354**Steps:**55561. **Prepare user data**5758 Required format (JSON):59 ```json60 [61 {62 "user_id": "user_1",63 "age": 32,64 "usage_frequency": "daily",65 "features_used": ["dashboard", "reports", "export"],66 "primary_device": "desktop",67 "usage_context": "work",68 "tech_proficiency": 7,69 "pain_points": ["slow loading", "confusing UI"]70 }71 ]72 ```73742. **Run persona generator**75 ```bash76 # Human-readable output77 python scripts/persona_generator.py7879 # JSON output for integration80 python scripts/persona_generator.py json81 ```82833. **Review generated components**8485 | Component | What to Check |86 |-----------|---------------|87 | Archetype | Does it match the data patterns? |88 | Demographics | Are they derived from actual data? |89 | Goals | Are they specific and actionable? |90 | Frustrations | Do they include frequency counts? |91 | Design implications | Can designers act on these? |92934. **Validate persona**9495 - Show to 3-5 real users: "Does this sound like you?"96 - Cross-check with support tickets97 - Verify against analytics data98995. **Reference:** See `references/persona-methodology.md` for validity criteria100101---102103### Workflow 2: Create Journey Map104105**Situation:** You need to visualize the end-to-end user experience for a specific goal.106107**Steps:**1081091. **Define scope**110111 | Element | Description |112 |---------|-------------|113 | Persona | Which user type |114 | Goal | What they're trying to achieve |115 | Start | Trigger that begins journey |116 | End | Success criteria |117 | Timeframe | Hours/days/weeks |1181192. **Gather journey data**120121 Sources:122 - User interviews (ask "walk me through...")123 - Session recordings124 - Analytics (funnel, drop-offs)125 - Support tickets1261273. **Map the stages**128129 Typical B2B SaaS stages:130 ```131 Awareness → Evaluation → Onboarding → Adoption → Advocacy132 ```1331344. **Fill in layers for each stage**135136 ```137 Stage: [Name]138 ├── Actions: What does user do?139 ├── Touchpoints: Where do they interact?140 ├── Emotions: How do they feel? (1-5)141 ├── Pain Points: What frustrates them?142 └── Opportunities: Where can we improve?143 ```1441455. **Identify opportunities**146147 Priority Score = Frequency × Severity × Solvability1481496. **Reference:** See `references/journey-mapping-guide.md` for templates150151---152153### Workflow 3: Plan Usability Test154155**Situation:** You need to validate a design with real users.156157**Steps:**1581591. **Define research questions**160161 Transform vague goals into testable questions:162163 | Vague | Testable |164 |-------|----------|165 | "Is it easy to use?" | "Can users complete checkout in <3 min?" |166 | "Do users like it?" | "Will users choose Design A or B?" |167 | "Does it make sense?" | "Can users find settings without hints?" |1681692. **Select method**170171 | Method | Participants | Duration | Best For |172 |--------|--------------|----------|----------|173 | Moderated remote | 5-8 | 45-60 min | Deep insights |174 | Unmoderated remote | 10-20 | 15-20 min | Quick validation |175 | Guerrilla | 3-5 | 5-10 min | Rapid feedback |1761773. **Design tasks**178179 Good task format:180 ```181 SCENARIO: "Imagine you're planning a trip to Paris..."182 GOAL: "Book a hotel for 3 nights in your budget."183 SUCCESS: "You see the confirmation page."184 ```185186 Task progression: Warm-up → Core → Secondary → Edge case → Free exploration1871884. **Define success metrics**189190 | Metric | Target |191 |--------|--------|192 | Completion rate | >80% |193 | Time on task | <2× expected |194 | Error rate | <15% |195 | Satisfaction | >4/5 |1961975. **Prepare moderator guide**198199 - Think-aloud instructions200 - Non-leading prompts201 - Post-task questions2022036. **Reference:** See `references/usability-testing-frameworks.md` for full guide204205---206207### Workflow 4: Synthesize Research208209**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.210211**Steps:**2122131. **Code the data**214215 Tag each data point:216 - `[GOAL]` - What they want to achieve217 - `[PAIN]` - What frustrates them218 - `[BEHAVIOR]` - What they actually do219 - `[CONTEXT]` - When/where they use product220 - `[QUOTE]` - Direct user words2212222. **Cluster similar patterns**223224 ```225 User A: Uses daily, advanced features, shortcuts226 User B: Uses daily, complex workflows, automation227 User C: Uses weekly, basic needs, occasional228229 Cluster 1: A, B (Power Users)230 Cluster 2: C (Casual User)231 ```2322333. **Calculate segment sizes**234235 | Cluster | Users | % | Viability |236 |---------|-------|---|-----------|237 | Power Users | 18 | 36% | Primary persona |238 | Business Users | 15 | 30% | Primary persona |239 | Casual Users | 12 | 24% | Secondary persona |2402414. **Extract key findings**242243 For each theme:244 - Finding statement245 - Supporting evidence (quotes, data)246 - Frequency (X/Y participants)247 - Business impact248 - Recommendation2492505. **Prioritize opportunities**251252 | Factor | Score 1-5 |253 |--------|-----------|254 | Frequency | How often does this occur? |255 | Severity | How much does it hurt? |256 | Breadth | How many users affected? |257 | Solvability | Can we fix this? |2582596. **Reference:** See `references/persona-methodology.md` for analysis framework260261---262263## Tool Reference264265### persona_generator.py266267Generates data-driven personas from user research data.268269| Argument | Values | Default | Description |270|----------|--------|---------|-------------|271| format | (none), json | (none) | Output format |272273**Sample Output:**274275```276============================================================277PERSONA: Alex the Power User278============================================================279280📝 A daily user who primarily uses the product for work purposes281282Archetype: Power User283Quote: "I need tools that can keep up with my workflow"284285👤 Demographics:286 • Age Range: 25-34287 • Location Type: Urban288 • Tech Proficiency: Advanced289290🎯 Goals & Needs:291 • Complete tasks efficiently292 • Automate workflows293 • Access advanced features294295😤 Frustrations:296 • Slow loading times (14/20 users)297 • No keyboard shortcuts298 • Limited API access299300💡 Design Implications:301 → Optimize for speed and efficiency302 → Provide keyboard shortcuts and power features303 → Expose API and automation capabilities304305📈 Data: Based on 45 users306 Confidence: High307```308309**Archetypes Generated:**310311| Archetype | Signals | Design Focus |312|-----------|---------|--------------|313| power_user | Daily use, 10+ features | Efficiency, customization |314| casual_user | Weekly use, 3-5 features | Simplicity, guidance |315| business_user | Work context, team use | Collaboration, reporting |316| mobile_first | Mobile primary | Touch, offline, speed |317318**Output Components:**319320| Component | Description |321|-----------|-------------|322| demographics | Age range, location, occupation, tech level |323| psychographics | Motivations, values, attitudes, lifestyle |324| behaviors | Usage patterns, feature preferences |325| needs_and_goals | Primary, secondary, functional, emotional |326| frustrations | Pain points with evidence |327| scenarios | Contextual usage stories |328| design_implications | Actionable recommendations |329| data_points | Sample size, confidence level |330331---332333## Quick Reference Tables334335### Research Method Selection336337| Question Type | Best Method | Sample Size |338|---------------|-------------|-------------|339| "What do users do?" | Analytics, observation | 100+ events |340| "Why do they do it?" | Interviews | 8-15 users |341| "How well can they do it?" | Usability test | 5-8 users |342| "What do they prefer?" | Survey, A/B test | 50+ users |343| "What do they feel?" | Diary study, interviews | 10-15 users |344345### Persona Confidence Levels346347| Sample Size | Confidence | Use Case |348|-------------|------------|----------|349| 5-10 users | Low | Exploratory |350| 11-30 users | Medium | Directional |351| 31+ users | High | Production |352353### Usability Issue Severity354355| Severity | Definition | Action |356|----------|------------|--------|357| 4 - Critical | Prevents task completion | Fix immediately |358| 3 - Major | Significant difficulty | Fix before release |359| 2 - Minor | Causes hesitation | Fix when possible |360| 1 - Cosmetic | Noticed but not problematic | Low priority |361362### Interview Question Types363364| Type | Example | Use For |365|------|---------|---------|366| Context | "Walk me through your typical day" | Understanding environment |367| Behavior | "Show me how you do X" | Observing actual actions |368| Goals | "What are you trying to achieve?" | Uncovering motivations |369| Pain | "What's the hardest part?" | Identifying frustrations |370| Reflection | "What would you change?" | Generating ideas |371372---373374## Knowledge Base375376Detailed reference guides in `references/`:377378| File | Content |379|------|---------|380| `persona-methodology.md` | Validity criteria, data collection, analysis framework |381| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |382| `example-personas.md` | 3 complete persona examples with data |383| `usability-testing-frameworks.md` | Test planning, task design, analysis |384385---386387## Validation Checklist388389### Persona Quality390- [ ] Based on 20+ users (minimum)391- [ ] At least 2 data sources (quant + qual)392- [ ] Specific, actionable goals393- [ ] Frustrations include frequency counts394- [ ] Design implications are specific395- [ ] Confidence level stated396397### Journey Map Quality398- [ ] Scope clearly defined (persona, goal, timeframe)399- [ ] Based on real user data, not assumptions400- [ ] All layers filled (actions, touchpoints, emotions)401- [ ] Pain points identified per stage402- [ ] Opportunities prioritized403404### Usability Test Quality405- [ ] Research questions are testable406- [ ] Tasks are realistic scenarios, not instructions407- [ ] 5+ participants per design408- [ ] Success metrics defined409- [ ] Findings include severity ratings410411### Research Synthesis Quality412- [ ] Data coded consistently413- [ ] Patterns based on 3+ data points414- [ ] Findings include evidence415- [ ] Recommendations are actionable416- [ ] Priorities justified417418## Related Skills419420- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions421- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research