Accessibilità digitale nel 2026
Download the then accessibility guide

Personas: designing with people at the center

Summary

They are not made-up characters to fill a slide. They are profiles built on interviews, observation and behavioral data.

They give a face to the numbers, create empathy inside the team and above all get everyone to agree on who they are designing for.

The difference between user personas and buyer personas, which answer different questions, and the five steps to build them. Starting with segmentation, which should be based on behavior and not on age.

Contents

Understanding people is the key to designing experiences that work. When we talk about UX, CX or EX, creating personas is not a creative exercise but a structured, data-based practice, designed to generate empathy, design consistency and business value.

What Personas are (and why they are not an invention)

Personas are semi-fictional representations of real users. They are not stereotypes but profiles built from ethnographic research, interviews, behavioral analysis and quantitative data. Their goal is to help teams design experiences centered on the people who will live them.

As Nielsen Norman Group points out, Personas improve a team’s ability to focus on user goals and design more effective solutions.

What Personas are for

They humanize data

The data collected from interviews or usability tests is often hard to internalize. Personas make this information more accessible by building concise, engaging stories.

They foster empathy

A well-built persona lets the team step into the user’s shoes and understand context, emotions and expectations. Empathy is not a “nice to have”, but a strategic requirement for the quality of the experience.

They make alignment easier

Personas become a shared reference across design, marketing, development and stakeholders. They help make consistent decisions, keeping a common language and an aligned vision.

They increase ROI

According to Qualtrics, adopting strategies based on realistic user insights significantly improves customer retention and satisfaction.

The two big categories: User Personas and Buyer Personas

User Personas

They represent who uses the product or service. They are fundamental in UX design because they describe users’ real behaviors, context of use, difficulties and goals.

Buyer Personas

They are the purchase decision makers. In many cases they are not the same as the end users. For example: a mother buys an educational app (buyer), but it is the child who uses it (user). Or, in a company, the CTO approves the purchase of software that is then used every day by the development team.

Why differentiate

Buyers and users have different expectations, needs and barriers. Ignoring this distinction leads to mistakes in positioning, tone of voice or features. A complete human-centered strategy takes both into account.

How to build solid personas in 5 steps

1. Research: the heart of personas

Personas must come from research. Useful sources:

  • Qualitative interviews with real users
  • Ethnographic observation and shadowing
  • Quantitative surveys to validate patterns
  • Analysis of behavioral data (Google Analytics, Hotjar, etc.)
  • Internal sources (customer care, NPS, reviews)

Medallia stresses the importance of Voice of the Customer to capture authentic expectations and frustrations (source: https://www.medallia.com/resource/how-to-build-personas/).

2. Segmentation: find behaviors, not ages

Avoid segmentation based on demographic data alone. Focus on:

  • Usage behaviors
  • Motivations
  • Pain points
  • Decision-making context

Effective segmentation produces consistent archetypes that are distinct from one another and represent meaningful clusters of real users.

3. Synthesis: build the narrative

Each persona should include:

  • A fictional name (e.g. “Giulia, the multitasking organizer”)
  • A realistic or illustrative photo
  • Age and profession (only if relevant)
  • Goals (expressed in the first person)
  • Frustrations and obstacles
  • Main touchpoints
  • Technology habits
  • Typical quotes

4. Validation: avoid bias

Personas should be validated with:

  • Real users (follow-up interviews)
  • Internal teams (to ensure consistency with existing insights)
  • Stakeholders (to align vision and expectations)

Validation is meant to avoid the risk of “inventing” personas tailored to confirm preconceptions.

5. Activation: really use them

Personas must live in projects. Some good practices:

  • Display them during design workshops or sprints
  • Include them in project briefs and user journeys
  • Use them to prioritize features
  • Adapt them for marketing copy and email automation
  • Keep them as “living” documents to update every 6-12 months

The impact of personas on UX, CX and EX

User Experience (UX)

Personas help design interfaces that are intuitive, personalized and consistent. Understanding the user’s behavior and context makes it possible to avoid frustration, abandonment and costly redesign cycles.

Customer Experience (CX)

CX personas cover the entire relationship cycle between customer and brand. They guide the creation of consistent, empathetic and personalized touchpoints across all channels, from the website to after-sales support.

Employee Experience (EX)

Employees also have journeys, needs and expectations. Building personas for internal profiles helps improve onboarding, internal tools, communication and organizational well-being. As Deloitte highlights, a positive employee experience directly affects engagement and performance.

Well-made personas: how to recognize them

A good persona:

  • Is based on real research
  • Has a clear, specific goal
  • Is not a caricature
  • Describes a behavior, not just an identity
  • Includes realistic quotes and data
  • Connects to concrete strategic decisions

Mistakes to avoid

  • Inventing profiles from scratch: without data, they are not personas.
  • Using too many personas: the risk is decision paralysis.
  • Not updating them: behaviors evolve, and so should personas.
  • Isolating them: they must be linked to journey maps, tests, roadmaps and metrics.
  • Not involving the team: a persona is useless if it is not understood and adopted by the working group.

Conclusions

Building Personas means taking a concrete step toward putting the user at the center. They are not the answer to everything, but a lens for looking at decisions through the eyes of the people who will use (or buy) the product. When well built, they improve design, conversions, loyalty and internal alignment.

At Then we consider creating Personas one of the key tools for ensuring authentic, measurable and sustainable experiences. From UX Design to a good EX strategy, every project starts by putting people at the center.

Sources:
User Journey Map
User Personas
Customer Experience Management
Personas
ROI
Segmentation
User Experience
Buyer Personas

A senior expert inside your team, starting next week.

Thirty minutes to understand the goal, then we propose the right person from the network.

Related articles
Research

UX metrics: how to measure User Experience

Which metrics really matter and how to link them to design and business decisions.
Research

Research Ops: what it is and why it is essential today

How to make user research scalable, shared and truly useful for decisions.
Research

User research: how to truly understand users and needs?

Qualitative and quantitative research together: how to turn insights into design decisions.

Find out if we can help.

Request a free call to talk about your project.