What a customer persona is
A persona is not an invented character with a name and an avatar. It is a tool that helps a team hold one shared understanding of who the product is for. A good persona covers:
- Demographic context — age, region, income level, occupation
- Motivation — why they come to your store, what job they are hiring it for
- Pain points — what stops them buying, what annoys them in the current experience
- Behavioural patterns — how they research a product, how they decide, which channels they arrive through
- Quotes — verbatim phrasing from interviews that carries the customer’s voice
The last item is routinely underrated — the customer’s own words are worth more than any summary.
Persona versus segment: different tools for different jobs
| Persona | Segment | |
|---|---|---|
| Nature | A qualitative portrait | A quantitative group |
| What it describes | Motivation and behaviour | Behavioural and demographic attributes |
| Where it is used | Design, content, strategy | Targeting, personalization, analytics |
| Built from | Interviews plus data | Platform data |
| Updated | As understanding of the audience changes | Dynamically, as the data changes |
In a mature team personas complement segments: the persona describes the why, the segment operationalises the who inside the working system.
How to build a persona for e-commerce
A four-step process:
-
Segment the transactional data. Find groups with a similar pattern: purchase frequency, average order value, categories. That is the starting hypothesis for the personas.
-
Run interviews. Five to eight conversations per persona is enough to reach saturation. Ask about the job, not about the product: “Tell me how you chose the last time…”
-
Assemble the persona from data, not from guesses. Every attribute should rest on data — or be explicitly labelled as a hypothesis.
-
Test it against a journey map. Walk each persona’s path through your site: where will they get stuck, where will they leave, what is missing.
Important: a persona is a living document. Markets shift and audiences evolve. Review personas once a year, or whenever the product or the market changes materially.
Common mistakes
Invented personas. The team creates personas without research and ends up with a document that reflects internal assumptions rather than real customers.
Too many attributes. A persona with 30 fields is unusable. Keep only what drives decisions: motivation, pain points, channels, purchase pattern.
Personas with no consequence. If the personas are created, live in a slide deck and never influence segmentation in the CDP, content strategy or design, the time was wasted.