User Persona Template: 6 Examples to Copy (B2B, B2C, Free)

User Persona Template: 6 Examples to Copy

A user persona is a one-page artifact that turns research about real users into a memorable character your team can design for. This guide gives you 6 ready-to-copy user persona templates across B2B SaaS, B2C, healthcare, fintech, and education contexts — plus the empty template you can adapt for your own product.

The trick to good personas isn't volume of detail — it's getting the six right things on a single page so your team actually references it during design reviews.

What Goes in a User Persona Template

Every example below uses the same six-block structure. Copy the structure even if you skip the examples:

Block	Purpose
Identity	Name, photo, role, one-line bio — gives the persona a face
Demographics	Age, location, tech fluency, team size — but only what affects design
Goals	What they're trying to accomplish (1-3 max, ranked)
Frustrations	Pain points with existing solutions (in their language)
Behaviors	How often, where, on what device, with whom
Quote	One representative line that captures who they are

Skip these: personality types, MBTI labels, favorite brands, hobbies unrelated to product use, fake stock photos. They're filler that doesn't change design decisions.

Template 1: B2B SaaS — UX Researcher

Identity: Maya Chen · Senior UX Researcher · 50-person SaaS company · 5 years experience

Demographics:

31, based in Brooklyn, hybrid 3 days/week
High tech fluency, comfortable with research platforms
Team of 2 (her + 1 junior researcher)
Reports to Head of Design

Goals:

Validate IA changes before engineering builds them
Run more research with the same headcount (efficiency)
Get buy-in from PMs who don't trust research

Frustrations:

Optimal Workshop costs $149/mo for one tool; budget was cut
PMs say "let's just ship and A/B test" instead of validating first
Recruiting takes longer than running the study itself

Behaviors:

Runs 2-3 studies/month, mix of card sorts + tree tests + interviews
Works in Figma + Notion + a research tool
Reads NN/g, Maze blog, listens to Brave UX podcast

Quote: "I'd rather have one tool that does 80% of what I need at $19/mo than four specialized tools that add up to $400."

Template 2: B2B SaaS — Product Manager (the buyer)

Identity: Marcus Johnson · Senior Product Manager · 200-person SaaS · 7 years experience

Demographics:

38, Austin TX, fully remote
Moderate tech fluency, lives in Linear + Slack + Notion
Owns 1 product area, works with 2 PMs in adjacent areas
Reports to VP Product

Goals:

Ship features that actually move retention/activation
Justify roadmap decisions to leadership with data
Reduce the "let's just ship it" instinct on his team

Frustrations:

Engineering builds whatever's in the spec, even when the spec is wrong
Research feels like a 4-week tax on every decision
Analytics tells him what's happening but not why

Behaviors:

Uses Mixpanel daily, runs 1-2 user interviews per quarter
Decides which research methods his team uses
Approves tools under $50/mo without procurement; anything more requires VP signoff

Quote: "I don't need a 6-week research project. I need a fast read on whether this feature will land before we spend 8 weeks building it."

Template 3: B2C E-Commerce — Casual Mobile Shopper

Identity: Jordan Rivera · Marketing Manager (day job) · Mobile shopper · 32 years old

Demographics:

32, Atlanta, urban
Phone-first for shopping (iPhone 14)
High discretionary spend on apparel, low patience for friction
Doesn't have brand loyalty; chases reviews + recommendations

Goals:

Find products that fit + match style without trying them
Buy quickly without creating accounts
Return easily if anything doesn't fit

Frustrations:

Sizing varies wildly between brands; can't trust size charts
Forced account creation kills the purchase flow
"Free shipping over $X" thresholds shown too late in checkout

Behaviors:

70% of shopping happens on phone during commute
Reads 3-5 reviews before buying anything new
Apple Pay or PayPal preferred; rarely enters card details manually

Quote: "If I have to create an account, sign in via email, or scroll through 4 screens of upsells, I'm out. Make it one tap or lose the sale."

Template 4: Healthcare — Patient Portal User

Identity: Carlos Mendez · Retired teacher · 58 · First-time specialist patient

Demographics:

58, Atlanta, suburban
Moderate digital fluency — comfortable with email + apps but struggles with multi-step web forms
Has Medicare; first time using a non-PCP specialist
Wife (61) helps with anything digital that takes more than 10 minutes

Goals:

See appointment results without calling the office
Message his doctor with quick questions
Manage prescriptions without playing phone tag with the pharmacy

Frustrations:

Login resets every 90 days for "security"
Lab results buried under 5 menus
Portal works on phone but text is too small to read comfortably

Behaviors:

Logs in once a week, mostly to check labs
Wife handles scheduling because the calendar widget is too finicky
Will call the office if anything takes more than 3 attempts in the portal

Quote: "I shouldn't have to call you to find out my own blood test results. But the portal is easier said than done."

Template 5: Fintech — Startup Founder Opening a Business Account

Identity: Lina Park · Founder/CEO · 3-person startup · Just incorporated

Demographics:

