Zurück
How to Create Customer Personas from Real Research

Matthieu Saussaye

To create customer personas, research real customers first, then group them by shared goals and behaviors, and finally describe each group as one realistic, named character. In practice: interview 10-20 customers, survey a larger sample to check which patterns are common, segment the data, and write a one-page profile per segment that your team can use in decisions.
The short version:
Start from a decision. Personas for a product roadmap need different detail than personas for ad targeting.
Interview before you survey. Interviews find the goals, triggers and objections; surveys tell you how widespread they are.
Segment on behavior and motivation, not on age and job title alone.
Keep it to 3-5 personas. More than that and nobody remembers them.
Make each persona falsifiable: every attribute should trace back to data, with the share of customers it represents.
Refresh them. Re-check personas at least yearly or after a big market shift.
Assumption-based vs research-based personas
Most personas fail because they are written in a workshop from what the team already believes. The difference shows up in every field.
Element | Assumption-based persona | Research-based persona | Where the data comes from |
|---|---|---|---|
Goals | "Wants a great experience" | "Needs to produce a monthly report for her director in under an hour" | Interviews, open survey answers |
Triggers | Not included | "Started looking after a failed audit" | Interviews ("What happened just before you started looking?") |
Behaviors | Guessed from demographics | "Compares three tools, reads reviews, asks peers on LinkedIn" | Survey, analytics, CRM |
Objections | "Price-sensitive" | "Worried that IT will block a new tool" | Lost-deal interviews, sales notes |
Size | Not stated | "About a third of new accounts in the last year" (example) | Survey segmentation, CRM |
Quote | Invented | Verbatim from a real customer | Interview transcripts |
The research-based version is harder to write and much more useful: it tells a designer what to build, a marketer what to say and a salesperson which objection to expect.
Where personas come from
The persona as a design tool is usually credited to software designer Alan Cooper. According to the Wikipedia article on personas, he began using an early version in 1983 based on informal interviews with seven or eight users, and popularized the technique in his 1999 book The Inmates Are Running the Asylum. One of the problems he named, the "elastic user", is still the best argument for personas: without a shared, concrete picture of the customer, each stakeholder stretches the definition of "the user" to fit their own preference.
How to create customer personas in 7 steps
1. Define the purpose and the scope
Write down which decisions the personas will inform and for which market. "Prioritize the 2027 roadmap for our SME product in DACH" scopes the research. "Understand our customers" does not.
2. Collect what you already have
CRM fields, sales notes, support tickets, product analytics, past survey results and reviews. These give you behaviors and a first guess at segments. They rarely give you motivations.
3. Interview 10-20 customers and prospects
Recruit across the variety you expect: new and long-standing customers, high and low spend, plus a few who chose a competitor. Ask about real past events, not hypothetical preferences. Stop when new interviews stop producing new goals or objections. Our guide to qualitative data covers how to code transcripts into themes.
4. Survey a larger sample to size the patterns
Turn the themes from the interviews into closed questions (goals, triggers, channels, criteria) plus a few open ones, and send them to a few hundred customers or prospects. Now you can say how common each pattern is. For the method choice, see qualitative vs quantitative research.
5. Segment
Group respondents by the variables that actually separate behavior: main goal, buying trigger, decision criteria, usage intensity. Simple approaches work: cross-tab two or three key variables. With larger samples, cluster analysis on attitude and behavior questions finds groups you might not have guessed. Check each segment is big enough to matter and distinct enough to act on.
6. Write one persona per segment
Give each segment a name, a realistic photo or illustration, and a one-page profile using the template below. Use real quotes. State the share of customers each persona represents.
7. Validate, share and maintain
Test each draft with the sales, support and product teams: "Do you recognize this person?" Then put the personas where decisions are made: briefs, roadmap reviews, campaign plans. Re-run the survey part yearly to check that segment sizes and priorities still hold.
Persona research questions
These questions work in interviews and, with answer options added, in surveys. Group them by what you need to learn. For phrasing tips, see our guide to open-ended questions.
Role and context
"What is your role, and what are you responsible for?"
"Walk me through a typical week. Where does [category] fit in?"
"Who else is involved in decisions about [category]?"
"What tools or products do you use today for this?"
Goals and success
"What are you trying to achieve with [category]?"
"How do you know when you have done this well?"
"What would make your work noticeably easier this year?"
Triggers and buying journey
"What happened that made you start looking for a solution?"
"Where did you look for information first?"
"Which options did you compare, and how did you choose?"
"What almost stopped you from buying?"
Pains and objections
"What is the most frustrating part of [task] today?"
"Tell me about the last time something went wrong with it."
"What would make you hesitate to try a new product in this area?"
Channels and influence
"Where do you go to learn about new tools or ideas in your field?"
"Whose recommendation would you trust most?"
"How do you prefer to be contacted by a vendor?"
Always ask for a concrete example ("Tell me about the last time…"). Stories reveal goals and triggers that direct questions about preferences do not.
A customer persona template
Field | What to write | Example (illustrative) |
|---|---|---|
Name and one-line summary | A memorable name and role | "Operations Olivia, runs a 40-person logistics team" |
Share of customers | From the segmentation | "About 30% of new accounts" (from your own data) |
Goals | Two to three, in her words | "Ship on time without weekend overtime" |
Triggers | What makes her start looking | "A missed delivery escalated to the CEO" |
Buying criteria | Ranked | Integration with current tools, then price, then support |
Pains and objections | Top three | "IT approval takes months" |
Channels | Where she learns and decides | Peer groups, review sites, vendor webinars |
Quote | Verbatim from research | "I don't need more dashboards, I need fewer surprises." |
What it means for us | Implications per team | Product: faster setup. Marketing: lead with reliability. |
Worked example: from interviews to three personas
An illustrative case. A company selling online booking software to small service businesses wants personas to guide its onboarding redesign.
Interviews (15): salon owners, physiotherapists and driving instructors, including four who tried the product and left. Three goals come up repeatedly: fewer no-shows, less time on the phone, and looking professional to new clients.
Survey (several hundred customers): each respondent ranks those goals, reports team size, how they found the product and what nearly made them quit during setup.
Segmentation: two variables separate behavior most clearly, team size (solo vs team) and main goal. Three segments are large enough to act on.
Personas: "Solo Sam" (one-person business, wants fewer calls, sets up on a phone in the evening), "Team Tara" (manages five staff calendars, needs permissions, decides with a partner), and "Growth Gabriel" (cares about looking professional, uses the booking page as a mini website).
Decision: onboarding splits at the first screen into solo and team paths, and the booking-page builder moves earlier for the growth segment.
Every persona attribute here traces back to an interview theme and a survey share. That traceability is what makes teams trust and use them.
Customer personas vs buyer personas vs segments
Concept | Focus | Built from | Used by |
|---|---|---|---|
Customer persona | Existing customers and how they use the product | Customer interviews, surveys, usage data | Product, CX, marketing |
Buyer persona | People who make or influence the purchase | Win/loss interviews, sales data | Sales, marketing |
User persona | People who use the product day to day (may not buy it) | Usability research, analytics | Product, design |
Market segment | A measurable group defined by shared variables | Survey and market data | Strategy, pricing, media |
In practice the terms overlap. A useful rule: a segment is the number, a persona is the story built on top of it. Personas without a segment behind them are fiction; segments without a persona are hard for teams to remember.
Common persona mistakes
Writing them in a workshop without research. You get your assumptions back, nicely formatted.
Segmenting on demographics only. Two 35-year-old managers can buy for opposite reasons.
Too many personas. Ten personas means no persona is prioritized.
Irrelevant details. Hobbies and pets add color but no decisions. Keep only what changes what you build or say.
No size attached. Without a share of customers, teams cannot choose between personas.
Never updated. A persona from three years ago describes a market that has moved.
Ignoring negative personas. Defining who you do not serve saves sales and product time.
Build personas from hundreds of real conversations
The slow part of persona research is the interviews: recruiting, scheduling, transcribing and coding 10-20 conversations, then running a separate survey to size them. SmartInterview combines the two. It runs interview-style surveys by voice or text, in each respondent's language, with an AI that follows up on short answers ("What happened just before you started looking?"). Open responses are coded into themes automatically, and you can cross-tab those themes with closed questions to see which goals and triggers define each segment.
You still decide the segments and write the personas. You do it from far more real answers. Start free.
Frequently Asked Questions
What is a customer persona?
A customer persona is a semi-fictional profile of a key customer group, built from research, that describes their goals, triggers, behaviors, objections and preferred channels. It gives teams a shared, concrete picture of who they are serving.
How many customer personas should I create?
Usually three to five. That is enough to reflect meaningful differences between customers and few enough for teams to remember and prioritize. Start with the segments that represent most of your revenue or growth.
What data do you need to create a persona?
You need qualitative data on goals, triggers and objections, usually from 10-20 interviews, and quantitative data on how common those patterns are, usually from a survey and your CRM or analytics. Demographics alone are not enough.
What should a customer persona include?
A name and summary, the share of customers it represents, goals, buying triggers, decision criteria, pains and objections, channels, a real quote, and what the persona means for product, marketing and sales.
What is the difference between a buyer persona and a customer persona?
A buyer persona focuses on the people who decide or influence a purchase; a customer persona focuses on existing customers and their experience. In practice the terms are often used interchangeably, and many companies build one set that covers both.
How often should personas be updated?
Review them at least once a year, and after any major change such as a new product line, a new market or a shift in competition. Re-running the sizing survey is the quickest way to check whether segments have moved.


