User Personas

Why Personas Matter

The Problem with "The User"

Without Personas:
┌─────────────────────────────────────┐
│  "Our users want..."               │
│       │                             │
│       ▼                             │
│  Generic solutions                  │
│  Conflicting priorities             │
│  Feature bloat                      │
│  Design by committee                │
└─────────────────────────────────────┘

With Personas:
┌─────────────────────────────────────┐
│  "Sarah the Marketer needs..."     │
│       │                             │
│       ▼                             │
│  Specific solutions                 │
│  Clear priorities                   │
│  Focused features                   │
│  Empathy-driven design              │
└─────────────────────────────────────┘

Benefits of Personas

For Design:

• Guides feature prioritization
• Informs information architecture
• Shapes interaction patterns
• Validates design decisions

For Teams:

• Creates shared understanding
• Aligns stakeholders
• Focuses discussions
• Resolves conflicts with data

For Business:

• Identifies market segments
• Informs marketing strategy
• Shapes product roadmap
• Measures success

Types of Personas

1. Proto-Personas

Based on stakeholder assumptions (not research).

Use when:

• Starting from scratch
• Limited research budget
• Quick alignment needed

Caution:

• Must validate with real research
• Risk of confirmation bias
• Temporary only

2. Qualitative Personas

Based on user interviews and observations.

Characteristics:

• Deep, rich insights
• Small sample (5-30 users)
• Behavioral focus
• Narrative-driven

Best for:

• New products
• Complex domains
• Behavior-heavy products

3. Quantitative Personas

Based on surveys and analytics.

Characteristics:

• Large sample sizes
• Statistical validation
• Segmentation focus
• Data-driven

Best for:

• Existing products with user base
• Proving hypotheses
• Prioritizing segments

4. Mixed-Method Personas

Combining qualitative and quantitative research.

Process:

1. Qualitative: Interview to find patterns
2. Quantitative: Survey to validate segments
3. Qualitative: Deep-dive into each persona

Gold standard for accuracy and richness.

Creating Personas

Step 1: Research

Qualitative methods:

User Interviews
├── 1-on-1 sessions (30-60 min)
├── Contextual inquiry (observe in environment)
├── Diary studies (longitudinal)
└── Focus groups (group dynamics)

Sample questions:
• Tell me about your typical day
• Walk me through how you [do task]
• What frustrates you most?
• What does success look like?
• What tools do you currently use?

Quantitative methods:

Surveys
├── Demographics
├── Behaviors (frequency, patterns)
├── Attitudes (scales, Likert)
└── Segmentation questions

Analytics
├── Usage patterns
├── Feature adoption
├── User flows
└── Cohort analysis

Step 2: Analyze and Synthesize

Find patterns:

Affinity Mapping:
1. Write observations on sticky notes
2. Group by similarity
3. Name the groups
4. Look for behavioral patterns

Example groups:
• Goals and motivations
• Pain points
• Tools and workflows
• Frustrations
• Success metrics

Identify personas:

Look for:
├── Distinct behavioral patterns
├── Different goals or needs
├── Varying contexts
├── Unique pain points
└── Separate workflows

Aim for: 3-5 primary personas
(Too many = unfocused, Too few = generic)

Step 3: Create Persona Artifacts

Essential elements:

┌────────────────────────────────────────────────────┐
│  [Photo]                                           │
│  NAME: "Sarah the Marketing Manager"              │
│  QUOTE: "I need to prove ROI without drowning      │
│         in spreadsheets."                          │
├────────────────────────────────────────────────────┤
│                                                    │
│  DEMOGRAPHICS                                      │
│  • Age: 32                                         │
│  • Role: Marketing Manager                         │
│  • Company: Mid-size B2B SaaS                     │
│  • Tech comfort: High                              │
│                                                    │
│  BEHAVIORS                                         │
│  • Checks analytics daily                          │
│  • Builds monthly reports                          │
│  • Uses 5+ marketing tools                         │
│  • Attends weekly standups                         │
│                                                    │
│  GOALS                                             │
│  • Demonstrate campaign effectiveness             │
│  • Reduce reporting time                           │
│  • Get stakeholder buy-in                          │
│                                                    │
│  PAIN POINTS                                       │
│  • Data scattered across tools                     │
│  • Manual report compilation                       │
│  • Hard to attribute conversions                   │
│                                                    │
│  MOTIVATIONS                                       │
│  • Recognition from leadership                     │
│  • Career advancement                              │
│  • Team efficiency                                 │
│                                                    │
│  SCENARIOS                                         │
│  "Sarah needs to prepare a board presentation..." │
│                                                    │
└────────────────────────────────────────────────────┘

Optional additions:

• Day in the life
• Tech stack
• Frustrations with current solutions
• Quotes from real users
• Photos (stock or real with permission)

Persona Templates

Basic Template

