◧ UX & accessibility

Personas: how to build them on real data and actually use them

What personas are, why they often fail and how to build them from interviews and usage data, focusing on goals and contexts rather than stereotypes.

Personas are synthetic portraits of groups of users, presented as if they were single individuals: a name, a context, goals, difficulties. Used well, they help a team remember who it is designing for. Used badly, they become decorative posters on the office wall that nobody looks at or, worse, stereotypes that drive wrong decisions.

Why many personas fail

The most common failure is making them up. A one-hour meeting in which the team imagines «Julia, 34, loves yoga and coffee» produces a plausible character with no foundation. Decisions taken with Julia in mind are really decisions taken with the team's opinions in mind.

Other frequent problems:

  • too many irrelevant details: hobbies, car brand, pets, which do not affect how the product is used;
  • too many personas: ten different profiles amount to choosing none;
  • demographics instead of behavior: age matters less than people think; what matters more is how often someone performs a task and under what conditions;
  • no updates: the product and its audience change, the personas stay frozen.

Start from data

A useful persona comes from real research. The main sources are:

  1. interviews with current and potential users, focused on concrete episodes;
  2. observation of the context of use, when possible;
  3. product usage data: which features are used, how often, from which devices;
  4. support requests: a valuable archive of real difficulties, already written in users' own words.

Once the information is gathered, look for the variables that truly distinguish groups. For invoicing software they might be the number of invoices issued per month, familiarity with accounting, and whether someone works alone or with an accountant. Placing interviewees along these dimensions reveals natural clusters: each one is the core of a persona.

What it should contain

An effective persona fits on one page. The essential elements are:

Element Example for invoicing software
Name and short role «Luca, tradesman who invoices on his own»
Context Works on building sites, handles invoices in the evening from his phone
Goals Issue an invoice in a few minutes, know who hasn't paid
Difficulties Little familiarity with tax terms, little time, small screen
Behavior About ten invoices a month, almost always to the same clients
Real quote A sentence taken from an interview, not invented

A quote from a real interview is a small detail with a big effect: it reminds everyone that there are real people behind the profile.

The name and photo make the profile memorable, but they should be chosen carefully so as not to reinforce stereotypes. Many teams prefer neutral illustrations or no image at all, precisely to shift attention to goals and context.

Primary and secondary personas

Not all profiles carry the same weight. The primary persona is the one for whom the product must work excellently; secondary ones have additional needs that can be met without compromising the primary. If two personas have conflicting needs and both are primary, perhaps you are dealing with two different products, or with two modes of use that should be clearly separated.

Using them in everyday work

A persona is only useful if it enters conversations. Some concrete ways:

  • in priority discussions, ask «Which of Luca's goals does this feature help with?»;
  • in usability tests, recruit participants who match the primary profiles;
  • in design reviews, walk through a typical task in the persona's shoes, with their device and the time they have;
  • in content work, check that the language suits their level of familiarity with the subject.

Alternatives and complements

Some teams prefer tools closer to the task, such as «jobs to be done», which describe the situation, the motivation and the expected outcome without building a character. These approaches are not incompatible: a persona can include the main jobs it needs to get done, and a job map can refer to the profiles.

In short

  • Useful personas come from interviews, observation and usage data, not from creative meetings.
  • Goals, context and behavior matter far more than demographic details.
  • A few profiles, with a clear primary persona, guide decisions better.
  • A persona is only useful if it is used in discussions, tests and reviews.
MM
Marco Marzaduri

Marco Marzaduri works in cybersecurity, digital forensics and web development. With degrees in computer science and psychology, he combines technical analysis with an understanding of the human factor.

Read also