Why Most User Personas Are Useless

You've probably seen them before — a stock photo of 'Sarah, 34, Marketing Manager' pinned to a wall with a list of made-up hobbies and a vague quote about wanting things to be 'easy to use'. These personas feel productive to create but do almost nothing to guide real design decisions.

The problem isn't the format. It's the source. Most personas are built from internal assumptions, sales anecdotes, or gut instinct — not actual user research. The result is a document that confirms what a team already believes rather than revealing what users actually need.

This tutorial walks you through how to build user personas grounded in real data: interviews, surveys, behavioural analytics, and synthesis frameworks. These are the methods used by UX teams at product companies and agencies like Lenka Studio when designing apps and digital products for clients across Australia, Singapore, Canada, and the US.

What You'll Need

  • Access to at least 6–8 user interviews (or a plan to conduct them)
  • A survey tool — Typeform, Tally, or Google Forms
  • Behavioural analytics — Mixpanel, Amplitude, or GA4
  • A synthesis tool — FigJam, Miro, or Notion
  • A persona template in Figma or a spreadsheet
  • 2–5 hours of focused synthesis time

Step 1: Define the Research Questions Before You Collect Anything

The biggest mistake teams make is jumping straight into interviews without knowing what they're trying to learn. Before you recruit a single participant, write down 3–5 core questions your personas need to answer.

Good examples for a B2B SaaS product:

  • What triggers someone to look for a solution like ours?
  • What does their current workflow look like before they use us?
  • What's the single biggest frustration in their day-to-day role?
  • How do they measure success in their job?
  • Who else is involved in their buying or adoption decisions?

Write these on a shared document and make sure everyone contributing to the research has agreed on them. This keeps interviews consistent and makes synthesis far easier.

Step 2: Collect Qualitative Data Through User Interviews

Aim for a minimum of 6 interviews per audience segment. If your product serves two distinct user types — say, a project manager and a freelance designer — run 6 interviews for each group.

How to structure the interview

Keep interviews to 45–60 minutes. Use a semi-structured format: you have a guide, but you follow the conversation where it leads.

A solid interview guide structure:

  1. Warm-up (5 min): Ask about their role, their team, their typical day.
  2. Context setting (10 min): Explore the problem space. 'Walk me through the last time you had to do [X].'
  3. Deep dive (25 min): Probe pain points, workarounds, motivations, and decision-making processes.
  4. Tool and workflow audit (10 min): What tools are they using? What do they love or hate about them?
  5. Wrap-up (5 min): Open floor for anything they want to add.

Pro tip: Record every session with consent, then use a transcription tool like Otter.ai or Grain. You'll miss critical details if you're only taking notes.

Step 3: Layer in Quantitative Data

Interviews tell you the 'why'. Analytics and surveys tell you the 'how many' and 'how often'. Both are essential for a persona that holds up under scrutiny.

Survey data

Send a short survey (8–12 questions) to a broader audience — ideally 50–200 respondents. Focus on measurable attributes: company size, role seniority, frequency of the problem, tools used, and willingness to pay. Use Likert scales and multiple-choice to get data you can segment later.

Behavioural analytics

Pull data from Mixpanel, Amplitude, or GA4 to understand actual usage patterns. Look for:

  • Which features are used most and least
  • Where users drop off in onboarding flows
  • Session frequency and depth by user cohort
  • Device and platform breakdown

Segment by plan type, company size, or acquisition channel to spot meaningful differences between user groups.

Step 4: Synthesise Your Data with Affinity Mapping

Now you have raw data — hours of transcripts, survey responses, and analytics exports. Synthesis is where the real work happens.

How to run an affinity mapping session

  1. Open a shared FigJam or Miro board.
  2. Go through each interview transcript and pull out notable quotes, observations, and pain points — one idea per sticky note.
  3. Paste all notes onto the board without organising them yet.
  4. Start grouping notes that share a theme. Don't force categories — let them emerge.
  5. Name each cluster with a concise label: 'Fear of data loss', 'Overwhelmed by too many tools', 'Needs approval from finance before buying'.
  6. Look for clusters that appear repeatedly across multiple participants. These are your signal.

Involve at least two people in this process to reduce individual bias. A research debrief session with your design and product team works well here.

Step 5: Identify Distinct Segments

Not every user is the same, and a single persona for your entire audience is almost always wrong. Use your affinity map clusters and survey segmentation to identify 2–4 meaningful user types.

Ask yourself: do these users have meaningfully different goals, contexts, or frustrations? If yes, they deserve separate personas. If the differences are superficial (different job titles, same underlying needs), merge them.

Common pitfall: Avoid creating personas based on demographics alone. 'Female, 28–35, urban professional' is not a persona. Segment by behaviour, motivation, and context — not age or gender.

Step 6: Write the Persona Document

With your segments identified, now you build the actual persona. Keep it on a single page — in Figma, Notion, or a PDF template — so it can be shared and referenced easily.

What to include in each persona

  • Name and role: A realistic name and job title. Skip the stock photo if it creates unconscious bias — use an abstract avatar instead.
  • Context: Company size, industry, team structure, and tools they use daily.
  • Goals: What are they trying to achieve in their role? What does success look like to them?
  • Frustrations: Specific pain points backed by actual quotes from your interviews. Use real language, not paraphrased summaries.
  • Triggers: What prompts them to look for a solution? What event sets the problem in motion?
  • Decision-making: Who else is involved? What objections do they have to adopting new tools?
  • Key insight: One or two sentences that capture the essential truth about this user — the thing that should inform every design decision made for them.

Pro tip: Include 2–3 direct quotes from your interviews in the persona document. Real words from real users are more persuasive to stakeholders than any summary you write.

Step 7: Validate and Pressure-Test Your Personas

Before you hand these off to a design team, validate them. Share the draft personas with a few of your interview participants and ask: does this feel accurate? What's missing or wrong?

Also run them past your sales, support, or customer success team. These people talk to users every day and will quickly spot anything that feels off. If your persona says users care primarily about speed but your support team is flooded with questions about data exports, that's a gap worth revisiting.

Set a reminder to review and update your personas every 6–12 months, or whenever your product or market shifts significantly. Personas built from 2023 data may not reflect your 2026 users at all — especially in fast-moving industries.

Step 8: Activate the Personas in Your Design Process

A persona only has value if it's used. Here's how to make sure it actually influences the work:

  • Reference personas in design reviews: When critiquing a design decision, ask 'Would [Persona Name] understand this immediately?'
  • Use them in job stories: Format requirements as 'When [situation], [persona] wants to [motivation], so they can [outcome].'
  • Map them to your user journey: Assign each touchpoint in your journey map to the persona most likely to experience it.
  • Share them in onboarding for new team members: Personas help new designers, developers, and marketers get up to speed on who they're building for.

Teams at Lenka Studio anchor every product design engagement in validated personas before a single wireframe is drawn. It's one of the fastest ways to reduce rework and align stakeholders early.

Next Steps

If you're building or redesigning a digital product, getting your personas right is one of the highest-leverage things you can do before touching Figma or writing a line of code. Done well, they cut scope debates, reduce design iterations, and help your team make faster decisions with confidence.

If you're not sure where your brand and product experience stand right now, start with a free brand health score assessment — it takes a few minutes and gives you a clear picture of where the gaps are.

And if you'd like help running user research or building a UX strategy for your product, get in touch with the Lenka Studio team. We work with SMBs and product teams across Australia, Singapore, Canada, and the US to design digital experiences that are grounded in real user insight.