The Short Answer
Personas shouldn’t be fiction. They should be facts.
Persona patterns turn research data into design decisions.
Traditional Personas vs Persona Patterns
Traditional Personas
- Names and photos
- Detailed backstories
- Demographics
- Often fabricated
Persona Patterns
- Behavioral segments
- Research-backed
- Context + goals
- Actionable design implications
Creating Persona Patterns
Step 1: Research
Interview users. Observe behavior. Collect data.
Step 2: Segment
Group by behavior, not demographics. What do they actually do?
Step 3: Pattern Match
Identify recurring goals, contexts, and frustrations.
Step 4: Design Implications
What does each pattern mean for your design?
Real Persona Patterns
The Time-Poor Professional
- Goal: Complete tasks quickly
- Context: On-the-go, distracted
- Frustration: Slow processes
- Design: Efficiency-focused, minimal steps
The Careful Learner
- Goal: Understand before acting
- Context: Methodical, analytical
- Frustration: Ambiguous instructions
- Design: Clear guidance, progressive disclosure
The Occasional User
- Goal: Remember how to use the product
- Context: Infrequent, forgetful
- Frustration: Forgetting workflow
- Design: Reusable templates, clear navigation, help on demand
Persona Pattern Template
Name: [Pattern name]
Behavior: [What they do]
Context: [When/where they use]
Goals: [What they want]
Frustrations: [What annoys them]
Design Implications: [How to design for them]
The Bottom Line
Personas are great. Persona patterns are better. Research-backed behavioral segments drive design decisions. Fictional characters drive conversations. Both have value. Use both.