User Personas / Archetypes

discoverymediumBeginner

TL;DR

Representations of your users based on real research that guide design decisions.

What is it

User Personas are semi-fictional representations of your ideal users, created from real research data. Unlike 'proto-personas' based on assumptions, UX personas are built with qualitative and quantitative data obtained from interviews, surveys, and direct observation.

They include information about behaviors, needs, frustrations, motivations, usage context, and user goals. They are a communication tool that humanizes research data.

What it is for

✓Align the team on who the real user is
✓Make design decisions based on real needs
✓Prioritize features based on impact on each user type
✓Communicate research findings in an accessible way

Research methods that feed it

In-depth interviewsLarge-scale surveysEthnographic researchUsage data analysisCard Sorting (for mental architecture)

When to use it

✓When starting a new project with no user knowledge
✓When the team has unvalidated assumptions
✓For redesigns where the user has changed
✓When stakeholders make decisions based on intuition

When NOT to use it

✗If you already have validated, current personas (< 12 months old)
✗If your product has a single, very homogeneous user type
✗When you need immediate usability results (use tests first)

How to create it step by step

1Research first: Conduct 8-15 in-depth interviews with real users. Complement with quantitative data from surveys or analytics.
2Identify patterns: Group users by similar behaviors, not demographics. Look for 3-5 distinct behavior patterns.
3Define key attributes: For each group, document: fictional name, representative photo, characteristic quote, main needs, frustrations, goals, usage context.
4Prioritize personas: Classify as primary (main user), secondary (frequent user), and tertiary (occasional user). Maximum 3-4 personas.
5Validate with data: Cross-reference your personas with quantitative data to verify segments exist in the expected proportion.
6Present to the team: Create a 1-page visual card per persona. Include concrete usage scenarios.

Tips for small teams

Start with 'proto-personas' based on what you know and validate with 5-8 interviews
One well-researched persona is better than 5 superficial ones
Use existing templates (Miro, Figma) to save time
Post persona cards in a visible place for the team

Common mistakes

✗Creating personas based only on assumptions without research
✗Including too many irrelevant demographic data
✗Creating more than 4 personas (choice paralysis)
✗Not updating personas when users change
✗Confusing market segments with UX personas

Contextualized example

Context: A sustainable fashion e-commerce platform in Chile needs to understand its buyers.

Primary persona — 'Valentina, the conscious shopper': 28 years old, graphic designer in Santiago. Shops online 2-3 times a month. Researches brands before buying. Main frustration: can't verify fabric quality online. Needs: detailed photos, accurate size guide, material and origin information.

Secondary persona — 'Carlos, the quick gift buyer': 35 years old, engineer. Buys sporadically as gifts. Doesn't know sustainable brands. Needs: price filters, gift guide, express shipping.

Phase

discovery

Audience

product-teamstakeholdersmultidisciplinary

Complexity

medium

Experience level

Beginner

Related deliverables

Related methodologies

Free tool by UXR — UX Research Consulting in Chile