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

Then they quietly disappear.

I’ve seen this happen 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 flowglossary×DelightMoments that exceed user expectations.Open glossary term→, or how to structure a journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→, 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.

I’ve worked on projects where personas were beautifully put together. Designed well, written well, clearly based on real researchservice×User ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service→. You could tell effort had gone into them.

But when you listened to the conversations happening in the team, they never came up.

Decisions were still being made based on opinion, internal priorities, or whatever felt like the safest option at the time.

The personas existed, but they weren’t doing anything.

That’s usually the turning point.

Because personas only have value if they influence behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→.

In my experience, the difference between personas that fail and personas that actually work comes down to one thing.

Whether they help you make decisions.

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 journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→.

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.

Suddenly, conversations changed.

Instead of what do we think works best, it became which of these users are we designing for here?

Instead of trying to satisfy everyone, 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.

That’s where they lose all their value.

When personas work, they’re part of the day-to-day.

They show up in conversations.

They get referenced in design critiques.

They’re 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 try and 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.

In reality, it’s far more effective to be deliberate.

Not every persona needs to be catered for in every journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→. Not every decision needs to satisfy every user type. The value comes from being clear about who you’re prioritising and why.

That’s often where teams struggle.

Because it forces trade-offsglossary×Trade-offsTrade-offs are decisions where improving one aspect requires compromising another.Open glossary term→.

It’s much easier to create something that tries to work for everyone than it is to make a call and say, this is designed for this type of user, and others may need to adapt.

But without that clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→, personas don’t drive decisions. They just sit alongside them.

So when personas fail, it’s rarely because the idea is wrong.

It’s because they’ve been positioned incorrectly.

They’re not there to describe users in a general sense.

They’re there to guide choices.

If a persona doesn’t help you decide what to prioritise, what to simplify, what to remove, or where to focus, then it’s not doing its job.

But when they’re built around behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→, kept simple, and actually used in the work, they become one of the most effective tools a team can have.

Not because they tell you everything about your users.

But because they help you stay focused on what actually matters when you’re designing for them.