User Persona Template (With a Filled-In Example)
Heads up: This is our own user persona template, with a filled example built around one user (Maya) so you can see the method in action. The example is illustrative.
User persona canvas
Maya Reyes — long-term freelancer
“Because I work for myself, I have to track everything myself!”
- 58 years old
- Freelance for 3 years
- Works from home
- Two sons (29, 32); husband at an architecture firm for 12 years; often minds her 2-year-old grandchild
- Finds the bank's online portal confusing
- Risk of clients who don't pay → anxiety at every payment date
- Uses the call center because the portal confuses her
- Wants to trust her bank for daily and personal matters
- Irregular income → can't plan ahead → watches savings closely
- Would rather answer her own questions than call support
See the bank as a retirement-savings planner
Check account activity across multiple channels
A bank to rely on in hard times
Self-serve answers without calling
A user persona template is only useful if it helps you design for a real person instead of a vague “the user.” The problem with most free templates is that they hand you empty boxes and no sense of what good looks like. This one comes with a complete, filled-in example so you can see how each section actually gets used.
A persona is a one-page portrait of who you’re designing for: their context, their needs, what frustrates them, and — most importantly — the insights that turn into design opportunities.
The point of a persona: it’s not a character sketch for its own sake. It exists to align the team on who you’re designing for and to surface the needs and frustrations your design has to address.
What goes in a user persona
A strong persona has six parts:
- Photo and name — a face and a real name make the persona memorable, not abstract.
- A quote — one line in the user’s own voice that captures their mindset.
- Definition — the basics: age, occupation, location, family, tech comfort.
- Needs — what they’re trying to achieve, and the support they look for.
- Pain points — what frustrates them, what makes them anxious, what they avoid.
- Insights and opportunities — the design openings that fall out of the above.
The first three orient the reader. The last three are where the design value is.
How to use the template
- Base it on research, not assumptions. A persona built from interviews carries weight; one invented at a desk is just a guess. (If you have no research yet, use a proto-persona and label it as such.)
- Write needs as verbs, not nouns. “Needs to feel in control of her payments” is an insight. “Needs an app” is a premature solution.
- Quote the user directly. Real phrasing beats your paraphrase.
- End on opportunities. Each pain point should suggest a design opening — that’s what makes the persona actionable.
A filled-in example: Maya
Here’s the template completed for one user, so you can see the level of specificity that makes a persona useful.
Maya Reyes — long-term freelancer
“Because I work for myself, I have to track everything myself!”
Definition
- Age: 58
- Occupation: Freelance for 3 years
- Location: Works from home
- Family: Two sons (29 and 32); her husband has worked at an architecture firm for 12 years. Because she works from home, her older son often asks her to look after her 2-year-old grandchild.
- Tech comfort: Modest — finds the bank’s online portal confusing.
Needs
- Freelancing means the risk of clients who don’t pay, so she feels uncertainty and anxiety around every payment date.
- She always uses the call center to check account activity, because the online portal confuses her.
- She values being able to trust her bank — both for day-to-day financial support and for more personal matters.
Pain points
- Irregular freelance income means she can’t make future plans with confidence, so she’s anxious and watches her savings closely.
- She’d much rather answer her own questions than be forced to call customer service.
Insights and opportunities
- See the bank as a planner for her retirement savings.
- Let her check account activity across multiple channels.
- Be the institution she can rely on in hard times.
Notice how the pain points lead directly to opportunities. “The portal confuses her, so she calls” becomes “let her self-serve across channels.” That hand-off is the whole job of a persona.
A tip for building empathy
To make a persona feel real, pay attention to what makes the person happy or frustrated — not just what they do, but how they feel and what they experience. Review your interview data and look for contradictions between what people say and what they actually do; those gaps are usually where the strongest insights live.
What to use before and after
- Before: a user interview gives you the real input a persona needs.
- After: map this persona’s customer journey to find the painful moments worth designing for.
For the bigger picture of how research like this becomes a portfolio piece, see the UX case study guide and real examples.
A persona shows you understood your user — and that’s exactly what a strong case study proves. When you’re ready to write yours up, Folioverse helps you turn the thinking into a case study recruiters trust. Try it free.