User Persona Template: 7 Free Templates and Examples for Product Teams (2026)

What is a user persona template?

A user persona template is a fillable framework that helps product teams document the goals, behaviors, frustrations, and context of a specific user segment in a consistent, shareable format. Good templates force you to capture behavioral signals (jobs-to-be-done, current workarounds, decision triggers) over demographic stereotypes (age bracket, gender, generic job title) — because behavior, not demographics, predicts how someone will use your product.

The templates below cover the three persona types Nielsen Norman Group identifies in modern UX practice: lightweight (proto-personas), qualitative (research-backed), and statistical (data-validated). Use the right one for your stage and budget.

Why most persona templates fail

If you have ever printed a glossy persona poster, hung it on a wall, and watched the team ignore it for the next twelve months, you are not alone. Personas fail not because the concept is broken, but because they are usually built on assumptions rather than actual user data — a finding well documented in Nielsen Norman Group's persona research.

The second failure mode: demographic bloat. A persona that opens with "Sarah, 34, marketing manager, drinks lattes" tells you nothing useful. The persona that opens with "Spends 6 hours a week reconciling spreadsheets and has tried 3 tools in the last year — none stuck because they required IT to set up" tells you exactly what to build.

The third failure mode: personas as marketing artifacts, not decision tools. If a persona cannot answer questions like "Will this user pay for this feature?" or "What will block adoption?", it is decoration.

The templates below are designed to avoid all three failure modes by capturing behavioral evidence directly from research, not from a brainstorm.

Template #1: Lightweight Persona (Proto-Persona)

Best for: Pre-launch startups, weekly discovery sprints, early-stage hypothesis testing. Build in under an hour using assumptions you then validate with interviews.

[Persona Name + One-Line Identity]
Example: "Burned-Out BizOps Bea — Series A startup, owns the data stack"

Context
- Company stage / type:
- Role and team size:
- Tools they use every day:

Job to Be Done
- The functional job:
- The emotional job:
- The social job:

Current Workaround
- How they solve this today:
- What they have tried before:
- Why those alternatives failed:

Trigger
- The event that makes them search for a new solution:

Blockers
- What stops them from switching:
- Who else has to approve:

Quote (hypothetical until validated)
- "What they would probably say..."

Validation rule: A proto-persona is a hypothesis. Run 5–8 interviews against it before you treat it as real. If 4+ interviews contradict your assumptions, rewrite the persona — do not patch it.

Template #2: Qualitative Research-Backed Persona

Best for: Product teams with budget for 15–30 interviews per segment. This is the workhorse template for most B2B SaaS, consumer apps, and internal tools.

Persona Name + Photo
Tag line — one sentence that captures who they are

Demographics & Firmographics (kept minimal)
- Role / title:
- Company size or life stage:
- Years of experience:
- Geography (only if it matters):

Goals (the outcomes they actually want)
- Top 3 goals, ranked

Jobs to Be Done
- Functional, emotional, and social jobs
- Use the format "When ___, I want to ___, so I can ___"

Behaviors
- Current process step-by-step
- Frequency of the task
- Tools and channels used

Pain Points & Frustrations
- Top 3 frictions, with severity
- Quotes from real interviews

Motivations & Decision Drivers
- What gets them to act
- What they evaluate before buying
- Who else is involved in the decision

Objections & Switching Costs
- Why they would NOT adopt your product
- What would need to be true for them to switch

Success Criteria
- How they measure success in their role
- The metric that, if you moved it, would change their life

Representative Quotes
- 3–5 verbatim quotes from interviews (with participant ID for traceability)

Validation rule: Anchor every field to evidence. If a claim in the persona is not traceable to at least 3 interviews or a survey n>30, mark it as "assumption" in italics.

Template #3: Statistical / Quantitative Persona

Best for: Enterprise products with large user bases, mature research practices, or teams who already have qualitative personas and need to validate at scale.

Segment Name + Size (% of total users)

Distinguishing Variables (3–5 that statistically separate this segment)
- Behavioral variable 1 (e.g., logins per week, value > X)
- Behavioral variable 2 (e.g., feature use, value range)
- Attitudinal variable 3 (e.g., NPS score, value range)

