Personas

---
type: subskill
title: "Personas"
---

# Personas

## Core Concepts

- Personas represent distinct user segments with different goals, constraints, and behaviors
- They replace the generic "as a user" with specific actors who have real motivations
- Good personas are research-backed: based on interviews, analytics, and observation
- Fewer is better: 3-5 primary personas cover most design decisions
- Personas make trade-offs visible: optimizing for one persona may hurt another

## Key Practices

- Define personas by goals and frustrations, not demographics alone
- Include technical proficiency, usage frequency, and environmental constraints
- Use personas in story writing: "As [Persona], I want X because [persona-specific motivation]"
- Identify the primary persona whose needs take precedence when conflicts arise
- Validate personas against real user data periodically  -  retire stale ones

## Common Mistakes

- Creating aspirational personas instead of reflecting actual users
- Making personas so numerous they lose decision-making power
- Treating personas as decorative artifacts rather than active design tools

## When to Apply

- The team says "users want" without specifying which users
- Design decisions require understanding different user contexts and constraints
- Prioritizing features: which persona does this serve and is that persona primary?
- Onboarding new team members who need to understand who they're building for