arrow_back Artifacts

Personas

A Persona (or User Persona) is a fictional user archetype based on real research data that represents a group of users with similar behaviors, goals, and motivations.

artifacts schedule 3 min read
toc Table of Contents expand_more
Info Icon Definición Rápida
A Persona (or User Persona) is a fictional user archetype based on real research data that represents a group of users with similar behaviors, goals, and motivations. It is used to humanize users and keep the design team focused on their needs.

What are Personas?

Imagine you’re designing a backpack. You could design it for “everyone,” but you’d probably end up with something generic that nobody loves. Instead, you could design it for “Ana, a 20-year-old university student who commutes to campus by bike, needs to carry her laptop and books, and values sustainability and style.”

That is a Persona. It’s not a real person, but it represents a real group of your users. It’s created from data collected through User Interviews and other forms of research. A typical Persona includes:

  • A name and a photo: To make it memorable and human.
  • Basic demographics: Age, occupation, location.
  • A short biography: A paragraph telling their story and their relationship with the problem you’re solving.
  • Goals: What do they want to achieve?
  • Frustrations (Pain Points): What prevents them from achieving their goals currently?
  • Motivations: What drives them?
  • A key quote: A phrase that summarizes their attitude.

Why are they important?

  • They create a common language: They allow the entire team to talk about “Ana” instead of “the user,” ensuring everyone has the same mental image of who they’re designing for.
  • They foster empathy: Putting a face and name to research data helps the team connect emotionally with users.
  • They guide design decisions: When in doubt, the team can ask: “What would Ana do in this situation?” or “Would this help Ana solve her problem?”
  • They prevent “designing for yourself”: They are a constant reminder that you are not the user. They help prevent designers and developers from making decisions based on their own preferences.

How are they made?

  1. Conduct the research: Personas are not invented. They are based on data. The first step is always to conduct [[User Interviews]], surveys, etc.
  2. Identify behavioral patterns: Analyze the data from your research (interview transcripts, survey responses). Look for groups of users who behave similarly. Pay attention to their goals, frustrations, and the tools they use.
  3. Create the archetypes: Group users with similar patterns into 2 to 4 main archetypes. These will be your Personas. You don’t need a Persona for every user; look for the most representative groups.
  4. Bring each Persona to life: For each archetype, create a one-page document.
    • Choose a name and a stock photo that fits the archetype.
    • Fill in the sections: biography, goals, frustrations, etc., using real quotes and data from your research.
  5. Share and socialize the Personas: Present the Personas to the entire team and stakeholders. Print them and put them on the wall. Make them visible and part of the daily conversation.

Mentor Tips

  • Quality over quantity: It’s better to have 2 or 3 well-defined, data-based Personas than 10 superficial ones.
  • Focus on goals, not just demographics: The most important thing about a Persona is not their age or city, but what they’re trying to achieve (their goals).
  • Base everything on real data: When writing the biography or frustrations, try to use direct quotes from your interviews. This makes them much more authentic and powerful.
  • Personas are not forever: As your product and user base evolve, your Personas should too. Review and update them periodically.

Resources and Tools

Tags

ux artifact research junior