Observed Behaviors (from product analytics)
- Activation pattern:
- Feature adoption profile:
- Churn / retention signal:

Validated Goals & Pain Points (from survey + interview cross-reference)

Financial Profile
- ACV / LTV range:
- Plan tier:
- Expansion potential:

Confidence Metrics
- Sample size (n =)
- Margin of error:
- Date of last refresh:

Validation rule: Refresh quarterly. Statistical personas decay fast as your product and market change.

Template #4: B2B Buyer Persona

Best for: B2B SaaS teams selling to multi-stakeholder buying committees.

The key difference from a user persona: a B2B buyer persona must capture buying-center role (economic buyer, technical evaluator, end user, champion, blocker) and the buying process itself.

Buyer Persona Name + Role in Buying Committee
E.g., "Skeptical CFO Steve — Economic buyer, signs the contract"

Buying-Center Role: [Economic / Technical / User / Champion / Blocker]
Reports to:
Key metrics they own:

Trigger Events (what makes them start a buying cycle)
Evaluation Criteria (ranked)
Procurement Process & Timeline
Objections & Risk Tolerance
Proof They Need (case studies, benchmarks, security docs)
Champion Relationship — who inside the company helps you sell to them

For a deeper dive on building these with survey data, see our buyer persona survey guide.

Template #5: Empathy Map Persona

Best for: Design teams running workshops, kickoffs, or early concept work. The empathy map is a complement to a persona, not a replacement.

For [Persona Name]:

SAYS — verbatim quotes from interviews
THINKS — what they believe but might not voice
DOES — observable behavior
FEELS — emotional state in the journey

GAINS — the wins they are chasing
PAINS — the frustrations blocking them

For a deeper dive, see our empathy map guide.

Template #6: Jobs-to-Be-Done Persona (Job-Centric)

Best for: Teams who have adopted Clayton Christensen / Tony Ulwick frameworks and want personas organized around jobs, not people.

Job Title (functional outcome)
E.g., "Get accurate revenue numbers in front of the board in under 2 hours"

Job Executor (who hires the job)
Job Context (situation, location, time pressure)
Desired Outcomes (with metrics — speed, accuracy, predictability)
Current Solutions Being "Fired"
Forces of Progress (push of the situation, pull of the new solution)
Forces of Resistance (anxiety about the new, habit of the old)

If you are new to this framing, start with our jobs to be done framework and switch interviews JTBD method guides.

Template #7: Anti-Persona (Who You Are NOT Building For)

Best for: Teams suffering from scope creep, where every new request gets shoved into the roadmap "because some user wants it."

Anti-Persona Name

Who they are:
Why they look like a fit at first glance:
Why they are NOT a fit:
- Their job is fundamentally different
- Their willingness to pay is too low / too volatile
- Serving them would compromise the primary persona

What to do when they show up:
- A specific routing / messaging plan

Anti-personas are an underused tool. Documenting who you will not serve is often more strategic than documenting who you will.

How to fill in a persona template (the right way)

Step 1 — Define the segment before you draft the persona

Start with a single, behaviorally distinct user segment. "All small businesses" is not a segment. "Solo bookkeepers managing 5–20 clients on QuickBooks Online who switched in the last 12 months" is a segment. The narrower, the more useful.

See our customer segmentation research interviews guide for how to identify and validate distinct segments.

Step 2 — Run 10–20 interviews per persona

Qualitative research consensus places saturation between 5 and 30 interviews per segment, with most teams reaching diminishing returns between 12 and 20. For high-stakes products, validate with a survey of n>100 against the qualitative themes.

For a deeper look at how to think about this, read our data saturation in qualitative research and how many interviews are enough guides.

Step 3 — Anchor every field to evidence

For every claim in the persona, you should be able to answer: "What interview, survey, or analytics event told us this?" If you cannot, the field is a hypothesis — mark it as such.

Step 4 — Capture verbatim quotes

Quotes are the connective tissue between qualitative data and stakeholder buy-in. A claim like "Users are frustrated by onboarding" is far less persuasive than "It took me three days to find the integration tab and I almost gave up" — one is an inference, the other is a fact.

See our customer quotes guide for how to extract, tag, and reuse quotes effectively.

