What is a persona in UX?
A persona in UX is a fictional but research-based profile of a typical user, describing their goals, habits and frustrations to keep design decisions grounded.
also calleduser persona · user profile · customer persona · buyer persona
A persona is a made-up person built from real findings. Instead of arguing about what "users" want, the team can ask what Maria, a part-time bookkeeper juggling three clients, would do on this screen. A name and a face make it far harder to forget that real people have to use what you build.
- A persona is a fictional character built from real research on a group of users.
- Keep it short and include only what affects design decisions.
- Two or three well-used personas beat a wall of unused ones.
- A persona does not replace talking to real users.
What goes into a persona
A useful persona is short, usually a page or less, and focuses on what affects the design. Typical ingredients are:
- A name, a photo or illustration, and a one-line summary
- Their goals: what they are trying to achieve with your product
- Their frustrations and fears
- Relevant context, such as devices, environment and skill level
- A quote that captures their attitude
Demographic details like age and city only belong if they change a design decision. Knowing someone is 34 rarely helps. Knowing they only have two minutes between meetings often does.
Built on research, not imagination
This is the dividing line between a persona and a puppet. A real persona comes from interviews, surveys, support tickets and analytics. You look for patterns: groups of people with similar goals and behaviors, and you turn each group into one character.
A persona invented in a workshop from assumptions is worse than none, because it gives guesses the authority of evidence. If you cannot point to the research behind a detail, leave it out or label it as a hypothesis.
How teams actually use them
Personas earn their place in everyday decisions. During planning they help you decide who a feature is for. In design reviews they prompt questions like "Would Maria understand this label?". They also help non-designers, such as developers and marketers, share one picture of who they are building for.
Keep two or three, not twelve. A crowd of personas becomes a poster on the wall that nobody consults.
Criticism worth hearing
Personas have real critics, and some of their points are fair. Stereotypes sneak in easily, especially when pictures, names and hobbies carry more detail than the research supports. Personas can also make teams feel they understand users without ever talking to one.
Some designers prefer jobs to be done or scenario-based approaches that focus on situations instead of people. Whichever tool you use, the point is the same: stay connected to real users.
Persona or user segment?
A segment is a statistical group, such as customers on a certain plan. A persona is a story about a representative person within a group. Segments are good for sizing and targeting, personas for empathy and design decisions. Teams often use both.
Persona: your questions, answered
What is a user persona?
It is a fictional profile representing a group of real users, built from research. It describes goals, behaviors, frustrations and context so that designers and the wider team can make decisions with a specific person in mind.
How do you create a UX persona?
Collect research through interviews, surveys and analytics, look for patterns in goals and behaviors, then group similar people. Turn each group into a short profile with a name, goals, frustrations and context, and check it with the team and with real users.
How many personas should a project have?
Usually two to four. Enough to cover the main user groups, few enough that people remember them. If you need many, consider whether you are splitting groups by details that do not change the design.
Are personas still useful?
Yes, when they come from solid research and are used in decisions. They lose value when they are invented from assumptions or filed away after the workshop. Their purpose is empathy and alignment, not decoration.
What should a persona not include?
Skip details that do not affect design, such as favorite foods or random hobbies, unless research shows they matter. Avoid stereotypes and unsupported claims. Every detail should trace back to something you learned.
More quick answers
What is the difference between a persona and an empathy map?
A persona describes a user type overall, while an empathy map captures what a user thinks, feels, says and does in a given situation. They work well together.
Is a persona the same as a target audience?
Not quite. A target audience is a broad group defined by traits like market or demographics. A persona is a specific, behavior-based character within it.
Can you make a persona without research?
You can, but it will be a guess. If you must, label it a proto-persona and plan to replace it with research-based findings.
What is an anti-persona?
An anti-persona describes someone you are deliberately not designing for. It can help a team say no to features that serve the wrong audience.
Where do personas fit in the design process?
Mostly after research and before ideation, where they guide the problem statement, user flows and design decisions.
An empathy map in UX is a simple one-page diagram that captures what a user says, thinks, does and feels, to help a team see the world from their side.
User research in UX is the practice of studying people who use or might use a product, to understand their needs and behavior so design rests on evidence.
A user journey map in UX is a visual timeline of the steps a person takes to reach a goal, showing their actions, thoughts, emotions and pain points.
An end user in UX is the person who actually uses a finished product to get something done, as opposed to the people who buy, build or manage it.
Empathy in UX is the ability to understand what users think, feel and need, and to let that understanding shape every design decision you make.
A user interview in UX is a one-on-one conversation where a researcher asks people about their goals, habits and frustrations to understand their real needs.
Found this useful? A GitHub star helps other designers find it.