Personas

A persona is a research-based representation of a recurring customer or user pattern. It gives a team a concrete person to design or communicate for while preserving the evidence behind a broader segment. Used well, personas focus expensive marketing, sales and product effort. Used poorly, they turn assumptions and stereotypes into persuasive-looking fiction.

Personas are most valuable when broad segmentation is too abstract for day-to-day decisions. The aim is not to pretend that every person in a segment is identical. It is to make relevant goals, behaviours, constraints and decision roles memorable enough to guide a specific choice. Personas may represent buyers, users, influencers or people for whom an offer is deliberately unsuitable; any “negative” persona should be based on legitimate fit, not protected characteristics or exclusionary profiling.

When to use it

• To focus marketing messages, product decisions, service design and customer journeys.
• To translate qualitative and quantitative research into a shared working representation.
• To distinguish the needs of buyers, users, influencers and other participants in a decision.
• To apply the model in the business situations described here.

Origins

The word persona has roots in theatre and was used in early 20th-century Jungian psychology to describe the social face an individual presents. The modern design method is different. During the 1980s, American software designer Alan Cooper began using specific, goal-oriented user archetypes to guide product decisions. In the 1990s, interaction design and advertising popularised fictional “day in the life” characters representing researched user or customer groups. Marketing later adapted the approach into buyer personas.

What it is

Begin with the decision the persona must support. What is being designed or sold, and which behaviour, need or obstacle matters? Then map the decision-making unit:

• How is the purchase or adoption decision made?

• Which people participate?

• When does each participant become involved?

• What evidence or reassurance does each person need?

• Who decides, influences, uses, approves or blocks?

Select the smallest set of distinct patterns needed for the decision. One persona may be enough when goals and behaviour are consistent; two or three may be required when key participants differ materially. A name, role and representative image can make the pattern memorable, but these fictional details must not outweigh the evidence.

Capture relevant goals, tasks, behaviours, contexts, barriers, values, fears, information needs and decision criteria. Include demographics only when research shows that they affect the behaviour in question. A breakfast-cereal persona will require different evidence from an industrial-raw-materials buyer.

Use several sources and document their limitations:

• Market research: reports, interviews, focus groups and surveys can reveal recurring needs and decision structures. Do not infer personal detail that the evidence does not support.

• Sales and service teams: customer-facing employees hold valuable observations, but their memories may overrepresent recent, vocal or successful customers.

• Internet research: public material can illuminate professional context and language. Do not treat a generic image search as evidence of what a group “looks like.”

• LinkedIn: role descriptions and career paths can help explain a professional context. Respect platform terms and privacy; do not scrape profiles or copy a real person’s identity into a fictional character.

• Google Analytics: aggregated data can show patterns among consenting site visitors. It describes observed traffic, not every potential customer, and should not be used to infer sensitive traits.

Once a persona is grounded, use it to develop messages and experiences. Test which language attracts attention, which evidence resonates, which terms feel familiar and which arguments support a decision. Validate the output with real people rather than assuming that internal empathy predicts behaviour.

Developments of the model

One persona can narrow attention so much that other members of the buying or usage system disappear. If several participants shape the outcome, develop separate personas and show their relationships. Do not force conflicting goals into an “average” character that represents nobody.

Fiction makes a persona vivid, but unsupported detail creates false confidence. Managers often project their own preferences onto customers, producing an egocentric persona despite available data. Label assumptions, confidence and sample limits; invite people with different perspectives to challenge the interpretation.

Personas also change. Needs and knowledge evolve along the customer journey, and markets change over time. Assign an owner, revisit the underlying evidence and retire a persona when it no longer predicts meaningful behaviour.

How to use it

Molson Coors Brewing Company UK and Ireland, a distributor of alcoholic and soft drinks to pubs, clubs and restaurants, used personas to make Net Promoter Score® (NPS) categories tangible. NPS asks how likely a customer is to recommend the company on a scale from 0 to 10. Respondents scoring 9 or 10 out of 10 are promoters; those scoring 6 or below are detractors; scores of 7 or 8 are passives. NPS subtracts the percentage of detractors from the percentage of promoters, while passives are excluded from that calculation.

Equivalently, the calculation is the percentage scoring 9 or 10 minus the percentage classified as detractors. The company represented the groups as Promoter Pat, Passive Pete and Detractor Dave. Posters combined each character’s views of Molson Coors with demographic context. The device helped staff remember different customer experiences, but the labels should be treated as summaries of survey patterns—not fixed personality types or causal explanations.

To build and use a persona:

• Define the business or design decision and the population in scope.

• Gather behavioural evidence from customers, users and relevant internal teams.

• Cluster recurring goals, contexts, obstacles and decision roles.

• Create only the personas needed to explain meaningful differences.

• Separate observed facts, analytical interpretations and fictional details.

• Use scenarios to test messages, journeys and product choices against each persona’s goals.

• Validate decisions with real customers and outcome data, then update the persona.

Some things to think about

• Make the persona memorable with a name and concise story, but keep its age, home, family, aspirations, possessions and other details only when those attributes are supported and relevant. A colourful biography is not a substitute for insight.

• A cut-out or poster can keep the customer visible in meetings. Pair it with a short evidence card showing research basis, date, confidence, exclusions and the decision it is intended to support.

Top practical tip

Give each persona enough human detail to be memorable, then attach the evidence: recurring goal, behaviour, context, source, confidence and last review date. If a detail cannot change a decision, leave it out.

Top pitfall

Do not confuse “walking in the customer’s shoes” with knowing the customer. Unsupported personas amplify projection, stereotypes and sample bias; validate the model with real people and measured outcomes.

Further reading

• Cooper, A. (nineteen ninety-nine). The Inmates Are Running the Asylum. Sams.
• Pruitt, J. and Adlin, T. (two thousand and six). The Persona Lifecycle. Morgan Kaufmann.