Why most personas fail (and how to make them useful)

I've seen this across all kinds of organisations, from smaller teams trying to formalise their processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ to large, complex environmentsglossary×EnvironmentAn environment is a specific configured setup where software runs, such as development, staging, or production, each with its own data and settings. Keeping them consistent is what makes behaviour in one predict behaviour in another.Open glossary term→ where entire sets of personas exist but rarely influence a single decision. Not because personas are inherently flawed, but because of how they're created and, more importantly, how they're used.

The most common issue is that personas become descriptive instead of functional. They tell you who the user is in a general sense: their age, their job, their preferences, sometimes even what they do in their spare time. It all feels rich, detailed, well thought through. But when it comes to actually making a decision, none of that helps. Knowing that someone is time-poor or values convenience doesn't tell you what to do with a checkout flow, or how to structure a journey, or what to prioritise when trade-offsglossary×Trade-offsTrade-offs are decisions where improving one thing requires giving up another, such as speed against quality or scope against cost. Every product decision involves them, whether or not they are made explicit.Open glossary term→ need to be made. So the persona sits there, technically correct, but practically useless.

The demographic detail also invites the wrong kind of confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→. A photograph, a name and an age make a persona feel like a person, and a fictional person is far easier to make assumptions about than a real patternglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→ of behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→. Richness and accuracy pull against each other here.

On projects where personas have been genuinely useful, they've been far simpler than people expect. Less about who the user is, more about how they behave in the contextglossary×ContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term→ of the product. What are they trying to achieve? What constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ are they operating under? What causes hesitation? What gives them confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→? Those are the things that actually shape a journey.

I remember working through a set of personas where we stripped almost everything back: removed the unnecessary detail, got rid of anything that didn't directly relate to behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→, and focused purely on how different types of users approached the same task. The shift was immediate. Instead of what do we think works best, conversations became which of these users are we designing for here? Decisions became more intentional, more focused. Trade-offsglossary×Trade-offsTrade-offs are decisions where improving one thing requires giving up another, such as speed against quality or scope against cost. Every product decision involves them, whether or not they are made explicit.Open glossary term→ became clearer because they were grounded in something tangible. That's when personas start to do their job.

The test is whether two of them ever disagree. If every persona would want the same thing from a given screen, the set is not doing any work, because it cannot help anybody choose. Useful personas are the ones that put a genuine trade-off in front of the team.

Another patternglossary×PatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term→ I've seen is personas being treated as a deliverable rather than a tool. They get created, presented, signed off, and then effectively archived, something to reference if needed, but not something that actively shapes the work. When personas work, they're part of the day-to-day. They show up in conversations, get referenced in design critiques, are used to challenge decisions. They become a shared language across the team, not just a document that lives somewhere in a folder.

Keeping them current matters as much as keeping them short. A persona built from researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→ two years ago describes a product and an audience that have both moved, and a stale one is worse than none because it carries the authority of having been agreed.

The signal that they have become live tools rather than documents is when somebody argues with one. Being challenged in a design review means it is influencing a decision, which is more than most persona sets ever achieve.

There's also a tendency to make personas cover everything: every edge caseglossary×Edge CaseAn edge case is a rare or extreme scenario that falls outside typical user behaviour.Open glossary term→, every scenario, every possible variation of user behaviourglossary×User BehaviourUser behaviour refers to how users interact with a product, including actions, patterns, and decision-making processes.Open glossary term→. The result is usually a set of personas that are too broad to be useful. They become vague by design, trying to represent everyone and ending up guiding no one. It's far more effective to be deliberate. Not every persona needs to be catered for in every journey. Not every decision needs to satisfy every user type. The value comes from being clear about who you're prioritising and why. That forces trade-offsglossary×Trade-offsTrade-offs are decisions where improving one thing requires giving up another, such as speed against quality or scope against cost. Every product decision involves them, whether or not they are made explicit.Open glossary term→. But without that clarity, personas don't drive decisions. They just sit alongside them.

Naming who you are not designing for is the part that gets skipped, and it does most of the work. It is uncomfortable in exactly the way strategic constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ are uncomfortable, and it is what turns a set of descriptions into something capable of settling an argument.