Persona (user persona)

"Margarita, 34, a marketer, is looking for a survey tool - it matters that she can set it up quickly and export to Excel" - this is a persona. A fictional but realistic image of a typical member of the target audience

Personas help the team understand who the product is for, what language to use, and where to find customers. On the customer journey map (CJM) each stage has its own persona: who makes the decision, who influences it, who uses the product. They are built from interviews, surveys, and analytics. In SurveyNinja you can run a survey to collect data about customers and build personas - try the customer profile template.

A persona is not statistics. It is a living image: name, age, job title, pains, goals, channels, a quote. It simplifies decision-making: "How would Margarita react to this copy?"

Definition

Persona - a generalized image of a typical member of an audience segment. It includes demographic characteristics, motivations, goals, pains, behavior, and channel preferences. It is used in marketing, product, and UX to keep decisions focused on real users. Personas are built from qualitative and quantitative research. Link to segmentation: one segment - one or several personas. On the CJM, personas are tied to the stages of the journey.

In short: "the typical customer with a face" - so that instead of an abstract "audience aged 25-40" you have a specific person with a name and a story.

Why personas matter

A shared language across the team - everyone understands who they are building for. Focus on the user - decisions are checked against "does this suit Margarita?". Content and copywriting - tone, channels, and arguments tailored to the persona. Prioritization - what matters more for the key persona. CJM and touchpoints - different personas follow different journeys. Recruiting respondents - whom to invite to interviews and surveys.

Persona vs target audience

The target audience is a broad group: "women aged 25-45, mid income". A persona is a specific version: "Anna, 32, project manager, looking for a work-life balance, values her time, buys online". The audience defines reach, the persona defines depth of understanding. You need both: the audience for targeting and sampling, the persona for content and product.

Types of personas

Buyer persona - the one who makes the purchase decision. Job title, budget, selection criteria, objections. For B2B the initiator, the influencer, the decision-maker, and the user can be different personas.

User persona - the one who directly uses the product. Tasks, scenarios, level of expertise, pain points while using it.

Negative persona - who is not our customer. Helps avoid spending resources on a non-target audience.

One product typically has 2-5 personas. More than that scatters focus. Fewer risks missing an important segment.

What to include in a persona

Name, age, job title. Goals and motivations - what they want to achieve. Pains and fears - what gets in the way, what they avoid. Behavior - how they look for information, where they spend time, how they make decisions. Demographics - as needed (city, income, if relevant). A quote - one phrase in the persona's voice. Channels - where they come from, where they look.

Don't overload it. 1-2 pages per persona is enough. Extra details go unused.

How to build a persona

Interviews. 5-15 in-depth interviews with customers or prospects. Open-ended questions: "Tell me how you look for a solution?", "What matters to you when choosing?". In-depth interviews and focus groups provide quotes and motivations.

Surveys. Quantitative data: demographics, preferences, purchase frequency, channels. Segment the responses - identify clusters. A survey complements interviews: interviews answer "why", surveys answer "how many of them".

Analytics and CRM. On-site behavior, purchase history, support data. Who buys what, where they come from, how they behave.

CustDev. Customer Development - conversations with customers during product development. Helps test hypotheses and refine personas.

Bring the data together: look for recurring patterns. Groups with shared characteristics are persona candidates. A single real person rarely matches a persona perfectly - a persona is an archetype. A synthesis, not a copy.

Personas and CJM

On the customer journey map personas come first: who the journey is being built for. A single stage can involve different personas: at the "consideration" stage the initiator does the research while the decision-maker approves the budget. Personas shape touchpoints: a young audience - TikTok and messengers, B2B - LinkedIn and email. Segment your stage-by-stage surveys by persona - hidden variables carry the segment.

In SurveyNinja: surveys for personas

Create a survey with questions about demographics, goals, channels, and selection criteria. Send it to customers or to a respondent panel. In the reports - cross-tabulation, segmentation. You identify clusters and shape them into personas. The customer profile template and the brand awareness research template are ready-made starting points.

Common mistakes

Making it up. A persona without research is a stereotype. Use real data - interviews, surveys, analytics.

Too many personas. 10 personas and no one will remember them. Focus on 2-4 key ones.

Not updating them. The audience changes. Once every year or two, check your personas against new data.

Copying someone else's personas. A "young mom aged 28" from a textbook is not your audience. Your own interviews, your own data.

A persona with no application. Created and filed away in a drawer. Personas should take part in discussions, briefings, and prioritization.

Too generic a quote. "I want a quality product" is not informative. Better: "I have no time to dig into the settings - I need a result within an hour". Specifics help.

Case study: a persona for SaaS

A survey service. They ran 20 customer interviews and a survey of 200 respondents. They identified 3 personas: an in-house marketer (needs simplicity, integrations), an agency (multi-user access, white label), a researcher (complex logic, export). Previously every feature was built "for everyone". After the personas - priority went to features for the marketer (60% of revenue). Sign-up conversion grew by 25%. One persona doesn't mean one segment, but the focus helped.

Second case study: e-commerce

An online clothing store. Before personas - newsletters sent "to everyone", a single message. A survey plus CRM data revealed two clusters - the "impulsive buyer" (comes in for promotions, quick decisions, mobile) and the "planner" (compares, reads reviews, orders less often but spends more). They created two personas. They split the newsletters: for the first - urgency, discounts, mobile design; for the second - comparisons, reviews, expertise. Conversion from the newsletter grew by 18%. Different personas - a different customer experience.

Link to segmentation

Segmentation is dividing the audience by attributes (behavior, demographics, LTV). A persona is the human face of a segment. The segment "customers with an LTV above 50,000" is an abstraction. The persona "Alexey, owner of a small company, buys regularly, values a personal approach" is clearer. Segmentation tells you whom to target, the persona tells you how to talk to them.

Questions for interviews and surveys

When building a persona: "Describe a typical day", "How do you find out about new products?", "What matters when choosing?", "What objections come up?", "Who do you consult before buying?". For B2B: "How does the approval process work?", "Who makes the decision?", "What is the budget?". Open-ended questions - for interviews. Closed-ended ones and scales - for surveys. The collected responses are coded, patterns are found, and personas are formulated.

When personas are not essential

A narrow B2B with 5-10 key customers - you know them by name. A very early-stage startup - hypotheses, not a persona. A one-off project with no repeats - it won't pay off. In all other cases personas pay back the time spent building them: fewer misses, clearer decisions, faster alignment within the team.

A persona is a customer or user archetype. It is built from research and used in CJM, marketing, and product. In SurveyNinja - surveys to collect data for personas.