proto-persona
Structured template for creating hypothesis-driven user personas from available research and stakeholder knowledge.
- Synthesizes existing user research, market data, and team insights into a working customer profile without requiring months of validation
- Includes step-by-step guidance for defining persona identity, voice, context, and decision-making influences with quality checks at each stage
- Designed to align teams early, guide initial design decisions, and explicitly surface assumptions that require validation through research
- Distinguishes proto-personas from validated personas and includes anti-patterns to avoid (treating assumptions as fact, fabricating quotes, creating too many personas)
Purpose
Create an initial, assumption-based persona profile that synthesizes available user research, market data, and stakeholder knowledge into a working hypothesis about your target user. Use this to align teams early in product development, guide initial design decisions, and identify gaps in understanding that require validation through research.
This is not a validated persona—it's a "proto" (prototype) persona that evolves as you learn more. Think of it as a structured placeholder that prevents design-by-committee while acknowledging you don't have all the answers yet.
Key Concepts
What is a Proto-Persona?
A proto-persona is a lightweight, hypothesis-driven persona created from:
- Existing research: User interviews, surveys, analytics (if available)
- Market data: Industry reports, competitor analysis, demographic trends
- Stakeholder knowledge: Sales, support, and team insights
- Informed assumptions: Best guesses that need validation
Proto vs. Validated Persona
| Proto-Persona | Validated Persona |
|---|---|
| Created in hours/days | Created over weeks/months |
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K