Ir al contenido

User persona

De Scrum Manager BoK
Esta página es una versión traducida de la página User persona. La traducción está completa al 100 %.
⏱ 3 min  ·  📅 2026
A user persona is a fictional yet realistic representation of a type of product user, built from observations, interviews, and qualitative data gathered during research with real users. It is not a statistical archetype or a demographic profile: it is a narrative description of a specific user—with a name, context, motivations, and frustrations—that makes the user tangible during product design.

The concept was introduced by Alan Cooper in his book The Inmates Are Running the Asylum (1999).

What it is for

  • Give the team a specific human reference during design sessions: instead of "the user," the team talks about "María, a 38-year-old project coordinator who uses the product on her phone between meetings."
  • Align product decisions around real needs, not assumptions.
  • Prioritize features: "Does this help María solve her main problem?"
  • Communicate with stakeholders who are not involved in user research.

What a well-built persona includes

  • Name and photo (illustration): to make the persona tangible and memorable.
  • Demographic and contextual profile: age, occupation, context in which the product is used.
  • Motivations and goals: what they want to achieve with the product (connects with Jobs to Be Done).
  • Frustrations and obstacles: what makes it difficult for them to achieve their goals.
  • Desired benefits: what positive outcomes they expect.
  • Behaviors: how they currently use the product or similar products.
  • Verbatim quotes: real phrases from interviews that capture their perspective.

How many personas to create

The answer depends on the product, but the general rule is to use the minimum number of personas that covers the relevant user segments without losing specificity. Too many personas dilute the focus; too few may overlook important segments.

Common pitfall

Building personas without prior research. A persona built on the team's assumptions—instead of interviews and observation—reflects the team's biases, not the real needs of users. "Made-up" personas give the illusion of user-centeredness without the real benefit. If there is no time for research, it is better not to create personas at all than to create false personas that reinforce wrong decisions.

Resources

🏦 Skill Design ThinkingState of the art and development guide · Skill Arena

📄 User persona templateResources · Scrum Manager

See also

Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.