Internal Safety Override
- Status: local-only unless explicitly opted into external access.
- Before using network tools, account connectors, browser automation, or APIs, state the destination, data scope, and credential source.
- Do not transmit repository files, secrets, credentials, or private documents by default.
- Audit categories: network.
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 for user research, persona creation, journey mapping, and design validation.4---56## Internal Safety Override78- Status: local-only unless explicitly opted into external access.9- Before using network tools, account connectors, browser automation, or APIs, state the destination, data scope, and credential source.10- Do not transmit repository files, secrets, credentials, or private documents by default.11- Audit categories: network.1213# UX Researcher & Designer1415Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.1617---1819## Table of Contents2021- [Trigger Terms](#trigger-terms)22- [Workflows](#workflows)23 - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)24 - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)25 - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)26 - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)27- [Tool Reference](#tool-reference)28- [Quick Reference Tables](#quick-reference-tables)29- [Knowledge Base](#knowledge-base)3031---3233## Trigger Terms3435Use this skill when you need to:3637- "create user persona"38- "generate persona from data"39- "build customer journey map"40- "map user journey"41- "plan usability test"42- "design usability study"43- "analyze user research"44- "synthesize interview findings"45- "identify user pain points"46- "define user archetypes"47- "calculate research sample size"48- "create empathy map"49- "identify user needs"5051---5253## Workflows5455### Workflow 1: Generate User Persona5657**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.5859**Steps:**60611. **Prepare user data**6263 Required format (JSON):64 ```json65 [66 {67 "user_id": "user_1",68 "age": 32,69 "usage_frequency": "daily",70 "features_used": ["dashboard", "reports", "export"],71 "primary_device": "desktop",72 "usage_context": "work",73 "tech_proficiency": 7,74 "pain_points": ["slow loading", "confusing UI"]75 }76 ]77 ```78792. **Run persona generator**80 ```bash81 # Human-readable output82 python scripts/persona_generator.py8384 # JSON output for integration85 python scripts/persona_generator.py json86 ```87883. **Review generated components**8990 | Component | What to Check |91 |-----------|---------------|92 | Archetype | Does it match the data patterns? |93 | Demographics | Are they derived from actual data? |94 | Goals | Are they specific and actionable? |95 | Frustrations | Do they include frequency counts? |96 | Design implications | Can designers act on these? |97984. **Validate persona**99100 - Show to 3-5 real users: "Does this sound like you?"101 - Cross-check with support tickets102 - Verify against analytics data1031045. **Reference:** See `references/persona-methodology.md` for validity criteria105106---107108### Workflow 2: Create Journey Map109110**Situation:** You need to visualize the end-to-end user experience for a specific goal.111112**Steps:**1131141. **Define scope**115116 | Element | Description |117 |---------|-------------|118 | Persona | Which user type |119 | Goal | What they're trying to achieve |120 | Start | Trigger that begins journey |121 | End | Success criteria |122 | Timeframe | Hours/days/weeks |1231242. **Gather journey data**125126 Sources:127 - User interviews (ask "walk me through...")128 - Session recordings129 - Analytics (funnel, drop-offs)130 - Support tickets1311323. **Map the stages**133134 Typical B2B SaaS stages:135 ```136 Awareness → Evaluation → Onboarding → Adoption → Advocacy137 ```1381394. **Fill in layers for each stage**140141 ```142 Stage: [Name]143 ├── Actions: What does user do?144 ├── Touchpoints: Where do they interact?145 ├── Emotions: How do they feel? (1-5)146 ├── Pain Points: What frustrates them?147 └── Opportunities: Where can we improve?148 ```1491505. **Identify opportunities**151152 Priority Score = Frequency × Severity × Solvability1531546. **Reference:** See `references/journey-mapping-guide.md` for templates155156---157158### Workflow 3: Plan Usability Test159160**Situation:** You need to validate a design with real users.161162**Steps:**1631641. **Define research questions**165166 Transform vague goals into testable questions:167168 | Vague | Testable |169 |-------|----------|170 | "Is it easy to use?" | "Can users complete checkout in <3 min?" |171 | "Do users like it?" | "Will users choose Design A or B?" |172 | "Does it make sense?" | "Can users find settings without hints?" |1731742. **Select method**175176 | Method | Participants | Duration | Best For |177 |--------|--------------|----------|----------|178 | Moderated remote | 5-8 | 45-60 min | Deep insights |179 | Unmoderated remote | 10-20 | 15-20 min | Quick validation |180 | Guerrilla | 3-5 | 5-10 min | Rapid feedback |1811823. **Design tasks**183184 Good task format:185 ```186 SCENARIO: "Imagine you're planning a trip to Paris..."187 GOAL: "Book a hotel for 3 nights in your budget."188 SUCCESS: "You see the confirmation page."189 ```190191 Task progression: Warm-up → Core → Secondary → Edge case → Free exploration1921934. **Define success metrics**194195 | Metric | Target |196 |--------|--------|197 | Completion rate | >80% |198 | Time on task | <2× expected |199 | Error rate | <15% |200 | Satisfaction | >4/5 |2012025. **Prepare moderator guide**203204 - Think-aloud instructions205 - Non-leading prompts206 - Post-task questions2072086. **Reference:** See `references/usability-testing-frameworks.md` for full guide209210---211212### Workflow 4: Synthesize Research213214**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.215216**Steps:**2172181. **Code the data**219220 Tag each data point:221 - `[GOAL]` - What they want to achieve222 - `[PAIN]` - What frustrates them223 - `[BEHAVIOR]` - What they actually do224 - `[CONTEXT]` - When/where they use product225 - `[QUOTE]` - Direct user words2262272. **Cluster similar patterns**228229 ```230 User A: Uses daily, advanced features, shortcuts231 User B: Uses daily, complex workflows, automation232 User C: Uses weekly, basic needs, occasional233234 Cluster 1: A, B (Power Users)235 Cluster 2: C (Casual User)236 ```2372383. **Calculate segment sizes**239240 | Cluster | Users | % | Viability |241 |---------|-------|---|-----------|242 | Power Users | 18 | 36% | Primary persona |243 | Business Users | 15 | 30% | Primary persona |244 | Casual Users | 12 | 24% | Secondary persona |2452464. **Extract key findings**247248 For each theme:249 - Finding statement250 - Supporting evidence (quotes, data)251 - Frequency (X/Y participants)252 - Business impact253 - Recommendation2542555. **Prioritize opportunities**256257 | Factor | Score 1-5 |258 |--------|-----------|259 | Frequency | How often does this occur? |260 | Severity | How much does it hurt? |261 | Breadth | How many users affected? |262 | Solvability | Can we fix this? |2632646. **Reference:** See `references/persona-methodology.md` for analysis framework265266---267268## Tool Reference269270### persona_generator.py271272Generates data-driven personas from user research data.273274| Argument | Values | Default | Description |275|----------|--------|---------|-------------|276| format | (none), json | (none) | Output format |277278**Sample Output:**279280```281============================================================282PERSONA: Alex the Power User283============================================================284285📝 A daily user who primarily uses the product for work purposes286287Archetype: Power User288Quote: "I need tools that can keep up with my workflow"289290👤 Demographics:291 • Age Range: 25-34292 • Location Type: Urban293 • Tech Proficiency: Advanced294295🎯 Goals & Needs:296 • Complete tasks efficiently297 • Automate workflows298 • Access advanced features299300😤 Frustrations:301 • Slow loading times (14/20 users)302 • No keyboard shortcuts303 • Limited API access304305💡 Design Implications:306 → Optimize for speed and efficiency307 → Provide keyboard shortcuts and power features308 → Expose API and automation capabilities309310📈 Data: Based on 45 users311 Confidence: High312```313314**Archetypes Generated:**315316| Archetype | Signals | Design Focus |317|-----------|---------|--------------|318| power_user | Daily use, 10+ features | Efficiency, customization |319| casual_user | Weekly use, 3-5 features | Simplicity, guidance |320| business_user | Work context, team use | Collaboration, reporting |321| mobile_first | Mobile primary | Touch, offline, speed |322323**Output Components:**324325| Component | Description |326|-----------|-------------|327| demographics | Age range, location, occupation, tech level |328| psychographics | Motivations, values, attitudes, lifestyle |329| behaviors | Usage patterns, feature preferences |330| needs_and_goals | Primary, secondary, functional, emotional |331| frustrations | Pain points with evidence |332| scenarios | Contextual usage stories |333| design_implications | Actionable recommendations |334| data_points | Sample size, confidence level |335336---337338## Quick Reference Tables339340### Research Method Selection341342| Question Type | Best Method | Sample Size |343|---------------|-------------|-------------|344| "What do users do?" | Analytics, observation | 100+ events |345| "Why do they do it?" | Interviews | 8-15 users |346| "How well can they do it?" | Usability test | 5-8 users |347| "What do they prefer?" | Survey, A/B test | 50+ users |348| "What do they feel?" | Diary study, interviews | 10-15 users |349350### Persona Confidence Levels351352| Sample Size | Confidence | Use Case |353|-------------|------------|----------|354| 5-10 users | Low | Exploratory |355| 11-30 users | Medium | Directional |356| 31+ users | High | Production |357358### Usability Issue Severity359360| Severity | Definition | Action |361|----------|------------|--------|362| 4 - Critical | Prevents task completion | Fix immediately |363| 3 - Major | Significant difficulty | Fix before release |364| 2 - Minor | Causes hesitation | Fix when possible |365| 1 - Cosmetic | Noticed but not problematic | Low priority |366367### Interview Question Types368369| Type | Example | Use For |370|------|---------|---------|371| Context | "Walk me through your typical day" | Understanding environment |372| Behavior | "Show me how you do X" | Observing actual actions |373| Goals | "What are you trying to achieve?" | Uncovering motivations |374| Pain | "What's the hardest part?" | Identifying frustrations |375| Reflection | "What would you change?" | Generating ideas |376377---378379## Knowledge Base380381Detailed reference guides in `references/`:382383| File | Content |384|------|---------|385| `persona-methodology.md` | Validity criteria, data collection, analysis framework |386| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |387| `example-personas.md` | 3 complete persona examples with data |388| `usability-testing-frameworks.md` | Test planning, task design, analysis |389390---391392## Validation Checklist393394### Persona Quality395- [ ] Based on 20+ users (minimum)396- [ ] At least 2 data sources (quant + qual)397- [ ] Specific, actionable goals398- [ ] Frustrations include frequency counts399- [ ] Design implications are specific400- [ ] Confidence level stated401402### Journey Map Quality403- [ ] Scope clearly defined (persona, goal, timeframe)404- [ ] Based on real user data, not assumptions405- [ ] All layers filled (actions, touchpoints, emotions)406- [ ] Pain points identified per stage407- [ ] Opportunities prioritized408409### Usability Test Quality410- [ ] Research questions are testable411- [ ] Tasks are realistic scenarios, not instructions412- [ ] 5+ participants per design413- [ ] Success metrics defined414- [ ] Findings include severity ratings415416### Research Synthesis Quality417- [ ] Data coded consistently418- [ ] Patterns based on 3+ data points419- [ ] Findings include evidence420- [ ] Recommendations are actionable421- [ ] Priorities justified422423## Related Skills424425- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions426- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research