{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-05-16T08:11:12.617Z"},"content":[{"type":"documentation","id":"1e4e9bdd-2fb4-4f96-a06d-438ae29dc5d0","slug":"user-persona-template","title":"User Persona Template: 7 Free Templates and Examples for Product Teams (2026)","url":"https://www.koji.so/docs/user-persona-template","summary":"A complete library of user persona templates — lightweight, qualitative, statistical, B2B buyer, empathy map, JTBD, and anti-persona — with rules for filling each one in. Anchored in Nielsen Norman Group's three persona types, with guidance on saturation, validation, and a modern AI-generated workflow that compresses persona creation from 4–6 weeks to 3–5 days.","content":"## What is a user persona template?\n\nA 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.\n\nThe 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.\n\n## Why most persona templates fail\n\nIf 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.\n\nThe 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.\n\nThe 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.\n\nThe templates below are designed to avoid all three failure modes by capturing behavioral evidence directly from research, not from a brainstorm.\n\n## Template #1: Lightweight Persona (Proto-Persona)\n\n**Best for:** Pre-launch startups, weekly discovery sprints, early-stage hypothesis testing. Build in under an hour using assumptions you then validate with interviews.\n\n```\n[Persona Name + One-Line Identity]\nExample: \"Burned-Out BizOps Bea — Series A startup, owns the data stack\"\n\nContext\n- Company stage / type:\n- Role and team size:\n- Tools they use every day:\n\nJob to Be Done\n- The functional job:\n- The emotional job:\n- The social job:\n\nCurrent Workaround\n- How they solve this today:\n- What they have tried before:\n- Why those alternatives failed:\n\nTrigger\n- The event that makes them search for a new solution:\n\nBlockers\n- What stops them from switching:\n- Who else has to approve:\n\nQuote (hypothetical until validated)\n- \"What they would probably say...\"\n```\n\n**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.\n\n## Template #2: Qualitative Research-Backed Persona\n\n**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.\n\n```\nPersona Name + Photo\nTag line — one sentence that captures who they are\n\nDemographics & Firmographics (kept minimal)\n- Role / title:\n- Company size or life stage:\n- Years of experience:\n- Geography (only if it matters):\n\nGoals (the outcomes they actually want)\n- Top 3 goals, ranked\n\nJobs to Be Done\n- Functional, emotional, and social jobs\n- Use the format \"When ___, I want to ___, so I can ___\"\n\nBehaviors\n- Current process step-by-step\n- Frequency of the task\n- Tools and channels used\n\nPain Points & Frustrations\n- Top 3 frictions, with severity\n- Quotes from real interviews\n\nMotivations & Decision Drivers\n- What gets them to act\n- What they evaluate before buying\n- Who else is involved in the decision\n\nObjections & Switching Costs\n- Why they would NOT adopt your product\n- What would need to be true for them to switch\n\nSuccess Criteria\n- How they measure success in their role\n- The metric that, if you moved it, would change their life\n\nRepresentative Quotes\n- 3–5 verbatim quotes from interviews (with participant ID for traceability)\n```\n\n**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.\n\n## Template #3: Statistical / Quantitative Persona\n\n**Best for:** Enterprise products with large user bases, mature research practices, or teams who already have qualitative personas and need to validate at scale.\n\n```\nSegment Name + Size (% of total users)\n\nDistinguishing Variables (3–5 that statistically separate this segment)\n- Behavioral variable 1 (e.g., logins per week, value > X)\n- Behavioral variable 2 (e.g., feature use, value range)\n- Attitudinal variable 3 (e.g., NPS score, value range)\n\nObserved Behaviors (from product analytics)\n- Activation pattern:\n- Feature adoption profile:\n- Churn / retention signal:\n\nValidated Goals & Pain Points (from survey + interview cross-reference)\n\nFinancial Profile\n- ACV / LTV range:\n- Plan tier:\n- Expansion potential:\n\nConfidence Metrics\n- Sample size (n =)\n- Margin of error:\n- Date of last refresh:\n```\n\n**Validation rule:** Refresh quarterly. Statistical personas decay fast as your product and market change.\n\n## Template #4: B2B Buyer Persona\n\n**Best for:** B2B SaaS teams selling to multi-stakeholder buying committees.\n\nThe 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.\n\n```\nBuyer Persona Name + Role in Buying Committee\nE.g., \"Skeptical CFO Steve — Economic buyer, signs the contract\"\n\nBuying-Center Role: [Economic / Technical / User / Champion / Blocker]\nReports to:\nKey metrics they own:\n\nTrigger Events (what makes them start a buying cycle)\nEvaluation Criteria (ranked)\nProcurement Process & Timeline\nObjections & Risk Tolerance\nProof They Need (case studies, benchmarks, security docs)\nChampion Relationship — who inside the company helps you sell to them\n```\n\nFor a deeper dive on building these with survey data, see our [buyer persona survey guide](/docs/buyer-persona-survey-guide).\n\n## Template #5: Empathy Map Persona\n\n**Best for:** Design teams running workshops, kickoffs, or early concept work. The empathy map is a complement to a persona, not a replacement.\n\n```\nFor [Persona Name]:\n\nSAYS — verbatim quotes from interviews\nTHINKS — what they believe but might not voice\nDOES — observable behavior\nFEELS — emotional state in the journey\n\nGAINS — the wins they are chasing\nPAINS — the frustrations blocking them\n```\n\nFor a deeper dive, see our [empathy map guide](/docs/empathy-map-guide).\n\n## Template #6: Jobs-to-Be-Done Persona (Job-Centric)\n\n**Best for:** Teams who have adopted Clayton Christensen / Tony Ulwick frameworks and want personas organized around jobs, not people.\n\n```\nJob Title (functional outcome)\nE.g., \"Get accurate revenue numbers in front of the board in under 2 hours\"\n\nJob Executor (who hires the job)\nJob Context (situation, location, time pressure)\nDesired Outcomes (with metrics — speed, accuracy, predictability)\nCurrent Solutions Being \"Fired\"\nForces of Progress (push of the situation, pull of the new solution)\nForces of Resistance (anxiety about the new, habit of the old)\n```\n\nIf you are new to this framing, start with our [jobs to be done framework](/docs/jobs-to-be-done-framework) and [switch interviews JTBD method](/docs/switch-interviews-jtbd-method) guides.\n\n## Template #7: Anti-Persona (Who You Are NOT Building For)\n\n**Best for:** Teams suffering from scope creep, where every new request gets shoved into the roadmap \"because some user wants it.\"\n\n```\nAnti-Persona Name\n\nWho they are:\nWhy they look like a fit at first glance:\nWhy they are NOT a fit:\n- Their job is fundamentally different\n- Their willingness to pay is too low / too volatile\n- Serving them would compromise the primary persona\n\nWhat to do when they show up:\n- A specific routing / messaging plan\n```\n\nAnti-personas are an underused tool. Documenting who you will *not* serve is often more strategic than documenting who you will.\n\n## How to fill in a persona template (the right way)\n\n### Step 1 — Define the segment before you draft the persona\nStart 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.\n\nSee our [customer segmentation research interviews](/docs/customer-segmentation-research-interviews) guide for how to identify and validate distinct segments.\n\n### Step 2 — Run 10–20 interviews per persona\nQualitative 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.\n\nFor a deeper look at how to think about this, read our [data saturation in qualitative research](/docs/data-saturation-qualitative-research) and [how many interviews are enough](/docs/how-many-interviews-enough) guides.\n\n### Step 3 — Anchor every field to evidence\nFor 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.\n\n### Step 4 — Capture verbatim quotes\nQuotes 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.\n\nSee our [customer quotes guide](/docs/customer-quotes-guide) for how to extract, tag, and reuse quotes effectively.\n\n### Step 5 — Pressure-test against anti-evidence\nFor 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.\n\n### Step 6 — Make them living documents\nAccording 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.\n\n## The modern approach: AI-generated personas from real interview data\n\nThe 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.\n\nKoji 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.\n\nHere is how the modern flow compares:\n\n| Step | Traditional Persona Workflow | Koji Workflow |\n| --- | --- | --- |\n| Recruit 15 participants | 1–2 weeks (recruiter or scheduling) | Same day (share interview link) |\n| Conduct interviews | 2 weeks (1:1 calls, 1 hour each) | 24–48 hours (async voice or text) |\n| Transcribe + clean | 3–5 days | Real-time |\n| Code and theme | 1–2 weeks (manual coding in Dovetail) | Automatic, with quality scoring |\n| Draft persona | 2–3 days | Generated draft, editable |\n| Total time | **4–6 weeks** | **3–5 days** |\n\nKey Koji capabilities for persona work:\n- **AI-moderated interviews** with intelligent follow-up probing, so you capture the depth a static survey never could\n- **Automatic theme extraction** that surfaces the patterns persona fields should reflect\n- **Quality scoring (1–5)** per interview, so you weight high-signal interviews more heavily\n- **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](/docs/structured-questions-guide)\n- **Customer quote extraction** with one click, so every persona field can be backed by a verbatim quote\n- **AI-generated personas** that you can edit, version, and export\n\nFor a deeper look at how this works, see [AI-generated customer personas](/docs/ai-generated-customer-personas).\n\n## What \"good\" looks like — a worked example\n\nLet's contrast a weak persona field with a strong one for the same segment.\n\n**Weak (assumption-based, demographics-first):**\n> \"Sarah, 32, marketing manager at a SaaS startup. Loves analytics and is data-driven. Wants better tools.\"\n\n**Strong (evidence-anchored, behavior-first):**\n> \"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.\"\n\nThe second persona generates immediate product, marketing, and pricing decisions. The first generates a wall poster.\n\n## Common mistakes when using persona templates\n\n1. **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.\n2. **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.\n3. **One-and-done personas.** If your persona file has not been updated in 12 months, it is a historical artifact, not a research tool.\n4. **Demographic overreach.** Unless age, gender, or location materially changes the behavior, leave them out.\n5. **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.\n6. **Skipping the anti-persona.** Without one, the persona drifts toward \"everyone\" and loses power.\n\n## How many personas should you have?\n\nFor 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.\n\n## Related Resources\n\n- [Structured Questions in AI Interviews](/docs/structured-questions-guide) — the 6 question types Koji uses to capture demographic, behavioral, and attitudinal data inside conversational interviews\n- [How to Create Research-Backed User Personas from Customer Interviews](/docs/user-persona-research-guide) — the end-to-end methodology that pairs with these templates\n- [AI-Generated Customer Personas](/docs/ai-generated-customer-personas) — the modern workflow for building personas directly from Koji interview data\n- [How to Build Data-Driven Buyer Personas with Research Surveys](/docs/buyer-persona-survey-guide) — surveys for validating qualitative B2B personas at scale\n- [Jobs to Be Done Framework](/docs/jobs-to-be-done-framework) — the foundation for the JTBD persona template\n- [Customer Quotes Guide](/docs/customer-quotes-guide) — how to extract and tag the verbatim quotes that bring personas to life\n- [Customer Segmentation Research Interviews](/docs/customer-segmentation-research-interviews) — how to identify the behaviorally distinct segments your personas should represent","category":"Research Methods","lastModified":"2026-05-16T03:19:48.416319+00:00","metaTitle":"User Persona Template: 7 Free Templates with Examples (2026) — Koji","metaDescription":"Free user persona templates with real examples — lightweight, research-backed, statistical, B2B buyer, empathy map, JTBD, and anti-persona. Generate personas from real interview data in days, not weeks.","keywords":["user persona template","persona template","user persona examples","buyer persona template","proto persona template","customer persona template","UX persona template","persona template free"],"aiSummary":"A complete library of user persona templates — lightweight, qualitative, statistical, B2B buyer, empathy map, JTBD, and anti-persona — with rules for filling each one in. Anchored in Nielsen Norman Group's three persona types, with guidance on saturation, validation, and a modern AI-generated workflow that compresses persona creation from 4–6 weeks to 3–5 days.","aiPrerequisites":["user-persona-research-guide","customer-segmentation-research-interviews"],"aiLearningOutcomes":["Choose the right persona template for your stage (lightweight, qualitative, or statistical)","Capture behavioral signals over demographic stereotypes in every persona field","Validate personas against interview evidence using the 10–20 per segment rule","Use anti-personas to prevent roadmap scope creep","Generate research-backed personas from real interview data in days, not weeks"],"aiDifficulty":"beginner","aiEstimatedTime":"14 min read"}],"pagination":{"total":1,"returned":1,"offset":0}}