Strategy
Proto-Personas
A practical early-stage UX strategy method for aligning teams on user hypotheses and planning what to validate.
How to create proto-personas to guide early design decisions, surface assumptions, and prioritise user research.
What it is
Proto-personas are preliminary, assumption-based representations of users, created early in a project when full serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service glossaryDataData is raw, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term is not yet available.
They capture hypothesised demographics, glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, goals, motivations, and glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term based on existing knowledge, glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term input, and market understanding.
The focus is on guiding early design decisions and identifying areas for validation.
Key takeaway
The goal is to provide a working model of users to inform ideation, design, and research planning.
When to use it
Use this method when you need early user glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term.
It is most useful when:
It is less useful when:
Proto-personas are often used alongside persona creation and research planning.
How to run it
Set up properly
Be clear on why you are making them, what they are based on, and which decisions they will inform. Proto-personas are assumption made explicit, which is useful only if the assumption is labelled.
Involve the people who hold the assumptions (sales, support, product) since the point is to surface what the organisation already believes.
Run the method
Proto-personas capture what a team currently assumes about its users, before serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service. Their value is in making disagreement visible, not in being accurate.
- Identify the hypothesised user groups, and be specific enough that two of them could not be merged.
- Capture assumed goals, glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term and glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term, alongside demographics only where they genuinely affect behaviour.
- Visualise simply. Effort spent on presentation makes an assumption look like a finding.
- Share with the team and record where people disagreed. The disagreements are the most valuable output of the exercise.
- Mark every assumption that needs validating, and turn the list into serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service questions.
Label them clearly as assumptions and revisit them once serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service exists. A proto-persona that quietly becomes a persona is the failure mode of the method.
Capture and make sense of it
The value comes from making assumptions explicit. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- The hypothesised groups and what is assumed about each
- Where the team disagreed, which marks genuine uncertainty
- Assumptions carrying the most risk if wrong
- The serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service needed to confirm or replace them
Use this to align a team quickly and to plan serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service. It is a starting point with an expiry date.
Key takeaway
Use this to start designing with user awareness.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If assumptions are not challenged, they mislead design.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps your team design with focus before full data is available.
Get in touch
If this sounds like something you need, we can help you create proto-personas to guide your early design and plan research effectively.
No guesswork. No assumptions. Just informed starting points for user-centred design.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What are proto-personas in UX?
They are assumption-based, preliminary representations of users used in early project stages.
When should you create proto-personas?
At the start of a project, before full research is complete.
What can you include?
Hypothesised demographics, goals, behaviours, and pain points.
Why are they important?
They guide early decisions and highlight assumptions to validate later.
Do proto-personas improve UX?
Yes. They provide focus and context for early design decisions while research is being conducted.
Quick take
If you need a starting point before full research, proto-personas help you design with early assumptions.
Related Services
