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-designer3description: UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user jo...4license: MIT5---6
7# UX Researcher & Designer
8
9Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
10
11---
12
13## Table of Contents
14
15- [Trigger Terms](#trigger-terms)
16- [Workflows](#workflows)
17 - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)
18 - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)
19 - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)
20 - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)
21- [Tool Reference](#tool-reference)
22- [Quick Reference Tables](#quick-reference-tables)
23- [Knowledge Base](#knowledge-base)
24
25---
26
27## Trigger Terms
28
29Use this skill when you need to:
30
31- "create user persona"
32- "generate persona from data"
33- "build customer journey map"
34- "map user journey"
35- "plan usability test"
36- "design usability study"
37- "analyze user research"
38- "synthesize interview findings"
39- "identify user pain points"
40- "define user archetypes"
41- "calculate research sample size"
42- "create empathy map"
43- "identify user needs"
44
45---
46
47## Workflows
48
49### Workflow 1: Generate User Persona
50
51**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
52
53**Steps:**
54
551. **Prepare user data**
56
57 Required format (JSON):
58 ```json
59 [
60 {
61 "user_id": "user_1",
62 "age": 32,
63 "usage_frequency": "daily",
64 "features_used": ["dashboard", "reports", "export"],
65 "primary_device": "desktop",
66 "usage_context": "work",
67 "tech_proficiency": 7,
68 "pain_points": ["slow loading", "confusing UI"]
69 }
70 ]
71 ```
72
732. **Run persona generator**
74 ```bash
75 # Human-readable output
76 python scripts/persona_generator.py
77
78 # JSON output for integration
79 python scripts/persona_generator.py json
80 ```
81
823. **Review generated components**
83
84 | Component | What to Check |
85 |-----------|---------------|
86 | Archetype | Does it match the data patterns? |
87 | Demographics | Are they derived from actual data? |
88 | Goals | Are they specific and actionable? |
89 | Frustrations | Do they include frequency counts? |
90 | Design implications | Can designers act on these? |
91
924. **Validate persona**
93
94 - Show to 3-5 real users: "Does this sound like you?"
95 - Cross-check with support tickets
96 - Verify against analytics data
97
985. **Reference:** See `references/persona-methodology.md` for validity criteria
99
100---
101
102### Workflow 2: Create Journey Map
103
104**Situation:** You need to visualize the end-to-end user experience for a specific goal.
105
106**Steps:**
107
1081. **Define scope**
109
110 | Element | Description |
111 |---------|-------------|
112 | Persona | Which user type |
113 | Goal | What they're trying to achieve |
114 | Start | Trigger that begins journey |
115 | End | Success criteria |
116 | Timeframe | Hours/days/weeks |
117
1182. **Gather journey data**
119
120 Sources:
121 - User interviews (ask "walk me through...")
122 - Session recordings
123 - Analytics (funnel, drop-offs)
124 - Support tickets
125
1263. **Map the stages**
127
128 Typical B2B SaaS stages:
129 ```
130 Awareness → Evaluation → Onboarding → Adoption → Advocacy
131 ```
132
1334. **Fill in layers for each stage**
134
135 ```
136 Stage: [Name]
137 ├── Actions: What does user do?
138 ├── Touchpoints: Where do they interact?
139 ├── Emotions: How do they feel? (1-5)
140 ├── Pain Points: What frustrates them?
141 └── Opportunities: Where can we improve?
142 ```
143
1445. **Identify opportunities**
145
146 Priority Score = Frequency × Severity × Solvability
147
1486. **Reference:** See `references/journey-mapping-guide.md` for templates
149
150---
151
152### Workflow 3: Plan Usability Test
153
154**Situation:** You need to validate a design with real users.
155
156**Steps:**
157
1581. **Define research questions**
159
160 Transform vague goals into testable questions:
161
162 | Vague | Testable |
163 |-------|----------|
164 | "Is it easy to use?" | "Can users complete checkout in <3 min?" |
165 | "Do users like it?" | "Will users choose Design A or B?" |
166 | "Does it make sense?" | "Can users find settings without hints?" |
167
1682. **Select method**
169
170 | Method | Participants | Duration | Best For |
171 |--------|--------------|----------|----------|
172 | Moderated remote | 5-8 | 45-60 min | Deep insights |
173 | Unmoderated remote | 10-20 | 15-20 min | Quick validation |
174 | Guerrilla | 3-5 | 5-10 min | Rapid feedback |
175
1763. **Design tasks**
177
178 Good task format:
179 ```
180 SCENARIO: "Imagine you're planning a trip to Paris..."
181 GOAL: "Book a hotel for 3 nights in your budget."
182 SUCCESS: "You see the confirmation page."
183 ```
184
185 Task progression: Warm-up → Core → Secondary → Edge case → Free exploration
186
1874. **Define success metrics**
188
189 | Metric | Target |
190 |--------|--------|
191 | Completion rate | >80% |
192 | Time on task | <2× expected |
193 | Error rate | <15% |
194 | Satisfaction | >4/5 |
195
1965. **Prepare moderator guide**
197
198 - Think-aloud instructions
199 - Non-leading prompts
200 - Post-task questions
201
2026. **Reference:** See `references/usability-testing-frameworks.md` for full guide
203
204---
205
206### Workflow 4: Synthesize Research
207
208**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.
209
210**Steps:**
211
2121. **Code the data**
213
214 Tag each data point:
215 - `[GOAL]` - What they want to achieve
216 - `[PAIN]` - What frustrates them
217 - `[BEHAVIOR]` - What they actually do
218 - `[CONTEXT]` - When/where they use product
219 - `[QUOTE]` - Direct user words
220
2212. **Cluster similar patterns**
222
223 ```
224 User A: Uses daily, advanced features, shortcuts
225 User B: Uses daily, complex workflows, automation
226 User C: Uses weekly, basic needs, occasional
227
228 Cluster 1: A, B (Power Users)
229 Cluster 2: C (Casual User)
230 ```
231
2323. **Calculate segment sizes**
233
234 | Cluster | Users | % | Viability |
235 |---------|-------|---|-----------|
236 | Power Users | 18 | 36% | Primary persona |
237 | Business Users | 15 | 30% | Primary persona |
238 | Casual Users | 12 | 24% | Secondary persona |
239
2404. **Extract key findings**
241
242 For each theme:
243 - Finding statement
244 - Supporting evidence (quotes, data)
245 - Frequency (X/Y participants)
246 - Business impact
247 - Recommendation
248
2495. **Prioritize opportunities**
250
251 | Factor | Score 1-5 |
252 |--------|-----------|
253 | Frequency | How often does this occur? |
254 | Severity | How much does it hurt? |
255 | Breadth | How many users affected? |
256 | Solvability | Can we fix this? |
257
2586. **Reference:** See `references/persona-methodology.md` for analysis framework
259
260---
261
262## Tool Reference
263
264### persona_generator.py
265
266Generates data-driven personas from user research data.
267
268| Argument | Values | Default | Description |
269|----------|--------|---------|-------------|
270| format | (none), json | (none) | Output format |
271
272**Sample Output:**
273
274```
275============================================================
276PERSONA: Alex the Power User
277============================================================
278
279📝 A daily user who primarily uses the product for work purposes
280
281Archetype: Power User
282Quote: "I need tools that can keep up with my workflow"
283
284👤 Demographics:
285 • Age Range: 25-34
286 • Location Type: Urban
287 • Tech Proficiency: Advanced
288
289🎯 Goals & Needs:
290 • Complete tasks efficiently
291 • Automate workflows
292 • Access advanced features
293
294😤 Frustrations:
295 • Slow loading times (14/20 users)
296 • No keyboard shortcuts
297 • Limited API access
298
299💡 Design Implications:
300 → Optimize for speed and efficiency
301 → Provide keyboard shortcuts and power features
302 → Expose API and automation capabilities
303
304📈 Data: Based on 45 users
305 Confidence: High
306```
307
308**Archetypes Generated:**
309
310| Archetype | Signals | Design Focus |
311|-----------|---------|--------------|
312| power_user | Daily use, 10+ features | Efficiency, customization |
313| casual_user | Weekly use, 3-5 features | Simplicity, guidance |
314| business_user | Work context, team use | Collaboration, reporting |
315| mobile_first | Mobile primary | Touch, offline, speed |
316
317**Output Components:**
318
319| Component | Description |
320|-----------|-------------|
321| demographics | Age range, location, occupation, tech level |
322| psychographics | Motivations, values, attitudes, lifestyle |
323| behaviors | Usage patterns, feature preferences |
324| needs_and_goals | Primary, secondary, functional, emotional |
325| frustrations | Pain points with evidence |
326| scenarios | Contextual usage stories |
327| design_implications | Actionable recommendations |
328| data_points | Sample size, confidence level |
329
330---
331
332## Quick Reference Tables
333
334### Research Method Selection
335
336| Question Type | Best Method | Sample Size |
337|---------------|-------------|-------------|
338| "What do users do?" | Analytics, observation | 100+ events |
339| "Why do they do it?" | Interviews | 8-15 users |
340| "How well can they do it?" | Usability test | 5-8 users |
341| "What do they prefer?" | Survey, A/B test | 50+ users |
342| "What do they feel?" | Diary study, interviews | 10-15 users |
343
344### Persona Confidence Levels
345
346| Sample Size | Confidence | Use Case |
347|-------------|------------|----------|
348| 5-10 users | Low | Exploratory |
349| 11-30 users | Medium | Directional |
350| 31+ users | High | Production |
351
352### Usability Issue Severity
353
354| Severity | Definition | Action |
355|----------|------------|--------|
356| 4 - Critical | Prevents task completion | Fix immediately |
357| 3 - Major | Significant difficulty | Fix before release |
358| 2 - Minor | Causes hesitation | Fix when possible |
359| 1 - Cosmetic | Noticed but not problematic | Low priority |
360
361### Interview Question Types
362
363| Type | Example | Use For |
364|------|---------|---------|
365| Context | "Walk me through your typical day" | Understanding environment |
366| Behavior | "Show me how you do X" | Observing actual actions |
367| Goals | "What are you trying to achieve?" | Uncovering motivations |
368| Pain | "What's the hardest part?" | Identifying frustrations |
369| Reflection | "What would you change?" | Generating ideas |
370
371---
372
373## Knowledge Base
374
375Detailed reference guides in `references/`:
376
377| File | Content |
378|------|---------|
379| `persona-methodology.md` | Validity criteria, data collection, analysis framework |
380| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |
381| `example-personas.md` | 3 complete persona examples with data |
382| `usability-testing-frameworks.md` | Test planning, task design, analysis |
383
384---
385
386## Validation Checklist
387
388### Persona Quality
389- [ ] Based on 20+ users (minimum)
390- [ ] At least 2 data sources (quant + qual)
391- [ ] Specific, actionable goals
392- [ ] Frustrations include frequency counts
393- [ ] Design implications are specific
394- [ ] Confidence level stated
395
396### Journey Map Quality
397- [ ] Scope clearly defined (persona, goal, timeframe)
398- [ ] Based on real user data, not assumptions
399- [ ] All layers filled (actions, touchpoints, emotions)
400- [ ] Pain points identified per stage
401- [ ] Opportunities prioritized
402
403### Usability Test Quality
404- [ ] Research questions are testable
405- [ ] Tasks are realistic scenarios, not instructions
406- [ ] 5+ participants per design
407- [ ] Success metrics defined
408- [ ] Findings include severity ratings
409
410### Research Synthesis Quality
411- [ ] Data coded consistently
412- [ ] Patterns based on 3+ data points
413- [ ] Findings include evidence
414- [ ] Recommendations are actionable
415- [ ] Priorities justified
416
417## Related Skills
418
419- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions
420- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research