Persona
Also known as: user persona, buyer persona, customer persona
What Is a Persona?
A persona is a research-based profile that represents a distinct segment of real users. It synthesizes behavioral patterns, goals, frustrations, and context into a named character that design and product teams can reference throughout a project.
Personas built from user research, then used to keep design decisions anchored to the people a product is meant to serve.
How Is a Persona Built?
The process starts with research: interviews, surveys, usability sessions, and behavioral analytics. Across that data, certain patterns emerge — users who share similar goals, workflows, or pain points, even if their demographics differ.
Those patterns are grouped into distinct segments. Each segment becomes a persona: given a name, a role, and a set of goals and frustrations that reflect what the research showed.
A B2B product might produce three or four — a power user who lives in the product daily, a manager who checks in weekly, and an occasional user who only needs one specific workflow.
What Are the Benefits?
Shared reference point — teams across design, product, and development can align around who they're building for, without re-litigating user assumptions at every decision.
Prioritization anchor — when features compete for attention, personas help evaluate which ones serve the most important user segments.
Onboarding tool — new team members and stakeholders can get up to speed on user needs quickly without sitting through full research readouts.
Reduced assumption risk — decisions are tested against a documented user profile rather than an internal guess about what users want.
What Are the Limitations?
Research-dependent accuracy — a persona built from limited or biased data will reflect those limitations directly in the decisions it informs.
Shelf life — user needs shift. A persona created two years ago may no longer reflect how people actually use a product today.
Over-rigidity — treated as fixed rules rather than flexible references, personas can start to constrain thinking rather than support it.
When Does a Persona Add the Most Value?
A persona is most useful at the start of a project, when teams are making decisions about scope, features, and priorities. It's also valuable mid-project when design direction needs re-evaluating, and during redesigns when teams need to re-anchor in user needs rather than inherited assumptions.
Persona building sits at the core of product strategy — the point in any engagement where knowing who the product serves shapes every design decision that follows.