A quickly assembled user archetype built from team assumptions and existing knowledge rather than new primary research. Proto-personas help align teams early in a project but should be treated as hypotheses to be validated — not as substitutes for proper research-backed personas.
Common contexts
- Running a two-hour workshop at project kickoff to surface team assumptions about the target user before any research begins
- Creating a draft archetype from support ticket themes and sales call notes to guide early design explorations
- Building a shared starting point for a cross-functional team that would otherwise each bring conflicting mental models of 'the user' into design reviews
Use when
Create proto-personas at project kickoff when no research exists yet and the team needs a shared starting point to make early design decisions — explicitly framing them as assumptions to be tested, not validated facts.
Avoid when
Don't allow proto-personas to outlive the research phase — once real user data exists, continuing to design against assumption-based archetypes introduces systematic bias that compounds with every subsequent decision.
Proto-personas are most dangerous not when they're wrong, but when they're partially right — the plausible details make teams skip the research that would reveal where the archetype fundamentally breaks down.
Real-world examples
- Spotify created proto-personas ('The Commuter', 'The Fitness Buff', 'The Party DJ') in the first week of a podcast feature sprint, aligning a cross-functional team on user intent before any research was conducted.
- Product teams at startups use proto-personas to make consistent hiring, roadmap, and marketing decisions without waiting months for formal research — treating them as hypotheses to be validated, not final truths.
- GOV.UK uses proto-personas to onboard new design team members, giving them a working model of the 'Baffled Betty' and 'Savvy Sam' user archetypes to apply immediately before they conduct their own research.