Step-by-Step Guide
Most personas are fiction with stock photos. Real personas are research-grounded documents that change how marketing, sales, and product teams operate. The 6-step process for building useful personas — and the demographic-trap that kills 80% of persona projects.
A buyer persona is a research-grounded archetype representing a specific kind of person in your buying audience. Done well, it tells your marketing team how to write copy, your sales team how to handle objections, and your product team what features matter. Done badly, it's an inert document filed in a Notion workspace, ignored within a quarter.
The difference between useful and useless personas is research depth and behavioral specificity. A persona that says "Marketing Mary, 35, lives in the suburbs, likes yoga" is useless. A persona that says "Mid-market growth marketer who measures success in pipeline-influenced revenue and gets dismissed by their CEO if MQL volume drops two months in a row" is useful.
Most B2B companies need 2-4 personas, not 8. B2C consumer brands often need 1-3. Each persona should represent a distinct decision-making behavior, not just a different job title.
For a marketing analytics tool, "VP of Marketing" and "Director of Marketing Operations" might be one persona (both make build-vs-buy decisions, both care about pipeline impact) or two distinct personas (VP focuses on revenue attribution; Ops focuses on data quality). Talk to a few of each to decide.
Eight interviews is the statistical sweet spot. Below 5, your patterns are anecdotal. Above 12, you hit diminishing returns. Aim for 8-12 conversations per persona, balanced across customers (who chose you), churned customers (who left), and prospects (who didn't choose you).
Interview structure: 30 minutes, recorded, transcribed. Standard interview guide. Listen for patterns in language, decision criteria, and trigger events.
For each persona, document:
Use the persona canvas template. Keep it to one page. Include a verbatim quote from one of your interviews — quotes carry more conviction than paraphrases. Avoid stock photos. Use first names only.
Bring the personas to your sales team and CS team. Read them aloud. Ask: does this match the people you talk to every day? Their pushback will surface gaps in your research and clarifying language for your final document.
Personas that live in a Notion doc are dead. Personas that live in:
...are alive. The format isn't what matters. The fact that decisions are made by reference to the persona is what matters.
The fastest test for whether your personas are real: ask three people on your team to name your personas without looking. If they can, the personas are operational. If they can't, the personas are decorative.
Real personas live in the team's vocabulary. "That's a Sarah question." "We need a play for the Marcus persona." If you don't hear that language in your weekly meetings, the personas haven't taken root.
Too many personas. If you have 7 personas, you have 0 personas. Constrain to 2-4.
Persona by committee. Built by polling internal stakeholders instead of researching real people. Produces aspirational personas detached from data.
Demographic-heavy. Pages of demographic detail and nothing about decision behavior.
Never updated. Built once, frozen forever. Personas should be refreshed every 12-18 months.