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×EnvironmentA specific setup where software runs, such as development, staging, or production.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 aspect requires compromising another.Open glossary term→ need to be made. So the persona sits there — technically correct, but practically useless.

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×ContextThe surrounding conditions that shape behaviour and decisions.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 aspect requires compromising another.Open glossary term→ became clearer because they were grounded in something tangible. That's when personas start to do their job.

Another patternglossary×PatternA reusable solution to a common design problem.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.

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 aspect requires compromising another.Open glossary term→. But without that clarity, personas don't drive decisions. They just sit alongside them.