Ad Hoc Personas: Using Multiple Persona Sets for Smarter Design and Strategy

Understanding Ad Hoc Personas in a Modern Context

Personas have long been used as a powerful tool in user-centered design, helping teams humanize data and align around real user needs. Building on ideas popularized by Don Norman and other pioneers in user experience, ad hoc personas represent a more flexible, context-sensitive approach. Instead of relying on a single, monolithic set of personas, organizations can create multiple persona sets that each serve a specific purpose or decision context.

This shift reflects how complex today’s products, services, and ecosystems have become. A single type of stakeholder can behave very differently depending on context: browsing vs. buying, support vs. advocacy, onboarding vs. expert use, and so on. Ad hoc personas acknowledge this complexity and allow teams to design more precisely for each moment.

What Are Ad Hoc Personas?

Ad hoc personas are lightweight, situationally defined user representations created for a focused goal or scenario rather than for universal, all-encompassing use. They are often faster to produce than full traditional personas, and they are intentionally scoped around a specific decision, project phase, or research question.

Rather than asking, “Who are our users overall?” ad hoc personas ask, “Who are our users for this purpose?” This subtle shift has major implications for product strategy, interaction design, content, and even organizational alignment.

Key Characteristics of Ad Hoc Personas

Why a Business Might Use Two Different Persona Sets for the Same Stakeholder

One of the most powerful ideas in context-driven persona work is that a business might legitimately maintain two different sets of personas for the same general type of stakeholder, each optimized for distinct purposes. At first glance this can feel redundant, but it is often the most accurate representation of reality.

Different Decisions Require Different Views of the Same Person

The same stakeholder can appear in multiple roles, channels, or emotional states when interacting with a business. For example, consider a B2B decision-maker:

Attempting to compress all of these dimensions into a single persona often leads to vague descriptions that are hard to design against. By contrast, separate persona sets let each function in the business see the stakeholder with the level of granularity and context they need.

Examples of Dual Persona Sets in Practice

Here are common scenarios where multiple persona sets for the same stakeholder group are not only useful but necessary:

Ad Hoc Personas vs. Traditional Personas

Traditional personas often aim to be comprehensive, consistent artifacts used across an entire organization for many years. While this can work in stable environments, it can become a constraint when markets, technologies, and user behaviors change quickly.

Limitations of One-Size-Fits-All Personas

Advantages of the Ad Hoc Approach

How to Create Multiple Persona Sets Without Confusion

Using multiple persona sets productively requires discipline. Without structure, teams risk duplication, contradiction, and confusion. With a clear framework, however, multiple persona sets can coexist and reinforce one another.

1. Start from Shared Foundational Research

All persona sets should originate from a shared evidence base: user interviews, field studies, analytics, surveys, support logs, and other research artifacts. This ensures that even when personas diverge by context, they remain grounded in the same underlying reality.

2. Define the Purpose and Scope of Each Persona Set

Before creating or revising personas, explicitly document:

Clear boundaries keep personas from drifting into each other’s territory.

3. Maintain a Meta-Map of Stakeholders

Behind the individual persona sets, maintain a higher-level map of stakeholder types and relationships. This map does not replace personas; instead, it:

4. Use Clear Naming and Versioning

Label persona sets with both audience and purpose, for example:

Descriptive names and version numbers reduce the risk of outdated personas being reused for inappropriate purposes.

5. Institute Lightweight Governance

Appoint a small group or guild responsible for persona hygiene. Their responsibilities can include:

Designing Experiences with Multiple Persona Sets

When multiple persona sets are in play, design teams need clear workflows for how to use them. The goal is to make personas actionable, not just well-documented.

Connecting Personas to User Journeys

Map each persona set to the stages of the user journey they best describe. For example:

This structure prevents teams from misapplying personas to phases of the journey they were never designed to represent.

Using Ad Hoc Personas in Agile and Lean Environments

Ad hoc personas are particularly well suited to agile and lean workflows. They can be created at the start of a sprint to clarify assumptions, then validated or refined as user feedback arrives. Over time, a library of context-specific personas emerges, supported by real-world learning rather than speculation.

Measuring the Impact of Persona Strategy

Persona efforts should be judged not by how beautifully they are documented, but by the outcomes they enable. To assess whether your multiple persona strategy is working, track both qualitative and quantitative indicators.

Qualitative Indicators

Quantitative Indicators

Common Pitfalls When Using Multiple Persona Sets

While the benefits are substantial, multiple persona sets introduce their own risks. Anticipating these pitfalls helps teams avoid confusion.

1. Persona Bloat

Teams may create new personas for every minor variation, leading to an unwieldy library that no one fully understands. To avoid this, enforce a simple rule: a new persona must unlock a distinct decision or reveal a meaningful behavioral difference.

2. Conflicting Narratives

If personas for the same stakeholder are built in isolation, they may contradict one another. Address this by:

3. Treating Ad Hoc Personas as Permanent

Ad hoc personas are meant to be flexible and provisional. When teams cling to them long after their context has changed, they become as stale as poorly maintained traditional personas. Regular review cycles ensure personas stay relevant.

4. Ignoring Edge Cases

Focusing too heavily on a small number of high-value personas can cause organizations to overlook accessible design, inclusivity, and emerging segments. While ad hoc personas are context-specific, they should still encourage teams to ask, “Who is not represented here, and what might we be missing?”

Strategic Benefits of Embracing Ad Hoc Persona Thinking

Beyond design and UX, the ad hoc persona mindset influences how organizations think and operate. It encourages teams to:

Ultimately, the value of ad hoc personas lies in their ability to keep teams close to users while adapting to an ever-changing environment.

Conclusion: Designing for People, Not Just Profiles

Personas, whether traditional or ad hoc, are only proxies for real people. The real goal is not to create perfect persona documents but to enable better decisions and more humane experiences. By maintaining multiple persona sets for the same stakeholder, businesses acknowledge that people are complex, context-dependent, and sometimes contradictory.

Used thoughtfully, this approach leads to sharper focus, richer empathy, and experiences that feel tailored rather than generic. As organizations continue to operate in increasingly intricate ecosystems, ad hoc personas offer a practical, strategic way to stay grounded in what matters most: understanding and serving the people behind the data.

The power of context-specific personas becomes especially clear in hospitality, where hotels serve multiple overlapping stakeholder groups every day. A single guest might appear in one persona set focused on booking behavior—how they search, compare prices, and choose locations—and in another set centered on on-site experiences, such as check-in, room preferences, amenities, and digital services. By modeling these different contexts separately, a hotel can refine its website and reservation flow for one persona set while tailoring in-stay touchpoints, loyalty programs, and service design using another. This dual approach reveals how the same traveler’s needs shift between planning, arrival, and departure, enabling hotels to craft seamless journeys that feel personal at every stage.