UX Researcher & Designer
Generate user personas from research data, create journey maps, plan usability
tests, and synthesize research findings into actionable design recommendations.
When to apply
Use this skill when the operator wants to:
- Create a research-backed user persona.
- Build a customer or product journey map.
- Plan or analyze a usability test.
- Synthesize interviews, surveys, or observational research.
- Define user archetypes, empathy maps, or pain points.
- Calculate sample sizes or pick the right research method.
Trigger phrases include: "create user persona", "generate persona from data",
"build customer journey map", "plan usability test", "synthesize interview
findings", "calculate research sample size", "create empathy map".
Do not use this skill for: pure visual design, marketing personas based on
purchase intent only, or product analytics without a research component.
Required input contract
Before producing any artifact, identify:
- Decision the artifact supports — what gets decided with this output.
- Audience — designer, PM, executive, customer-facing team.
- Source data available — interviews, surveys, analytics, support tickets,
session recordings. Note volume and recency.
- Sample size and recency — drives confidence level and method choice.
- Privacy posture — consent recorded, retention window, redaction status.
If the operator requests a persona or journey map without ≥ 2 data sources,
ask one sharp question to surface what data exists before drafting.
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 |
Extended table (longitudinal, segmented): references/research-workflow.md.
Core workflows
1. Generate User Persona
- Prepare user data (JSON: demographics, usage, features, pain points).
- Run
python scripts/persona_generator.py (or json for machine output).
- Review archetype, demographics, goals, frustrations with frequency counts, design implications.
- Validate with 3-5 real users + cross-check support tickets + analytics.
2. Create Journey Map
- Define scope: persona, goal, start, end, timeframe.
- Gather data from interviews, recordings, analytics, support.
- Map stages (e.g., Awareness → Evaluation → Onboarding → Adoption → Advocacy).
- Fill layers per stage: Actions, Touchpoints, Emotions (1-5), Pain, Opportunities.
- Score opportunities:
Frequency × Severity × Solvability.
3. Plan Usability Test
- Convert vague goals into testable questions.
- Pick method (moderated 5-8 / unmoderated 10-20 / guerrilla 3-5).
- Design tasks as scenario + goal + success criterion (not instructions).
- Define success metrics (completion > 80%, time < 2×, error < 15%, satisfaction > 4/5).
- Prepare moderator guide with think-aloud + non-leading prompts.
4. Synthesize Research
- Code data:
[GOAL], [PAIN], [BEHAVIOR], [CONTEXT], [QUOTE].
- Cluster patterns (≥ 3 participants = pattern; below that = hypothesis).
- Calculate segment sizes and viability.
- Extract findings: statement + evidence + frequency + business impact + recommendation.
- Prioritize opportunities by Frequency × Severity × Solvability (or FBS-S 4-axis).
Full step-by-step procedures: references/research-workflow.md.
Templates (interview guide, survey, moderator script, empathy map, journey layers):
references/methods-and-templates.md.
Coding, finding statements, reporting templates: references/synthesis-and-artifacts.md.
Safety, privacy, and consent
- Treat all research data as PII by default.
- Obtain explicit recorded consent before any session; state purpose, recording, retention, anonymization, right to withdraw.
- Mask sensitive on-screen data before recording.
- Use participant IDs (P01, P02) in artifacts, not names.
- Apply retention window from consent (default 90 days raw / 12 months redacted).
- Never paste raw participant data into shared chat tools or third-party LLMs without an explicit data-handling check.
- Never re-identify pseudonymized participants, attribute quotes by name when consent was anonymous, or publish demographics that single out an individual in a small segment.
- Escalate findings that touch accessibility/age-gating compliance, retention or collection changes, or contradict recently shipped major decisions.
Full privacy detail: references/privacy-validation-and-troubleshooting.md.
Validation gates
Every artifact must pass its gate before being delivered.
| Artifact |
Gate |
| Persona |
20+ users, ≥ 2 data sources, goals + frustrations (with frequency) + design implications + confidence stated |
| Journey map |
Scope defined; based on real data; all 5 layers filled; opportunities prioritized |
| Usability test |
Testable questions; tasks are scenarios not instructions; 5+ participants/design; success metrics defined; severity ratings on findings |
| Synthesis |
Consistent coding; patterns ≥ 3 data points; findings carry evidence + frequency + business impact; recommendations actionable + prioritized |
Full checklists: references/privacy-validation-and-troubleshooting.md.
Confidence and severity scales
| Sample Size |
Confidence |
Use Case |
| 5-10 users |
Low |
Exploratory |
| 11-30 users |
Medium |
Directional |
| 31+ users |
High |
Production |
| 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 |
Output expectations
| Request |
You produce |
| "Create a persona" |
Persona one-pager with goals, frustrations (with frequency), design implications, sample size, confidence |
| "Map the journey" |
Journey one-pager with stages × layers + top 3 prioritized opportunities |
| "Plan a usability test" |
Test plan: questions, method, tasks, success metrics, moderator guide |
| "Synthesize this research" |
Readout: question, method/sample, top 3 findings with evidence, recommendations table, confidence + limitations |
Worked examples for each: references/examples.md.
Tool reference
scripts/persona_generator.py
| Argument |
Values |
Default |
Description |
| format |
(none), json |
(none) |
Output format |
Archetypes: power_user, casual_user, business_user, mobile_first. Persona
components, archetype signals, and sample output: references/methods-and-templates.md, references/examples.md.
Reference map
| Need |
Read |
| Full step-by-step for all 4 workflows + extended method selection |
references/research-workflow.md |
| Interview / survey / moderator templates, archetypes, persona components, empathy map, journey layers |
references/methods-and-templates.md |
| Coding scheme, clustering, finding statement, prioritization, reporting templates |
references/synthesis-and-artifacts.md |
| Consent and privacy rules, validation checklists, anti-patterns, troubleshooting, escalation |
references/privacy-validation-and-troubleshooting.md |
| Worked outputs: persona, journey, usability findings, readout |
references/examples.md |
Related skills
product-team/ui-design-system/ — research findings inform design system decisions.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# UX Researcher & Designer78Generate user personas from research data, create journey maps, plan usability9tests, and synthesize research findings into actionable design recommendations.1011## When to apply1213Use this skill when the operator wants to:1415- Create a research-backed user persona.16- Build a customer or product journey map.17- Plan or analyze a usability test.18- Synthesize interviews, surveys, or observational research.19- Define user archetypes, empathy maps, or pain points.20- Calculate sample sizes or pick the right research method.2122Trigger phrases include: "create user persona", "generate persona from data",23"build customer journey map", "plan usability test", "synthesize interview24findings", "calculate research sample size", "create empathy map".2526Do not use this skill for: pure visual design, marketing personas based on27purchase intent only, or product analytics without a research component.2829## Required input contract3031Before producing any artifact, identify:3233- **Decision the artifact supports** — what gets decided with this output.34- **Audience** — designer, PM, executive, customer-facing team.35- **Source data available** — interviews, surveys, analytics, support tickets,36 session recordings. Note volume and recency.37- **Sample size and recency** — drives confidence level and method choice.38- **Privacy posture** — consent recorded, retention window, redaction status.3940If the operator requests a persona or journey map without ≥ 2 data sources,41ask one sharp question to surface what data exists before drafting.4243## Method selection4445| Question Type | Best Method | Sample Size |46|---------------|-------------|-------------|47| "What do users do?" | Analytics, observation | 100+ events |48| "Why do they do it?" | Interviews | 8-15 users |49| "How well can they do it?" | Usability test | 5-8 users |50| "What do they prefer?" | Survey, A/B test | 50+ users |51| "What do they feel?" | Diary study, interviews | 10-15 users |5253Extended table (longitudinal, segmented): `references/research-workflow.md`.5455## Core workflows5657### 1. Generate User Persona58591. Prepare user data (JSON: demographics, usage, features, pain points).602. Run `python scripts/persona_generator.py` (or `json` for machine output).613. Review archetype, demographics, goals, frustrations with frequency counts, design implications.624. Validate with 3-5 real users + cross-check support tickets + analytics.6364### 2. Create Journey Map65661. Define scope: persona, goal, start, end, timeframe.672. Gather data from interviews, recordings, analytics, support.683. Map stages (e.g., Awareness → Evaluation → Onboarding → Adoption → Advocacy).694. Fill layers per stage: Actions, Touchpoints, Emotions (1-5), Pain, Opportunities.705. Score opportunities: `Frequency × Severity × Solvability`.7172### 3. Plan Usability Test73741. Convert vague goals into testable questions.752. Pick method (moderated 5-8 / unmoderated 10-20 / guerrilla 3-5).763. Design tasks as scenario + goal + success criterion (not instructions).774. Define success metrics (completion > 80%, time < 2×, error < 15%, satisfaction > 4/5).785. Prepare moderator guide with think-aloud + non-leading prompts.7980### 4. Synthesize Research81821. Code data: `[GOAL]`, `[PAIN]`, `[BEHAVIOR]`, `[CONTEXT]`, `[QUOTE]`.832. Cluster patterns (≥ 3 participants = pattern; below that = hypothesis).843. Calculate segment sizes and viability.854. Extract findings: statement + evidence + frequency + business impact + recommendation.865. Prioritize opportunities by Frequency × Severity × Solvability (or FBS-S 4-axis).8788Full step-by-step procedures: `references/research-workflow.md`.89Templates (interview guide, survey, moderator script, empathy map, journey layers):90`references/methods-and-templates.md`.91Coding, finding statements, reporting templates: `references/synthesis-and-artifacts.md`.9293## Safety, privacy, and consent9495- Treat all research data as PII by default.96- Obtain explicit recorded consent before any session; state purpose, recording, retention, anonymization, right to withdraw.97- Mask sensitive on-screen data before recording.98- Use participant IDs (P01, P02) in artifacts, not names.99- Apply retention window from consent (default 90 days raw / 12 months redacted).100- Never paste raw participant data into shared chat tools or third-party LLMs without an explicit data-handling check.101- Never re-identify pseudonymized participants, attribute quotes by name when consent was anonymous, or publish demographics that single out an individual in a small segment.102- Escalate findings that touch accessibility/age-gating compliance, retention or collection changes, or contradict recently shipped major decisions.103104Full privacy detail: `references/privacy-validation-and-troubleshooting.md`.105106## Validation gates107108Every artifact must pass its gate before being delivered.109110| Artifact | Gate |111|----------|------|112| Persona | 20+ users, ≥ 2 data sources, goals + frustrations (with frequency) + design implications + confidence stated |113| Journey map | Scope defined; based on real data; all 5 layers filled; opportunities prioritized |114| Usability test | Testable questions; tasks are scenarios not instructions; 5+ participants/design; success metrics defined; severity ratings on findings |115| Synthesis | Consistent coding; patterns ≥ 3 data points; findings carry evidence + frequency + business impact; recommendations actionable + prioritized |116117Full checklists: `references/privacy-validation-and-troubleshooting.md`.118119## Confidence and severity scales120121| Sample Size | Confidence | Use Case |122|-------------|------------|----------|123| 5-10 users | Low | Exploratory |124| 11-30 users | Medium | Directional |125| 31+ users | High | Production |126127| Severity | Definition | Action |128|----------|------------|--------|129| 4 - Critical | Prevents task completion | Fix immediately |130| 3 - Major | Significant difficulty | Fix before release |131| 2 - Minor | Causes hesitation | Fix when possible |132| 1 - Cosmetic | Noticed but not problematic | Low priority |133134## Output expectations135136| Request | You produce |137|---------|-------------|138| "Create a persona" | Persona one-pager with goals, frustrations (with frequency), design implications, sample size, confidence |139| "Map the journey" | Journey one-pager with stages × layers + top 3 prioritized opportunities |140| "Plan a usability test" | Test plan: questions, method, tasks, success metrics, moderator guide |141| "Synthesize this research" | Readout: question, method/sample, top 3 findings with evidence, recommendations table, confidence + limitations |142143Worked examples for each: `references/examples.md`.144145## Tool reference146147`scripts/persona_generator.py`148149| Argument | Values | Default | Description |150|----------|--------|---------|-------------|151| format | (none), json | (none) | Output format |152153Archetypes: power_user, casual_user, business_user, mobile_first. Persona154components, archetype signals, and sample output: `references/methods-and-templates.md`, `references/examples.md`.155156## Reference map157158| Need | Read |159|------|------|160| Full step-by-step for all 4 workflows + extended method selection | `references/research-workflow.md` |161| Interview / survey / moderator templates, archetypes, persona components, empathy map, journey layers | `references/methods-and-templates.md` |162| Coding scheme, clustering, finding statement, prioritization, reporting templates | `references/synthesis-and-artifacts.md` |163| Consent and privacy rules, validation checklists, anti-patterns, troubleshooting, escalation | `references/privacy-validation-and-troubleshooting.md` |164| Worked outputs: persona, journey, usability findings, readout | `references/examples.md` |165166## Related skills167168- `product-team/ui-design-system/` — research findings inform design system decisions.169- `product-team/product-manager-toolkit/` — customer interview analysis complements persona research.
kmshihab7878