User Persona Template

Open in app

Fill in who this persona is, what they're trying to do and what gets in the way. It saves in your browser as you go.

Showing example: Head of Operations (full example)

Persona details

Photo (optional)

Shrunk to a small square and kept in this browser only. Without one, we show initials.

When, where, and why do they use this? This matters more than demographics.

One per line. Keep to 2-3.

One per line. What they need to actually be able to do.

One per line. Be specific and observable, not vague.

What actually drives their decisions.

A direct, first-person line that captures their perspective.

The specific failure that loses them for good.

Preview

Priya Chandran

Head of Operations (non-designer stakeholder)

“I do not need it to be beautiful. I need to know it did what I told it to do.”

Context of use

Reviews the internal booking tool a few times a week, usually between meetings, on a laptop she doesn't have time to sit still with. She isn't the one who requested the tool but she's the one whose team lives in it.

Goals

  • Approve or reject a request in under two minutes
  • Trust that the numbers she's looking at are current
  • Avoid having to ask IT or the designer to explain the screen to her

Key tasks

  • Approve a pending request
  • Check whether a change has taken effect
  • Find last week's numbers without asking someone for a screenshot

Frustrations

  • Has clicked the wrong button twice because two actions look identical
  • Can't tell if a change she made actually saved, so re-clicks and re-checks rather than trusting the screen
  • Gets asked to "just try the new version" with no explanation of what changed or why

Motivations

Wants her team to look competent to the wider business. A tool that makes her hesitate in front of others is worse to her than a tool that's merely plain.

What would make them abandon us

If a second unexplained UI change causes a visible mistake in front of her own team, she'll ask for the old version back and stop trusting updates altogether.

myuxacademy.com/tools/persona-builder/

Kept in this browser. Log in to save it to your account and open it on another device. Download the PNG or the .md file to keep a copy.

Copy always works. The download button may be blocked in some embedded browsers. If nothing happens, use Copy instead.

Be honest about limits

A persona is only as good as what it's built from.

Context of use, specific frustrations, a real quote, a reason someone would abandon you — these are the fields that change design decisions. They only work when the answers come from real people: interviews, usability sessions, support tickets, sales calls.

Filled it in from imagination or the AI draft? Say so on the persona, then go and test it.

Treat as a· hypothesis, not fact ·
Questions

Frequently asked questions

What should a user persona template include?

A name and role, a representative quote, context of use, two or three goals, key tasks, specific frustrations, motivations, and what would make this person abandon your product. Add a mental model and an evidence line (where it came from) if you can. Leave out hobbies, family details and tech-savviness scores unless they change a design decision.

Can I download a blank user persona template?

Yes. The "Download blank template" link above the editor gives you a Markdown file with every section and a prompt for what goes in it. Open it in any text editor, Notion, Google Docs or Confluence. Or skip the download and fill the same fields in here, with a live preview card.

Is my data saved anywhere?

Everything you type is kept in this browser (localStorage), on your own device. Log in to save it to your account and open it anywhere. The only things that leave your browser are the one-sentence description you type into the optional "Draft with AI" box, and your work if you choose to save it.

Is the AI-drafted persona based on real research?

No, and this matters. An AI draft is a plausible starting point built from patterns and assumptions, not from talking to your actual users. Treat every field it fills in as a hypothesis to go and test, not a fact. A persona that isn't eventually grounded in real user research is a liability: it gives a team false confidence in decisions nobody actually checked.

Can I use this for a real client or work project?

Yes. Export as Markdown and paste it into whatever deck, doc, or wiki your team already uses. There's no watermark, login, or attribution requirement.

WhatsApp us