ux-researcher-designer

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](#trigger-terms)
• [Workflows](#workflows)
• [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)
• [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)
• [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)
• [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)
• [Tool Reference](#tool-reference)
• [Quick Reference Tables](#quick-reference-tables)
• [Knowledge Base](#knowledge-base)

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:

1. Prepare user data

Required format (JSON): ``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"] } ] ``

1. Run persona generator

```bash # Human-readable output python scripts/persona_generator.py

# JSON output for integration python scripts/persona_generator.py json ```

1. 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? |

1. Validate persona

• Show to 3-5 real users: "Does this sound like you?"
• Cross-check with support tickets
• Verify against analytics data

1. Reference: See references/persona-methodology.md for validity criteria

Proto-Persona Canvas (Lightweight Alternative)

When you lack research data but need a hypothesis-driven persona to align the team, use a proto-persona canvas. Proto-personas are assumption tools -- not validated truth -- meant to be tested and refined.

Use when: Starting a new initiative with no research budget, aligning a cross-functional team quickly, or creating a testable hypothesis about your user.

Proto-Persona Canvas Template:

### [Alliterative Name] (e.g., "Careful Carlos")

**Bio & Demographics:**
- Age, geography, social status, career stage
- Online presence, leisure activities, partner status

**Quotes** (what they say, feel, think):
- "[Direct quote capturing their perspective]"
- "[Quote revealing frustration or aspiration]"

**Pains:**
- [Pain related to the problem space]
- [Pain related to current workarounds]

**What They're Trying to Accomplish:**
- [Observable behavior 1]
- [Observable behavior 2]

**Goals** (wants, needs, dreams):
- [Short-term goal]
- [Long-term aspiration]

**Attitudes & Influences:**
- Decision Making Authority: [Can they buy/adopt your solution?]
- Decision Influencers: [Who influences their decisions?]
- Beliefs & Attitudes: [What beliefs impact their choices?]

**Assumptions to Validate:**
- [Top assumption that must be true for this persona to be viable]
- [Second assumption]
- [Third assumption]

Next steps after proto-persona:

1. Generate interview questions to validate assumptions (Recommended)
2. Generate an anti-persona to define scope boundaries
3. Convert into a one-page stakeholder brief

Workflow 2: Create Journey Map

Situation: You need to visualize the end-to-end user experience for a specific goal.

Steps:

1. 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 |

1. Gather journey data

Sources:

• User interviews (ask "walk me through...")
• Session recordings
• Analytics (funnel, drop-offs)
• Support tickets

1. Map the stages

Typical B2B SaaS stages: `` Awareness → Evaluation → Onboarding → Adoption → Advocacy ``

1. 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? ``

1. Map three experience paths (not just the happy path)

| Stage | Happy Path | Fail Path | Difficult Path | |---|---|---|---| | Awareness | Finds product via search | Never discovers product | Finds competitor first | | Consideration | Clear value proposition | Confused by pricing | Needs manager approval | | Decision | Easy signup flow | Form errors, abandons | Legal review delays | | Delivery & Use | Smooth onboarding | Can't import data | Workaround needed | | Loyalty | Becomes advocate | Churns silently | Stays but complains |

• Happy Path: Everything works as designed.
• Fail Path: User cannot complete their goal and drops off.
• Difficult Path: User completes the goal but with friction, workarounds, or frustration.

1. Add KPIs and ownership per stage

| Stage | Leading KPI | Lagging KPI | Team Owner | |---|---|---|---| | Awareness | Site visits, ad impressions | Brand recall | Marketing | | Consideration | Demo requests, pricing page views | MQL conversion | Marketing/Sales | | Decision | Trial starts, contract sent | Close rate | Sales | | Use | Feature adoption, DAU | Retention rate | Product | | Loyalty | NPS, referral count | LTV, expansion revenue | Customer Success |

1. Identify top friction points and interventions

For each friction point, document:

| Friction Point | Why It Matters | Intervention | Expected Impact | Effort | Confidence | |---|---|---|---|---|---| | [Description] | [User/business impact] | [Proposed fix] | High/Med/Low | S/M/L | High/Med/Low |

Priority Score = Frequency x Severity x Solvability

1. 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:

1. 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?" |

1. 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 |

1. 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

1. Define success metrics

| Metric | Target | |--------|--------| | Completion rate | >80% | | Time on task | <2× expected | | Error rate | <15%