Persona

What is a Persona?

A persona (also called a user persona or buyer persona) is a semi-fictional representation of a key user or customer segment, built from research and real data. Personas are used in product design, marketing, and onboarding to ground decisions in the needs, behaviours, goals, and frustrations of specific types of users — rather than a hypothetical average user who represents no one in particular.

A well-constructed persona typically includes: a name and role, a primary goal, key frustrations, success criteria, technical comfort level, and how the product fits into their existing workflow.

How to Build Personas That Actually Work

The single biggest mistake in persona creation is building them from internal assumptions. Here's the research-first approach:

1. Interview real users. 8–12 interviews per segment is typically enough to identify patterns. Ask about goals, current workflow, frustrations, and how they evaluate success — not about your product.
2. Analyse behavioural data. What do your highest-retained users have in common? Company size, role, use case? Segment your retention cohorts and look for clusters.
3. Validate with surveys. Once you've identified candidate persona profiles from qualitative research, use a survey to your broader user base to validate frequency and priority.
4. Build the fewest personas that explain most of your users. If you have 7 personas, you have a taxonomy, not a decision tool. Two to three primary personas is the maximum that a product team can genuinely hold in mind.

Personas in Onboarding Design

Personas are most actionable when applied to onboarding. Different user types need fundamentally different first-hour experiences:

• A technical founder evaluating your API integration has different questions than a non-technical marketing manager using your visual interface
• A solo user needs to experience personal value immediately; a team lead needs to see collaboration features early
• A user migrating from a competitor needs a translation layer; a first-time tool user needs foundational concepts

Personalised onboarding flows — triggered by a simple signup question about role or goal — can dramatically increase activation rates by serving each persona the path most relevant to them.

When Personas Fail

Personas fail when they're:

• Too broad to be useful — "Sarah, 35, a professional who uses technology" tells you nothing
• Built once and never updated — your users at 100 customers may look completely different from your users at 10,000
• Not connected to product decisions — a persona that lives in a Confluence doc and is never referenced in sprint planning is a document, not a tool
• Demographically focused instead of behaviourally focused — what matters is what users are trying to accomplish, not their age and job title