Free tool

Build a user persona, not a fill-in-the-blank exercise.

Fill in the form below and watch a real persona card take shape as you type. Starts pre-filled with a worked example so you can see what “good” looks like before you touch a field. Supports multiple personas, saves your work automatically, and exports to Markdown. No signup, nothing sent anywhere unless you use the optional AI draft.

Start building ↓What should a persona include? →

The tool

Edit the example, or start fresh.

The example below is a fictional but realistic stakeholder persona -- deliberately a non-designer, since that is who most of our students end up designing alongside. Edit it directly, or click “+ Add persona” to start a blank one.

Personas:

Optional: draft with AI

Describe your product and audience in a sentence or two and we will draft a starting persona into the form below. An AI draft is a starting point built from assumptions, not research -- a persona that is not grounded in real users is a liability, not an asset. Treat every field as a hypothesis to test, not a fact.

Your product and audience

Persona details

Name

Role / job title

Age range

Context of use

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

Goals

One per line. Keep to 2-3.

Key tasks

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

Frustrations

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

Motivations

What actually drives their decisions.

Tech confidence

Representative quote

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

What would make them abandon us

The specific failure that loses them for good.

Preview

Priya Chandran

Head of Operations (non-designer stakeholder) · 35-44

“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 does not have time to sit still with. She is not the one who requested the tool but she is the one whose team lives in it.

Goals

Approve or reject a request in under two minutes
Trust that the numbers she is 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
Cannot tell if a change she made actually saved
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 is merely plain.

Tech confidence

Moderate

What would make them abandon us

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

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 is built from.

This tool will happily produce a clean, professional-looking persona card from nothing but assumptions. That is exactly the trap: a confident-looking artefact with no real user behind it gives a team false certainty. The fields here (context of use, specific frustrations, a real quote, a concrete reason someone would abandon you) are the ones that actually change design decisions, but they only do that work if the answers came from watching or talking to real people -- interviews, usability sessions, support tickets, sales call notes. If you filled this in from imagination or from the AI draft, say so on the persona itself, and treat it as a hypothesis to go and test rather than a finished deliverable.

Questions

About this tool.

Is this the same as the user persona template?

No. The persona template page explains what a good persona template contains and why, as a static download. This tool is for actually building one: fill in a form, see a live persona card, save multiple personas, and export as Markdown. Use the template page to learn the fields; use this tool to fill them in.

Is my data saved anywhere?

Everything you type is saved only in your own browser (localStorage), on your own device. Nothing is sent to a server unless you use the optional "Draft with AI" button, which sends only the one-sentence description you type into that box.

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 is not 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 is no watermark, login, or attribution requirement.

Next step

Want feedback on a persona you built for a real project?

Send us what you have got and tell us a bit about the project. We will not build your research for you, but we will tell you honestly whether the persona would survive a design review.

Part of a set

A persona is usually the first of three artefacts. Once you have one, map what happens to them with the Journey Map Builder, or synthesise raw research into one with the Empathy Map Builder.

Learning UX yourself

Tools help you do the work. They do not teach you the judgement behind it. Beginner UX (AI) Design is taught live online by working UX professionals, built for career-changers with no design background. Get the brochure and see the full curriculum, the schedule and what the weeks actually involve.

Working in a team rather than learning on your own? We run in-house UX training built around your own product, or you can book a call to talk it through.