What are Personas?

In the context of marketing and user experience design, a persona is a fictional representation of a typical user or customer that is used to guide product development and marketing strategies.

Personas are created based on research and data collected about a target audience, and are designed to represent the needs, goals, behaviors, and preferences of different types of users. They are typically given a name, demographic information, and other characteristics that make them feel like real people.

Personas are useful in product development and marketing because they help teams to focus on the needs and wants of their target audience, rather than making assumptions or designing for themselves. Personas can help to answer questions such as: What are the key pain points that our customers experience? What motivates them to use our product? What features or functionality would be most valuable to them?

Personas can be used to inform a wide range of product development and marketing activities, such as user research, user interface design, content creation, and advertising. By designing products and marketing campaigns that are tailored to the needs of specific personas, companies can increase the likelihood of success and better connect with their target audience.

Why it matters

They help teams consider needs beyond their own experience and make design assumptions visible.

Example

Imagine research for a booking service revealing two recurring behaviors: frequent users know the process well, while occasional users struggle to remember what information they need. The team builds a persona representing the occasional user's goals, context, and difficulties, grounding it in interviews and observed sessions. It uses that persona to question a proposed shortcut that assumes prior knowledge. The team then tests clearer preparation guidance with real occasional users and checks whether they can complete a booking. The persona helps focus design conversations, but direct evidence from users determines whether the change actually addresses their needs.

Common misunderstanding

A persona can look convincing because it has a name, photograph, and detailed biography, even when those details were invented. That apparent realism may cause teams to defend assumptions about a user group instead of learning from people whose behavior differs.

Separate research findings from hypotheses and focus on needs, goals, and behavior relevant to the decision. Do not assume a demographic characteristic explains how someone will use a service. Personas help organize understanding; they do not replace contact with real users or evidence that challenges the profile.

Related terms

Customer Journey Map · Kano Model · Mock Prototype

Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.