Persona
Also: Buyer Persona, User Persona, Customer Persona, Marketing Persona, Persona (FR), Profil type, Buyer Profile
A semi-fictional, research-based representation of your ideal customer: their goals, frustrations, behaviours and decision criteria.
What it is
A persona is a semi-fictional, research-based archetype that represents a distinct segment of your customers, users, or stakeholders. It condenses patterns found across many real people into a single, memorable profile: a named character with goals, frustrations, behaviours, and decision criteria. A persona is not a demographic bucket and not a guess. It is built from evidence (interviews, surveys, analytics, support logs, sales calls) and kept deliberately concrete so teams can reason about a real human instead of an abstract "average user."
A persona typically includes:
- Context: role, environment, level of expertise
- Goals: what success looks like for this person
- Pain points: obstacles and frustrations they want removed
- Behaviours: how they research, buy, and use products
- Decision criteria: what tips them toward yes or no
- Watering holes: channels and sources they trust
Why it matters
Personas create a shared reference point across teams. When product, marketing, and sales all picture the same customer, decisions get faster and more consistent. Personas force explicit assumptions into the open, where they can be tested and corrected. They also help prioritise: features, messages, and offers can be scored against whether they serve a priority persona.
The main risk is fiction dressed as fact. A persona invented in a workshop without data will mislead. Good personas cite their evidence and are revisited as the market shifts.
How it is used in practice
- Marketing: shapes messaging, channel choice, and content themes.
- Product: prioritises features against real goals and pains.
- Sales: anticipates objections and tailors discovery questions.
- AI systems: guides prompt design, tone, and evaluation criteria for assistants and agents.
Teams usually maintain three to five active personas. More than that dilutes focus.
Worked example
"Compliance-first Clara," Head of Risk at a mid-size bank.
- Goal: adopt an AI tool without creating audit exposure.
- Frustration: vendors overstate accuracy and hide data handling.
- Behaviour: reads documentation before any demo, involves legal early.
- Decision criteria: data residency, explainability, human-in-the-loop controls.
Given Clara, a vendor would lead with a security whitepaper rather than a flashy feature tour, and route her to a solutions engineer, not a generic SDR. The same persona would tell an AI product team to expose confidence scores and citation trails by default.
See also
Frequently asked questions
What is a persona in marketing and product work?
A persona is a semi-fictional, research-based archetype representing a distinct segment of your customers or users. It condenses patterns observed across many real people into one named profile with goals, frustrations, behaviours and decision criteria. It is built from evidence such as interviews, surveys, analytics, support logs and sales calls, not from assumptions.
What is the difference between a persona and a customer segment?
A segment is a group defined by shared attributes such as industry, company size or age; a persona is a concrete individual profile that explains why that group behaves as it does. A persona is not a demographic bucket: it adds goals, pain points, decision criteria and the channels the person trusts. Segments help you size a market, personas help teams decide what to build and what to say.
How many personas should a team maintain?
Three to five active personas is the usual working range. Beyond that, focus dilutes and the personas stop being a shared reference point because nobody remembers them all. If you feel the need for more, it usually signals that some personas overlap and should be merged.
What should a persona actually contain?
Six blocks: context (role, environment, level of expertise), goals (what success looks like), pain points, behaviours (how the person researches, buys and uses products), decision criteria (what tips them toward yes or no), and watering holes (the channels and sources they trust). Each element should be traceable to evidence. A persona without cited sources is fiction dressed as fact and will mislead the teams that rely on it.
How do personas change the way an AI product is designed?
They guide prompt design, tone and the evaluation criteria used for assistants and agents. Take "Compliance-first Clara," a Head of Risk at a mid-size bank whose decision criteria are data residency, explainability and human-in-the-loop controls: that persona pushes the product team to expose confidence scores and citation trails by default. The same profile changes go-to-market too, leading with a security whitepaper rather than a feature tour and routing her to a solutions engineer instead of a generic SDR.