Persona variants: one persona, many customer segments

Picture a persona called System Lead — the person responsible for getting your product live and keeping it running. Now ask: is that person the same at a Big Bank as at a fast-moving FinTech?

Not even close. Same role, very different reality:

• At a Big Bank, the System Lead works inside tight approval chains, with more oversight roles and a lower tolerance for risk.
• At a FinTech, the same role has broad autonomy, moves fast, and expects to self-serve.

So what do you do — write two personas? Five? One for every segment?

The duplication trap

Spinning up a near-identical persona per segment feels tidy at first. Then it rots:

• The copies drift. A change made to one isn’t made to the others.
• Nobody’s sure which is canonical.
• Comparison becomes meaningless because you’re comparing slightly-different clones.

You end up with more personas and less clarity.

A better model: variants

A variant keeps one base persona and records only what changes for a given customer type:

• Overridden values for the fields that differ (decision authority, pain points, technical profile…).
• “What changes” notes that explain the difference in plain language.

The base persona is the common thread; variants are the deltas. One source of truth, with the nuance made explicit instead of buried.

Why it pays off

• You can compare a persona against its own variants to see exactly how a role shifts across segments.
• Sales and pre-sales walk into an account already knowing how this customer type differs.
• Implementation teams can pair a variant with a Launchpad to tailor the setup.

One persona. Many contexts. No clones.

Learn how variants work in the docs.