Pesquisador e Designer de UX
Resumo em PT-BR: Combina pesquisa com proposta de experiencia e solucao de interface.
Titulo original: UX Researcher & Designer
Observacao: instrucoes detalhadas, referencias e scripts originais abaixo foram preservados em ingles.
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 (
produto/sistema-de-design-de-ui/) — Research findings inform design system decisions
- Product Manager Toolkit (
produto/kit-do-gerente-de-produto/) — Customer interview analysis complements persona research
1---2name: pesquisador-e-designer-de-ux3description: Combina pesquisa com proposta de experiencia e solucao de interface.4---56# Pesquisador e Designer de UX78Resumo em PT-BR: Combina pesquisa com proposta de experiencia e solucao de interface.9Titulo original: `UX Researcher & Designer`10Observacao: instrucoes detalhadas, referencias e scripts originais abaixo foram preservados em ingles.111213Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.1415---1617## Table of Contents1819- [Trigger Terms](#trigger-terms)20- [Workflows](#workflows)21 - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)22 - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)23 - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)24 - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)25- [Tool Reference](#tool-reference)26- [Quick Reference Tables](#quick-reference-tables)27- [Knowledge Base](#knowledge-base)2829---3031## Trigger Terms3233Use this skill when you need to:3435- "create user persona"36- "generate persona from data"37- "build customer journey map"38- "map user journey"39- "plan usability test"40- "design usability study"41- "analyze user research"42- "synthesize interview findings"43- "identify user pain points"44- "define user archetypes"45- "calculate research sample size"46- "create empathy map"47- "identify user needs"4849---5051## Workflows5253### Workflow 1: Generate User Persona5455**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.5657**Steps:**58591. **Prepare user data**6061 Required format (JSON):62 ```json63 [64 {65 "user_id": "user_1",66 "age": 32,67 "usage_frequency": "daily",68 "features_used": ["dashboard", "reports", "export"],69 "primary_device": "desktop",70 "usage_context": "work",71 "tech_proficiency": 7,72 "pain_points": ["slow loading", "confusing UI"]73 }74 ]75 ```76772. **Run persona generator**78 ```bash79 # Human-readable output80 python scripts/persona_generator.py8182 # JSON output for integration83 python scripts/persona_generator.py json84 ```85863. **Review generated components**8788 | Component | What to Check |89 |-----------|---------------|90 | Archetype | Does it match the data patterns? |91 | Demographics | Are they derived from actual data? |92 | Goals | Are they specific and actionable? |93 | Frustrations | Do they include frequency counts? |94 | Design implications | Can designers act on these? |95964. **Validate persona**9798 - Show to 3-5 real users: "Does this sound like you?"99 - Cross-check with support tickets100 - Verify against analytics data1011025. **Reference:** See `references/persona-methodology.md` for validity criteria103104---105106### Workflow 2: Create Journey Map107108**Situation:** You need to visualize the end-to-end user experience for a specific goal.109110**Steps:**1111121. **Define scope**113114 | Element | Description |115 |---------|-------------|116 | Persona | Which user type |117 | Goal | What they're trying to achieve |118 | Start | Trigger that begins journey |119 | End | Success criteria |120 | Timeframe | Hours/days/weeks |1211222. **Gather journey data**123124 Sources:125 - User interviews (ask "walk me through...")126 - Session recordings127 - Analytics (funnel, drop-offs)128 - Support tickets1291303. **Map the stages**131132 Typical B2B SaaS stages:133 ```134 Awareness → Evaluation → Onboarding → Adoption → Advocacy135 ```1361374. **Fill in layers for each stage**138139 ```140 Stage: [Name]141 ├── Actions: What does user do?142 ├── Touchpoints: Where do they interact?143 ├── Emotions: How do they feel? (1-5)144 ├── Pain Points: What frustrates them?145 └── Opportunities: Where can we improve?146 ```1471485. **Identify opportunities**149150 Priority Score = Frequency × Severity × Solvability1511526. **Reference:** See `references/journey-mapping-guide.md` for templates153154---155156### Workflow 3: Plan Usability Test157158**Situation:** You need to validate a design with real users.159160**Steps:**1611621. **Define research questions**163164 Transform vague goals into testable questions:165166 | Vague | Testable |167 |-------|----------|168 | "Is it easy to use?" | "Can users complete checkout in <3 min?" |169 | "Do users like it?" | "Will users choose Design A or B?" |170 | "Does it make sense?" | "Can users find settings without hints?" |1711722. **Select method**173174 | Method | Participants | Duration | Best For |175 |--------|--------------|----------|----------|176 | Moderated remote | 5-8 | 45-60 min | Deep insights |177 | Unmoderated remote | 10-20 | 15-20 min | Quick validation |178 | Guerrilla | 3-5 | 5-10 min | Rapid feedback |1791803. **Design tasks**181182 Good task format:183 ```184 SCENARIO: "Imagine you're planning a trip to Paris..."185 GOAL: "Book a hotel for 3 nights in your budget."186 SUCCESS: "You see the confirmation page."187 ```188189 Task progression: Warm-up → Core → Secondary → Edge case → Free exploration1901914. **Define success metrics**192193 | Metric | Target |194 |--------|--------|195 | Completion rate | >80% |196 | Time on task | <2× expected |197 | Error rate | <15% |198 | Satisfaction | >4/5 |1992005. **Prepare moderator guide**201202 - Think-aloud instructions203 - Non-leading prompts204 - Post-task questions2052066. **Reference:** See `references/usability-testing-frameworks.md` for full guide207208---209210### Workflow 4: Synthesize Research211212**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.213214**Steps:**2152161. **Code the data**217218 Tag each data point:219 - `[GOAL]` - What they want to achieve220 - `[PAIN]` - What frustrates them221 - `[BEHAVIOR]` - What they actually do222 - `[CONTEXT]` - When/where they use product223 - `[QUOTE]` - Direct user words2242252. **Cluster similar patterns**226227 ```228 User A: Uses daily, advanced features, shortcuts229 User B: Uses daily, complex workflows, automation230 User C: Uses weekly, basic needs, occasional231232 Cluster 1: A, B (Power Users)233 Cluster 2: C (Casual User)234 ```2352363. **Calculate segment sizes**237238 | Cluster | Users | % | Viability |239 |---------|-------|---|-----------|240 | Power Users | 18 | 36% | Primary persona |241 | Business Users | 15 | 30% | Primary persona |242 | Casual Users | 12 | 24% | Secondary persona |2432444. **Extract key findings**245246 For each theme:247 - Finding statement248 - Supporting evidence (quotes, data)249 - Frequency (X/Y participants)250 - Business impact251 - Recommendation2522535. **Prioritize opportunities**254255 | Factor | Score 1-5 |256 |--------|-----------|257 | Frequency | How often does this occur? |258 | Severity | How much does it hurt? |259 | Breadth | How many users affected? |260 | Solvability | Can we fix this? |2612626. **Reference:** See `references/persona-methodology.md` for analysis framework263264---265266## Tool Reference267268### persona_generator.py269270Generates data-driven personas from user research data.271272| Argument | Values | Default | Description |273|----------|--------|---------|-------------|274| format | (none), json | (none) | Output format |275276**Sample Output:**277278```279============================================================280PERSONA: Alex the Power User281============================================================282283📝 A daily user who primarily uses the product for work purposes284285Archetype: Power User286Quote: "I need tools that can keep up with my workflow"287288👤 Demographics:289 • Age Range: 25-34290 • Location Type: Urban291 • Tech Proficiency: Advanced292293🎯 Goals & Needs:294 • Complete tasks efficiently295 • Automate workflows296 • Access advanced features297298😤 Frustrations:299 • Slow loading times (14/20 users)300 • No keyboard shortcuts301 • Limited API access302303💡 Design Implications:304 → Optimize for speed and efficiency305 → Provide keyboard shortcuts and power features306 → Expose API and automation capabilities307308📈 Data: Based on 45 users309 Confidence: High310```311312**Archetypes Generated:**313314| Archetype | Signals | Design Focus |315|-----------|---------|--------------|316| power_user | Daily use, 10+ features | Efficiency, customization |317| casual_user | Weekly use, 3-5 features | Simplicity, guidance |318| business_user | Work context, team use | Collaboration, reporting |319| mobile_first | Mobile primary | Touch, offline, speed |320321**Output Components:**322323| Component | Description |324|-----------|-------------|325| demographics | Age range, location, occupation, tech level |326| psychographics | Motivations, values, attitudes, lifestyle |327| behaviors | Usage patterns, feature preferences |328| needs_and_goals | Primary, secondary, functional, emotional |329| frustrations | Pain points with evidence |330| scenarios | Contextual usage stories |331| design_implications | Actionable recommendations |332| data_points | Sample size, confidence level |333334---335336## Quick Reference Tables337338### Research Method Selection339340| Question Type | Best Method | Sample Size |341|---------------|-------------|-------------|342| "What do users do?" | Analytics, observation | 100+ events |343| "Why do they do it?" | Interviews | 8-15 users |344| "How well can they do it?" | Usability test | 5-8 users |345| "What do they prefer?" | Survey, A/B test | 50+ users |346| "What do they feel?" | Diary study, interviews | 10-15 users |347348### Persona Confidence Levels349350| Sample Size | Confidence | Use Case |351|-------------|------------|----------|352| 5-10 users | Low | Exploratory |353| 11-30 users | Medium | Directional |354| 31+ users | High | Production |355356### Usability Issue Severity357358| Severity | Definition | Action |359|----------|------------|--------|360| 4 - Critical | Prevents task completion | Fix immediately |361| 3 - Major | Significant difficulty | Fix before release |362| 2 - Minor | Causes hesitation | Fix when possible |363| 1 - Cosmetic | Noticed but not problematic | Low priority |364365### Interview Question Types366367| Type | Example | Use For |368|------|---------|---------|369| Context | "Walk me through your typical day" | Understanding environment |370| Behavior | "Show me how you do X" | Observing actual actions |371| Goals | "What are you trying to achieve?" | Uncovering motivations |372| Pain | "What's the hardest part?" | Identifying frustrations |373| Reflection | "What would you change?" | Generating ideas |374375---376377## Knowledge Base378379Detailed reference guides in `references/`:380381| File | Content |382|------|---------|383| `persona-methodology.md` | Validity criteria, data collection, analysis framework |384| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |385| `example-personas.md` | 3 complete persona examples with data |386| `usability-testing-frameworks.md` | Test planning, task design, analysis |387388---389390## Validation Checklist391392### Persona Quality393- [ ] Based on 20+ users (minimum)394- [ ] At least 2 data sources (quant + qual)395- [ ] Specific, actionable goals396- [ ] Frustrations include frequency counts397- [ ] Design implications are specific398- [ ] Confidence level stated399400### Journey Map Quality401- [ ] Scope clearly defined (persona, goal, timeframe)402- [ ] Based on real user data, not assumptions403- [ ] All layers filled (actions, touchpoints, emotions)404- [ ] Pain points identified per stage405- [ ] Opportunities prioritized406407### Usability Test Quality408- [ ] Research questions are testable409- [ ] Tasks are realistic scenarios, not instructions410- [ ] 5+ participants per design411- [ ] Success metrics defined412- [ ] Findings include severity ratings413414### Research Synthesis Quality415- [ ] Data coded consistently416- [ ] Patterns based on 3+ data points417- [ ] Findings include evidence418- [ ] Recommendations are actionable419- [ ] Priorities justified420421## Related Skills422423- **UI Design System** (`produto/sistema-de-design-de-ui/`) — Research findings inform design system decisions424- **Product Manager Toolkit** (`produto/kit-do-gerente-de-produto/`) — Customer interview analysis complements persona research