A useful alignment tool when built from research. A dangerous one when built from assumptions.

A persona is a fictional character built from patterns observed across real users. It describes who someone is, what they're trying to accomplish, what frustrates them, and how they make decisions. The goal is to give the product team a consistent human reference point when making design choices — so that "what would the user want here?" has a more grounded answer than collective gut feel.

The key distinction is research-based versus assumption-based. Personas derived from Usability Testing, interviews, and behavioral data serve a real function. Personas derived from internal assumptions about who the user "probably" is serve mostly to reflect the team's existing biases back at them.

Most personas fail because they're demographic profiles, not behavioral ones. A persona that tells you a user is "35-45, college-educated, tech-savvy" doesn't help make a single design decision. What matters is context, goals, and friction — not age brackets.

They also fail when they're created once, presented in a workshop, and never referenced again. A persona that lives in a slide deck and gets cited vaguely in kickoff meetings isn't influencing decisions. It's decoration. Personas need to be embedded in the team's working process — referenced in design reviews, in sprint planning, in the framing of research questions — or they stop being useful almost immediately.

The details that move design decisions:

• Primary goal: What is this person trying to achieve? In their words, not product team vocabulary.
• Context of use: Where and how do they use the product? Time pressure? Multiple monitors? Mobile or desktop?
• Pain points: What slows them down, confuses them, or makes them distrust the product?
• Decision-making style: Do they read everything or scan? Do they explore or follow a linear path?
• What success looks like for them — not for the business, for the user.

Include direct quotes from real research sessions. Nothing grounds a team faster than a verbatim quote from an actual user.

A proto-persona is a hypothesis-based persona — created quickly from team knowledge and assumptions before real research is complete. It's not a research artifact; it's a starting point for alignment.

Used honestly, proto-personas are a practical tool at the start of a project when you don't have time for full research but need some shared model of the user. The risk is treating them as validated when they're not — using them to justify design decisions that should still be tested. A proto-persona is a placeholder. Label it as one.

The most common misuse is creating personas for stakeholders rather than for design decisions. A beautifully formatted persona document may satisfy a stakeholder request for "user research" while doing nothing to inform the actual work.

Personas also get misused as a substitute for ongoing research. "What would Maya think?" is a useful gut-check heuristic. It's not a replacement for watching real users attempt a task. When a team stops doing research because they have personas, they've turned a research tool into a reason to skip research.

For teams trying to build genuine user understanding, UX Research ties persona development directly to ongoing research — so the personas stay current rather than gradually drifting from reality.