What Happens When You Remove Personas From Journey Work

Personas are a fixture of service design. Every practitioner has built them, every client has received them, and most organizations have a folder somewhere containing personas that the team looked at twice before the project closed and never touched again.

Removing them from journey work sounds radical. In practice, it tends to produce cleaner, more durable, more inclusive maps — and significantly fewer political headaches.

How Personas Break Down Over Time

The original purpose of a persona is empathy. It gives teams a human face to design for, a story to hold in mind when making decisions about a product or experience. For that narrow purpose, in a specific moment — usually just before a workshop where participants need an emotional anchor — personas can be genuinely useful.

The problem is what happens after that moment. Personas stay. They get printed, displayed, shared across teams, and gradually fossilized into something the original research never supported.

The archetype becomes a caricature. A persona representing users with lower digital proficiency becomes "the one who doesn't get it." A persona representing a specific age demographic starts carrying assumptions about behavior that the data never contained. Once a persona has a name and a face, it accumulates meaning that diverges from the evidence — and teams start designing for the persona rather than for the actual range of people the persona was meant to approximate.

"I once worked on a project where a persona representing lower digital proficiency was a middle-aged woman. She was meant as an archetype, but she gradually became 'the one who doesn't get it.' The stereotype stuck."

What Jobs-to-Be-Done Does Instead

The alternative is not to eliminate empathy from journey work. It is to anchor empathy in behavior rather than identity.

Jobs-to-Be-Done asks a different question than personas do. Instead of "who is this person?", it asks "what is this person trying to accomplish?" The shift is significant. Intent is more durable than demographic. It does not assume anything about age, gender, education, or cultural background unless the job itself requires those distinctions.

In B2B contexts, the same job — "validate that this solution meets our compliance requirements" — might be performed by a legal counsel, a procurement officer, or a technology architect. Designing for the job rather than the title means the solution works across all three.

In B2C contexts, the principle that good services work for everyone (as Lou Downe articulates in Good Services) applies directly. You do not design a special experience for "less experienced users." You design an experience clear enough that no one gets lost.

Hashtags as a Practical Replacement

In practice, the replacement for persona lanes is simple: tags.

Each insight on the journey map gets tagged with the relevant job or role. "I look for discounts during peak shopping periods" gets #holiday-shopper. "I need updated product assets for the campaign" gets #marketing. "I worry about invoice accuracy" gets #finance.

This approach keeps the map unified rather than fragmented across multiple persona-specific versions. It preserves role visibility — you can still see which jobs cluster where — without locking insights into fictional character profiles that drift from reality over time.

The map stays inclusive, dimensionally clear, and free of narrative clutter. Teams can filter by tag when they need to focus on a specific group. They do not have to maintain multiple parallel maps or reconcile contradictions between personas that were never meant to coexist.

When to Use Personas (Briefly)

There is one legitimate use case for personas in journey work: as a storytelling device immediately before a workshop where participants need to inhabit the user's perspective for ideation purposes.

In that context, a persona is a temporary lens — a way to make behavioral data feel human before a creative session. It should be introduced at the start of the workshop and set aside at the end. It is not a deliverable, not a document, and not a long-term reference tool.

Outside that moment, let Jobs-to-Be-Done run the map. The insights will be more accurate, the decisions will be better grounded, and the team will avoid spending two months maintaining a set of fictional characters that increasingly serve as a distraction from the actual work.