Proto-Persona Template (With an Example)
Heads up: This is our own proto-persona template. The example is illustrative.
Proto-persona canvas
Freelance Fatma — assumption-based
Freelance Fatma (rough sketch)
45–60, self-employed, modest tech comfort; uses mobile apps but not power features
Know where her money is; avoid surprises; don't waste time on admin
Trusts the call center over the app; checks balance often; anxious about late client payments
A proto-persona template is the fast, honest version of a persona: a quick sketch built from what the team believes, before you have real research. It shifts the focus from the thing you’re building to the person you’re building it for — and gets every stakeholder’s assumptions on the table where you can see them.
Why it works: a proto-persona isn’t pretending to be evidence. It’s a brainstorm artifact that aligns stakeholders and gives you a starting hypothesis to validate. Its honesty about being an assumption is the whole point.
What goes in a proto-persona
Four quadrants:
- Sketch and name — a rough drawing and a name. A sketch is enough; this isn’t a polished persona.
- Demographics — the basics you’re assuming.
- Needs and goals — what you think this person is trying to achieve.
- Beliefs and behaviors — how you think they act and what they believe.
How to use it
- Get stakeholders in a room with the product.
- Give individuals or small groups ~15 minutes to each draft a proto-persona.
- Share them out loud, find the overlaps, and merge into a few core proto-personas everyone recognizes.
- Label it as assumptions. Then go validate it with user interviews and turn it into a real persona.
Team of 1–12, ~15 minutes per proto-persona, with paper, markers, and sticky notes.
An illustrative example
Before any research, a bank team’s proto-persona for a freelance customer:
- Sketch & name: “Freelance Fatma” (rough sketch)
- Demographics: 45–60, self-employed, modest tech comfort, uses mobile apps but not power features.
- Needs & goals: Know where her money is; avoid surprises; not waste time on admin.
- Beliefs & behaviors: Trusts the call center more than the app; checks her balance often; anxious about late client payments.
This is a hypothesis, not a fact. Run interviews and it might hold, shift, or break — and that evolution is exactly what makes a strong case study later.
What to use after
Validate the proto-persona with user interviews, then build a research-based persona and empathy map.
For how an assumption-to-evidence story becomes a portfolio piece, see the UX case study guide.
Showing how your assumptions evolved into evidence is what makes a case study credible. Folioverse helps you turn that thinking into a case study recruiters trust. Try it free.
FAQ
What is a proto-persona?
A proto-persona is a fast, assumption-based sketch of a user built from what the team believes, before you have real research. It is a brainstorm artifact that aligns stakeholders and gives you a starting hypothesis to validate.
What is the difference between a proto-persona and a persona?
A proto-persona is based on team assumptions and made before research, while a persona is research-based. You validate a proto-persona with user interviews and then turn it into a real persona.
What goes in a proto-persona?
Four quadrants: a sketch and name, demographics, needs and goals, and beliefs and behaviors. Each is a rough, assumed version rather than a polished or evidenced one.