Step 5 — Pressure-test against anti-evidence

For every key persona claim, deliberately look for interviews that contradict it. If you cannot find any contradictions, you have probably cherry-picked. Real personas have nuance and exceptions.

Step 6 — Make them living documents

According to Nielsen Norman Group, the strongest personas evolve over time. Set a quarterly review where you check each persona against the last 90 days of interviews and analytics, and update behavioral fields. Personas built once and never updated are research debt.

The modern approach: AI-generated personas from real interview data

The traditional persona workflow takes 3–6 weeks: schedule interviews, transcribe, code, synthesize, design poster, socialize, never look at it again. For most product teams running weekly discovery, that timeline is dead on arrival.

Koji takes a different approach. Because Koji conducts AI-moderated voice and text interviews end-to-end — recruiting, moderating, transcribing, and analyzing — the platform can generate research-backed personas directly from your latest cohort of interviews, with every field linked to the verbatim moment in the transcript that supports it.

Here is how the modern flow compares:

Key Koji capabilities for persona work:

• AI-moderated interviews with intelligent follow-up probing, so you capture the depth a static survey never could
• Automatic theme extraction that surfaces the patterns persona fields should reflect
• Quality scoring (1–5) per interview, so you weight high-signal interviews more heavily
• Structured questions (6 types — open_ended, scale, single_choice, multiple_choice, ranking, yes_no) for capturing demographic, behavioral, and attitudinal data inside the same interview — see our structured questions guide
• Customer quote extraction with one click, so every persona field can be backed by a verbatim quote
• AI-generated personas that you can edit, version, and export

For a deeper look at how this works, see AI-generated customer personas.

What "good" looks like — a worked example

Let's contrast a weak persona field with a strong one for the same segment.

Weak (assumption-based, demographics-first):

"Sarah, 32, marketing manager at a SaaS startup. Loves analytics and is data-driven. Wants better tools."

Strong (evidence-anchored, behavior-first):

"B2B Marketer at a 50–200 person SaaS. Owns the demand-gen funnel. Spends 6+ hours per week pulling reports from HubSpot, Mixpanel, and Salesforce into a Monday slide deck for the CMO. Has tried Looker Studio twice (gave up — too much SQL) and Hex (gave up — sales required a procurement cycle). Decision trigger: a missed pipeline number that forced an emergency dashboard build. Won't switch unless onboarding is under 30 minutes and the CFO already approved the vendor."

The second persona generates immediate product, marketing, and pricing decisions. The first generates a wall poster.

Common mistakes when using persona templates

1. Filling in every field even when you have no evidence. An honest persona with 5 well-supported fields beats a complete persona with 15 fabricated ones.
2. Designing for the persona instead of with the persona. Test new designs against the actual users in your panel, not your interpretation of a poster.
3. One-and-done personas. If your persona file has not been updated in 12 months, it is a historical artifact, not a research tool.
4. Demographic overreach. Unless age, gender, or location materially changes the behavior, leave them out.
5. Confusing personas with segments. A segment is statistical (people who match a behavioral profile). A persona is narrative (a representative human-shaped story of that segment). You need both.
6. Skipping the anti-persona. Without one, the persona drifts toward "everyone" and loses power.

How many personas should you have?

For most products, 3–5 personas is the sweet spot. Fewer than 3 and you are probably under-segmenting. More than 5 and the team will stop using them. If you find yourself needing 7+ personas, you may be selling a platform with distinct product lines — each line should have its own 3–5 personas.

Related Resources

• Structured Questions in AI Interviews — the 6 question types Koji uses to capture demographic, behavioral, and attitudinal data inside conversational interviews
• How to Create Research-Backed User Personas from Customer Interviews — the end-to-end methodology that pairs with these templates
• AI-Generated Customer Personas — the modern workflow for building personas directly from Koji interview data
• How to Build Data-Driven Buyer Personas with Research Surveys — surveys for validating qualitative B2B personas at scale
• Jobs to Be Done Framework — the foundation for the JTBD persona template
• Customer Quotes Guide — how to extract and tag the verbatim quotes that bring personas to life
• Customer Segmentation Research Interviews — how to identify the behaviorally distinct segments your personas should represent