Most persona examples online are furniture. A stock photo. A cute name. “Sarah enjoys yoga and craft beer.” Nobody ever made a better product because of Sarah’s hobbies.
A persona has one job: help a team understand a real person well enough to serve them better. The four examples below do that job. One B2C mobile app user. One B2B buyer. One service-business customer. One nonprofit donor. Each is fully built, and each comes with a plain accounting of why it works — because the why is the part you get to keep.
New to personas? Start with Personas 101. Ready to build your own? The step-by-step lives at how to create a user persona. This page shows you the standard to hit.
The rule behind every example here: a detail earns its place only if it informs a decision. Nielsen Norman Group’s research on why personas fail keeps finding the same culprit — personas that get created, admired, and never used. Decoration is how that happens.
Example 1: The B2C Mobile App User
A consumer app persona lives or dies on one question: what 25 minutes of this person’s day do you actually get?
“I’ve got 25 minutes and one pair of shoes. Meet me where I am.”
- Fit a workout between 12-hour shifts
- Feel progress by Friday
- Keep the streak without the guilt
- Rigid six-week programs
- Shame-flavored notifications
- Paywall before the first workout
Why this persona works. Nothing here is trivia. The shift schedule tells product why a fixed “Monday: legs” plan fails her — her Monday might be someone else’s midnight. The streak tells lifecycle marketing what to protect and what never to weaponize: a “you missed a day” push is how the app earns its uninstall. The paywall frustration tells growth exactly where the first value moment has to land — before the credit card form, not after.
Notice what’s missing. No favorite bands. No personality type. Maya is defined by her constraints, and constraints are what design is made of. Her quote does the heaviest lifting: eleven words that settle a hundred roadmap arguments.
Example 2: The B2B Buyer
In B2B, you are never selling to a person. You are selling to a person who has to sell it to five more.
“I’m not buying software. I’m buying fewer 6 a.m. phone calls.”
- Cut missed delivery windows
- Get dispatch, finance, and IT to yes
- Roll out without stalling operations
- Pricing hidden behind a demo call
- A six-person signoff chain
- Tools that die in week three
Why this persona works. Dan’s quote reframes the entire sale. He isn’t comparing feature grids; he’s buying a quieter Tuesday. That single line tells marketing to lead with the outcome and tells sales to stop demoing dashboards nobody asked about.
The “get three departments to yes” goal is the strategic heart of the card. Gartner’s B2B buying research puts the typical buying group at six to ten stakeholders, with buyers spending only about 17% of the journey meeting with potential suppliers. So the persona’s real demand isn’t a better pitch — it’s ammunition Dan can forward: a one-page ROI summary, a security doc IT can skim, pricing the CFO can see without booking a call. Build for the forward, not the meeting.
One persona can’t carry a whole buying committee, though. When the user and the check-signer are different people, you need both cards on the wall — that split is the subject of buyer personas vs. user personas, and the full committee treatment lives in our guide to B2B buyer personas.
Example 3: The Service-Business Customer
When a customer can’t judge the work, they judge everything around the work.
“I don’t know what a fair price is. I just don’t want to get burned.”
- Someone who shows up in the window
- A price before the work starts
- A company worth saving in her contacts
- Four-hour arrival windows
- Quotes that grow on site
- Being talked down to
Why this persona works. Rachel’s quote names the real product: certainty. She can’t evaluate a compressor. She can evaluate whether the technician texted before arriving, whether the price on the invoice matched the price on the phone, whether anyone explained the problem without the eye-roll. The persona turns “provide great service” into a checklist an owner can run on Monday morning.
Her price anxiety isn’t a niche trait — it’s the most documented behavior in commerce. In Baymard Institute’s checkout research, surprise extra costs are the number-one reason shoppers abandon a purchase, cited by 39% of users. The instinct travels offline intact: a quote that grows on site is a surprise fee with a clipboard. The persona tells this business to publish flat diagnostic pricing and watch conversion move.
And the “loyal after one good job” tag reframes the economics. Rachel isn’t a $180 service call. She’s fifteen years of maintenance, referrals, and a water heater in 2031 — if the first visit earns the contact-book save.
Example 4: The Nonprofit Donor
Donors don’t leave because they stopped caring. They leave because nobody treated them like they mattered.
“I can’t fix everything. I can make sure a family eats this week.”
- Give monthly without it pinching
- See where the money lands
- Feel like a partner, not a wallet
- Forms that nudge her toward $100
- Silence until the next ask
- Impact reports written for boards
Why this persona works. Evelyn is the donor most fundraising decks skip — she’s not a major gift, so she’s invisible. The persona makes her visible, and the math backs it up. In the M+R Benchmarks study of nonprofit fundraising, about 71% of monthly donors are still giving a year later, versus roughly 24% of new one-time donors. Evelyn’s $25 a month, kept for a decade, beats a long parade of one-off $100 gifts — and costs almost nothing to keep.
Every frustration on the card indicts a common practice. The preset-amount nudge tells her that her gift is too small. The silence-then-ask cadence tells her she’s an ATM. The board-speak report tells her the story wasn’t written for her. Fix those three and retention moves — no gala required. Her quote hands the copywriter the whole voice: concrete, modest, one family at a time.
Build a persona right now — free, no signup
You just read four. Yours takes about ten minutes. Name, goals, frustrations, one honest quote.
Open the free persona creator →The Four, Side by Side
Different industries, same skeleton. Put them in one table and the pattern shows itself.
| Persona | Context | Core Goal | Breaking Point | What the Team Does About It |
|---|---|---|---|---|
| Maya Torres | B2C fitness app, shift worker | A workout that fits a chaotic schedule | Guilt-based notifications | Adaptive 25-minute sessions; value before paywall |
| Dan Okafor | B2B ops software buyer | Three departments at yes, zero drama | Pricing behind a sales call | Forwardable proof: ROI one-pager, visible pricing |
| Rachel Kim | HVAC customer, first emergency | Certainty about price and arrival | The quote that grows on site | Flat diagnostics; arrival texts; plain explanations |
| Evelyn Marsh | Recurring nonprofit donor | Steady giving that visibly helps | Silence until the next ask | Impact notes for humans; protect the modest gift |
What Makes These Examples Work
A persona is finished when someone can make a decision with it. Not before.
Every line points at an action. Maya’s schedule → adaptive sessions. Dan’s committee → forwardable collateral. Rachel’s price fear → flat diagnostics. Evelyn’s loyalty math → retention over acquisition. Read any line on any card and you can name the meeting where it settles an argument.
Behavior leads, demographics follow. Age and city appear once, in small type, for context. The headline is always what the person is trying to do and what stands in the way. Two 36-year-olds in Raleigh can want opposite things; two wary first-timers never do.
The quotes sound recorded, not written. “I just don’t want to get burned” is something a human said. If your persona’s quote would look at home on a billboard, take it back to the interview notes and find the sentence someone actually muttered. Good raw material comes from good questions — we keep a working list of persona interview questions for exactly this.
Each one picks a fight. Maya argues against the notification strategy. Dan argues against gated pricing. Evelyn argues against the gala budget. A persona everyone nods at and nobody argues about is wallpaper. The useful ones cost somebody a pet project.
The Anti-Patterns to Avoid
Bad personas aren’t neutral. They give a team confidence in a user who doesn’t exist.
The demographic dossier. “Sarah is 29, lives in Brooklyn, earns $78K, drives a Civic.” A census entry with a headshot. It says everything about who someone is and nothing about what they do.
The wish-fulfillment persona. Unlimited budget, quick decisions, delighted by exactly the features you already shipped. That’s not a persona. That’s a mirror.
The novel. Six pages, a childhood backstory, a Myers-Briggs type. Nobody read it last quarter and nobody will read it next quarter. Everything above fit on a card; yours can too.
The confident guess. Right structure, zero research. It feels true, which makes it dangerous — the team acts on it with conviction. If you haven’t interviewed anyone yet, that’s fine: build a proto-persona, label it as assumption, and let it tell you what to go verify. Nielsen Norman Group’s breakdown of the three persona types is useful here — lightweight, qualitative, statistical. Each is honest work at a different budget. Pretending one is another is the only real sin.
Steal the Structure, Not the People
Your users are not Maya, Dan, Rachel, or Evelyn. Don’t copy them. Copy the bones:
- One archetype line that names the pattern (“the wary first-timer”), so the team has a handle.
- Three goals, three frustrations — each specific enough to argue with.
- One quote a real person could have said on a bad day.
- Traits as tags, not paragraphs.
- A “so what” — if you can’t write two paragraphs on what the persona changes, it isn’t done.
Want the skeleton ready-made? Grab the free persona template, or skip the blank page entirely and build a persona right now — free, no signup. When you’re ready to do it properly, research and all, the full walkthrough is how to create a user persona.
Frequently Asked Questions
What should a user persona include?+
A name and short context line, one primary goal, two or three specific frustrations, observable behaviors, a quote that sounds like a real person, and a handful of traits. One page. Every detail should inform a decision — if it doesn’t, cut it.
How many user personas does a team need?+
Most products need two to four. One persona means you haven’t looked hard enough at how differently people use you. Seven means you’re slicing too thin and nobody will remember any of them.
What’s the difference between a user persona and a buyer persona?+
A user persona describes the person who uses the product day to day. A buyer persona describes the person who approves the purchase. In B2C they’re often the same human. In B2B they usually aren’t — Dan above is a buyer; his dispatchers are the users. The full comparison: buyer vs. user personas.
Can I copy a persona example for my own product?+
Copy the structure, never the content. Examples set a standard of specificity to hit. Your users have their own breaking points — you find those by talking to them. No research yet? Start with a proto-persona and label it as an assumption.
Do user personas need demographics?+
Only when a demographic changes a decision. Maya’s night shifts shape when she can work out — that stays. Her taste in music changes nothing — that goes. If you’re defining an audience for targeting rather than understanding, you may want an ICP instead; see persona vs. ICP.