29, San Francisco, fully remote team
High tech fluency, evaluates 3-5 tools before picking any
Pre-revenue Y Combinator company
Decides solo on tools under $200/mo

Goals:

Open a business account fast (days, not weeks)
Connect to payroll, Stripe, and accounting without manual reconciliation
Move money internationally for offshore contractors

Frustrations:

Banks ask for documents she doesn't have yet (DBA, EIN proof, lease)
ETAs are vague ("1-5 business days")
Some banks won't approve "AI startups" — undisclosed policy until rejection

Behaviors:

Researches via Twitter and founder Slack groups
Evaluates in 1-2 days; commits once she's seen 1 founder testimonial
Will pay a premium for "approved in 24 hours" SLA

Quote: "I'll pick whoever can approve me in 24 hours. The actual feature set is a tie between Brex, Mercury, and Rho — the differentiator is speed."

Template 6: Education — University Student

Identity: Riley Park · Sophomore · Studying Information Systems · 19

Demographics:

19, Indiana University, on-campus
High tech fluency, but resistant to anything that "looks like Blackboard"
Tight budget — most tools must be free or have student discount
Uses 2-3 devices interchangeably (laptop, phone, library iMac)

Goals:

Get a usable degree without taking on more debt
Build a portfolio for entry-level UX/product internships
Pass classes without spending hours on tool setup

Frustrations:

Most "free" tools have crippling caps (10 responses, 3 days)
Group projects require everyone to sign up for new tools
Academic licenses require .edu email + 6-week approval process

Behaviors:

Researches via TikTok, Reddit, and Discord servers
Will use a tool for 1 class project and switch next semester
Rarely reads documentation; learns by clicking around

Quote: "If I can't get it running in 5 minutes for free, I'll use whatever the prof recommended even if it's worse."

The Empty Template (Copy & Fill)

Use this for your own product:

[Persona Name] · [Role] · [Company size / context] · [Years experience]

DEMOGRAPHICS
- Age, location, work setup
- Tech fluency level
- Team size / relationships
- Reports to / decision authority

GOALS (1-3 ranked)
1. Top goal in their own words
2. Second goal
3. Third goal

FRUSTRATIONS
- Pain point 1 (in their language, not yours)
- Pain point 2
- Pain point 3

BEHAVIORS
- Frequency: how often do they do the task?
- Channels: where do they work? on what device?
- Discovery: how do they find tools?
- Decision: who approves purchases at what threshold?

QUOTE
"One representative line that captures how they actually talk about the problem."

Build it in any tool that lets you make a one-page artifact: Figma, FigJam, Notion, Google Docs. The tool matters less than the source of the content — personas built from real interviews compound across every decision; personas built from stakeholder workshops are fiction.

How to Validate a Persona

Run user interviews with 8-12 participants who match your target user definition. Look for behavioral clusters. Distill each cluster into one persona. Then validate: show the personas to 3-5 new participants and ask which one they identify with. If a persona doesn't claim anyone, it's fiction — redo it.

Pair personas with Jobs-to-be-Done to surface the outcome users want (the "job"), not just who they are. Persona = who. JTBD = what they're trying to accomplish. Together they cover both dimensions.

Connect Personas to Journey Maps

Personas come first; journey maps come second. Each persona moves through a distinct journey. The same product can have 3 personas with 3 different journeys — and trying to design one journey for all 3 produces a generic experience that fits no one. See Journey Map Examples: 6 User & Customer Journey Maps for the worked-example structure.

Run Research to Build Real Personas

ValidateThat's free interview tool supports recorded sessions with auto-transcription and theme tagging — so the patterns you need to build personas surface in days, not weeks. Pair with card sorts and surveys to validate that the persona's mental model matches the real user base.

Start research free →

Frequently Asked Questions

What's in a user persona template? A user persona template captures six things in a single one-page artifact: identity (name, photo, role, one-line bio), demographics that matter to the product (age, location, tech fluency, team size), goals (what they're trying to accomplish), frustrations (current pain points), behaviors (how often, where, on what device), and a representative quote in their own words. Skip personality types, MBTI labels, and "favorite brands" — they're filler that doesn't change design decisions.

What's the difference between a user persona and a customer persona? A user persona describes someone who uses your product, including users who never pay. A customer persona describes someone who makes the purchase decision, with budget authority and procurement criteria. In B2C they're often the same person. In B2B they're almost always different.

How do I create a user persona? Build user personas in four steps. (1) Run 8-12 user interviews. (2) Look for behavioral clusters. (3) Distill each cluster into one persona. (4) Validate by asking 3-5 new participants which persona they identify with.

How many personas should I have? Most product teams need 2-4 personas total. Fewer than 2 means you're treating the user base as monolithic. More than 5 dilutes the value.

Are user personas worth it? Yes — when they're research-driven, lightweight, and actively used. They fail when they're decorative posters. The test: when your team debates a design decision, does someone open the persona and quote it?

User Persona Template: 6 Examples to Copy (B2B, B2C, Free)