┌─────────────────────────────────────┐
│ [Photo]  Name: ________            │
│          Role: ________            │
│                                    │
│ "Quote"                            │
├─────────────────────────────────────┤
│ About                              │
│ • Demographics                     │
│ • Background                       │
│                                    │
│ Goals                              │
│ 1.                                 │
│ 2.                                 │
│ 3.                                 │
│                                    │
│ Frustrations                       │
│ 1.                                 │
│ 2.                                 │
│ 3.                                 │
│                                    │
│ Behaviors                          │
│ •                                  │
│ •                                  │
└─────────────────────────────────────┘

Detailed Template

┌─────────────────────────────────────┐
│ 1. OVERVIEW                        │
│    Name, photo, quote, archetype   │
│                                    │
│ 2. DEMOGRAPHICS                    │
│    Age, location, role, income     │
│                                    │
│ 3. PSYCHOGRAPHICS                  │
│    Values, attitudes, lifestyle    │
│                                    │
│ 4. BEHAVIORS                       │
│    Activities, habits, workflows   │
│                                    │
│ 5. GOALS                           │
│    Primary and secondary goals     │
│                                    │
│ 6. PAIN POINTS                     │
│    Current frustrations            │
│                                    │
│ 7. MOTIVATIONS                     │
│    What drives them                │
│                                    │
│ 8. TOUCHPOINTS                     │
│    Where they interact             │
│                                    │
│ 9. SCENARIOS                       │
│    Use cases and stories           │
│                                    │
│ 10. QUOTES                         │
│    Real user quotes                │
└─────────────────────────────────────┘

Using Personas in Design

Persona-Based Scenarios

Format:

Given [persona] in [context],
When they [trigger],
They want to [goal],
So that [outcome].

Example:
Given Sarah the Marketing Manager
who has a board meeting tomorrow,
When she opens the dashboard,
She wants to see campaign ROI at a glance,
So that she can prepare talking points quickly.

Design Reviews

Persona Check:
□ Would Sarah understand this?
□ Does this solve Sarah's pain point?
□ Is this workflow natural for Sarah?
□ Does this match Sarah's tech comfort?
□ Would Sarah find value here?

Feature Prioritization

Matrix: Persona Importance × Feature Relevance

              Feature A    Feature B    Feature C
Persona 1     High         Medium       Low
Persona 2     Low          High         High
Persona 3     Medium       Low          Medium

Prioritize: Feature B (serves multiple important personas)

Common Mistakes

1. Demographics Over Behaviors

❌ Focus on:
   • Age
   • Gender
   • Income
   • Location

✅ Focus on:
   • Goals
   • Pain points
   • Behaviors
   • Motivations

"A 25-year-old male from New York"
vs
"A busy professional who values efficiency"

2. Too Many Personas

❌ 12 different personas
    → Team can't remember them
    → Design becomes generic
    → Conflicting priorities

✅ 3-5 primary personas
    + 1-2 secondary personas
    → Clear focus
    → Memorable
    → Actionable

3. Not Based on Research

❌ "I think our users are..."
❌ Stereotypes
❌ Idealized users
❌ Internal assumptions

✅ Interview real users
✅ Observe actual behavior
✅ Validate with data
✅ Update based on feedback

4. Shelf-Ware Personas

❌ Created for kickoff, never referenced
❌ Hung on wall, ignored
❌ Not shared with team
❌ Not updated

✅ Reference in every design review
✅ Include in design docs
✅ Share with all stakeholders
✅ Update quarterly

Validating Personas

Quantitative Validation

Survey existing users:

"Which of these describes you best?"
• Persona A description
• Persona B description
• Persona C description
• None of the above

Measure: % alignment with each persona
Goal: >70% identify with at least one

Qualitative Validation

User testing:

Recruit users matching each persona
Test designs with them
Do their reactions match expectations?

Adjust personas based on findings

Ongoing Refinement

Quarterly Review:
□ Are behaviors still accurate?
□ Have goals changed?
□ New pain points emerged?
□ Tech landscape shifted?
□ Update photos and details

Advanced Techniques

Negative Personas

Who you're NOT designing for.

"Enterprise Edward"
• Needs: Complex workflows, compliance
• Budget: $100k+
• Timeline: 12-month sales cycle

Not our target (we're SMB-focused)
→ Helps say "no" to feature requests

Proto-Persona to Full Persona

Week 1: Stakeholder workshop

• Create assumptions-based personas
• Document hypotheses

Week 2-4: User research

• Interview 15-20 users
• Look for patterns

Week 5: Validation

• Refine personas with data
• Remove assumptions
• Finalize artifacts

Living Personas

Keep personas accessible and current:

□ Wiki page (Confluence, Notion)
□ Design system documentation
□ Slack bot responses
□ Dashboard in analytics tool
□ Printed cards for workshops

Update triggers:
• New research insights
• Product pivot
• Market changes
• Quarterly review