What needs to be finished first
At least 10-15 structured interviews or qualitative observations from the target group are available, from which patterns can be derived.
Demographic, behavioral, or funnel data from analytics, CRM, or surveys complement the qualitative findings so segment sizes can be estimated.
What needs to be ready before start
Affinity mapping board (Miro, FigJam) for research synthesis; persona template with fields (name, photo, demographics, goals, pain points, behavior, context, quotes); optional quantitative data export (analytics, CRM).
A UX researcher as owner; one to three researchers with direct interview context; a Product Manager for segment prioritization; one to two designers for persona format and visuals.
Interview notes or transcribed highlights; demographic quantitative data; known internal persona attempts and their weaknesses; persona purpose (design decisions vs marketing messaging vs strategy).
1-3 days (1 day for synthesis, 1 day for persona creation, 0.5-1 day for validation)
Collect research highlights as stickies on an affinity board. Cluster by behavior patterns. Define the persona template (what to include, what to omit). Clarify the persona purpose explicitly (design vs marketing).
The one question this method answers
Which distinct user groups with different needs, goals, and behaviors can be derived from research, and which of them drive design decisions?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Synthesize research | 4-8 h | Collect interview highlights as stickies. Run affinity mapping: cluster by similar behavior, goals, pain points. Identify 3-5 clusters (often more is over-factored). | Anyone who clusters by demographics (age, gender) produces weak personas. Behavior and goals are the right dimensions. |
2Phase 2: Design persona profiles | 3-5 h | Create one persona profile per cluster: name (fictitious but memorable), photo, short context story, goals (3-5), pain points (3-5), behavior, representative quotes. Add realistic details from interviews. | Stock-photo personas without substance are ignored. Concrete quotes and behavior make personas usable. |
3Phase 3: Quant validation | 2-4 h | Check personas against quantitative data: how large is each segment? How are behaviorals distributed? If data contradicts the personas, adjust them. | Personas without quantitative anchors drift. If Persona X only covers 1% of the user base, the team should know that before treating it as driving. |
4Phase 4: Stakeholder validation | 1-2 h | Validate personas with stakeholders (sales, support, service). Who has regular customer contact? Do personas match their experience? | Sales and support often see different personas than the research team. If major differences exist, review research coverage or refine personas. |
5Phase 5: Team activation | 1-2 h | Distribute personas in the team, post them in design spaces, reference them in backlog templates. Name one champion per persona who challenges decisions through that persona lens. | Personas stored away in a drawer have no effect. Visibility and active use are the levers. |
What comes out at the end
Set of 3-5 persona profiles as one-page documents (PDF, Miro board, Notion page) with photo, demographics, context, goals, pain points, behavior, quotes, and segment size, plus guidance for team use.
Review personas annually for freshness because the market changes. For larger research rounds, create a new version with date. Mark outdated personas explicitly as archived, not deleted (history is valuable).
Compact working template for Personas with context, input, output artifacts, and next step.
Evidence-based archetypes of different user groups.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Context: Senior Product Manager, 8 years of experience, medium-sized company, leads product triad Goals: quick method overview for upcoming workshops; compare methods for similar problems Pain points: existing method pages are too generic; no practical instructions; no negative guidance on when a method does not fit Behavior: checks methods Sunday evening before Monday workshops; bookmarks 3-5 pages; extracts individual sections Quote: "I do not need theory, I need the trick to get this done in 45 minutes." Segment size: ~45% of first visits (analytics)
Context: Early-career PM or UX, 1-3 years experience, wants structure and basic understanding Goals: method overview as curriculum; understand when to use which method Pain points: he knows method names, but application is unclear; fear of choosing the wrong method Behavior: reads sequentially, checks related methods, stays in longer sessions Quote: "I want to first understand the differences between User Story Mapping and Event Storming." Segment size: ~30% (estimated from session-length buckets)
Context: External advisor or internal coach, 10+ years of experience, composes method sets for customers Goals: create method sets for a concrete customer problem; provide source references for pitches Pain points: source links are often weak; no curated sets; tags are not practical enough Behavior: filters by tags, copies lists, shares links Quote: "When I build a discovery program for a customer, I need five methods with clear sources." Segment size: ~15% (higher return rate)
Context: CTO in a startup, 50-150 employees, looks for architecture and product methods in parallel Goals: make fast method choices for mixed problems; cross-domain mapping Pain points: methods mostly exist in silos; no cross-recommendations between product and architecture Segment size: ~10% (small but highly recurring group)
Recognize symptoms and steer against them
Personas differ mainly by age, gender, or location, not by behavior and goals.
Switch dimensions to goals, pain points, and usage behavior. Treat demographics as background, not the differentiator.
8+ personas with small differences and no clear recall of who is who.
Consolidate to 3-5 personas. If more are needed, use sub-personas or acknowledge the segment is too heterogeneous for one set.
Personas are created in a stakeholder workshop without interview data.
Synthesize personas from research, not invent them during sprint planning. Without data grounding, personas become marketing decoration.
Personas are created once and never used or updated.
Post personas visibly in design spaces and reference them in sprint refinement. Refresh them annually. Otherwise they become decoration.
No one defends a specific persona perspective in decisions; it disappears in consensus.
Name one owner per persona who brings the persona lens into discussions. A persona without a voice is useless.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.