UX persona template: how to build effective user personas

A UX persona is a composite representation of a real user segment, built to help a product team make decisions with that segment's actual needs and behavior in mind. Personas fail when they are built from internal assumptions rather than real interviews, and succeed when every detail on the template traces back to something a real participant actually said or did.

What belongs on a persona template

Goal. What is this person actually trying to accomplish, in their own words, not the feature they might click on.
Context. Where, when, and under what constraints does this person encounter the problem your product addresses?
Current workaround. What do they do today, before your product exists in their world, to deal with the problem?
Frustration. What specifically makes their current approach painful, in their own language, not a generic complaint?
Trigger to switch. What would need to be true for them to change how they currently solve this problem?
A representative quote. A real verbatim from an interview that captures the persona's voice better than a paragraph of description could.

What does not belong on a persona

Demographic details like age, income, or a stock photo are the least useful part of a persona and are often the first thing teams default to. Two people of the same age and income can have completely different goals and frustrations. What actually predicts useful product decisions is behavior and motivation, not demographics.

Building a persona from real research

A defensible persona starts with a set of qualitative interviews, run until the study reaches data saturation, the point where new interviews stop surfacing new goals or frustrations. Each field on the template should be traceable back to specific interview evidence, ideally with a verbatim quote or video clip attached, not a team's best guess at what a user probably thinks.

Key takeaways

A persona is only as good as the research behind it. Assumption-based personas actively mislead product decisions.
Goals, context, current workaround, and frustration matter more than demographic details.
Every field on a persona template should trace back to real interview evidence, ideally with a verbatim or video clip attached.
Personas should be rebuilt periodically as user behavior and the competitive landscape change, not treated as a one-time deliverable.

Frequently asked questions

How many interviews does it take to build a persona?

Enough to reach data saturation for the segment, commonly somewhere between 12 and 20 interviews, though it varies with how diverse the segment is and how complex the topic is.

Should personas include demographic information?

Demographic details can add context but should not be the primary content of a persona. Goals, current behavior, and frustrations predict product decisions far better than age or income.

How often should personas be updated?

Whenever the underlying user behavior or competitive landscape has meaningfully changed. A persona built from research more than a year or two old should be revisited before being used for a major decision.

Can AI-moderated interviews be used to build personas?

Yes. AI-moderated interviews can gather the goal, context, and frustration detail a persona needs across a large number of participants quickly, with video evidence a team can pull real verbatims from.

User interview questions: best examples for UX research
User research process: step-by-step framework for teams
What is data saturation in qualitative research?