User Persona Template
Build a structured persona card with goals, frustrations, and a behavioral profile. Align your team around a shared picture of your target user before making product decisions.
Use this templateWhat you get
- Header with avatar, name, role, and quote
- Three-column layout: Goals, Frustrations, and Profile
- Color-coded item cards for quick scanning
What this template is for
A user persona template gives your team a shared, human reference point for every product decision. This template structures the essentials — name, role, quote, goals, frustrations, and behavioral profile — into a single card your team can reference in design reviews, sprint planning, and stakeholder presentations. Fill in one persona per key user segment to keep product decisions grounded in real user needs.
When to use this template
- Kick off a discovery sprint by aligning the team on who the primary user actually is.
- Anchor a design review around a specific persona so feedback stays relevant to user needs.
- Onboard a new team member with a clear picture of the target audience.
- Reduce scope creep by asking 'does this feature serve our persona's goals?' before adding it.
- Present user research findings to stakeholders in a format they can scan in under a minute.
How to use it
- 1Start with one real user segment you have research data for — avoid building a persona from assumptions alone.
- 2Fill in the header: name, role, age range, and location give the persona a human identity.
- 3Write the quote as a single sentence in the user's voice — it should capture their biggest motivation or frustration.
- 4List three to five goals that represent what this user is trying to accomplish, not product features.
- 5List three to five frustrations your product should address — these become your design constraints.
- 6Add a brief profile: background, tools they use today, and one behavioral pattern that shapes how they work.
Quick example
B2B SaaS product manager persona
How it compares to similar tools
User persona vs. buyer persona
A user persona represents someone who uses the product day to day; a buyer persona represents someone who decides to purchase it. In B2C they are usually the same person. In B2B they often differ: the user is the engineer on the team, the buyer is the engineering director or procurement. Both matter — design for the user but sell to the buyer.
User persona vs. user segment
A user segment is a statistical group ('SMB customers under 50 employees'). A user persona is one specific imagined person from that segment, with a name, role, goals, and frustrations. Segments describe the market; personas put a face on it so the team can ask 'what would Sarah think of this'. Both are useful — segments for marketing, personas for product decisions.
User persona vs. JTBD (Jobs To Be Done)
JTBD focuses on what users are trying to accomplish, not who they are. A JTBD statement reads 'When [situation], I want to [motivation], so I can [outcome]'. Personas focus on the person; JTBD focuses on the job. Many teams now use JTBD for product decisions and reserve personas for marketing and design empathy — they are complementary rather than competing.
Common mistakes to avoid
Demographics without behavior
'Sarah, 34, marketing manager, lives in Brooklyn' is a stock photo, not a persona. What does Sarah actually do at work, what tools does she use, what frustrates her, what does success look like in her role? Behavior, goals, and pain points matter — age and location rarely do unless the product is genuinely demographic-sensitive.
Too many personas
If you have eight personas, you have zero — the team cannot keep them in mind. Limit to 2-4 primary personas and 1-2 secondary. The discipline of cutting forces clearer thinking about who you are actually building for.
Personas built on assumptions, not research
A persona written in a meeting room without talking to real users is a fictional character that conveniently confirms what the team wants to believe. Base personas on actual interviews, surveys, or behavior data. Mark which parts are validated and which are assumptions — and revisit when you learn more.
Beautiful personas no one uses
Personas printed in a frame on the wall and never referenced in product decisions are decoration. They need to be invoked: 'Would Marcus understand this empty state?' 'Would Priya pay $99 for this feature?' If the product team never says the persona's name in a sprint review, the persona is dead.
Frequently asked questions
What is a user persona?+
A user persona is a fictional representation of a target user, based on research, used to align product decisions around real user needs. A typical persona includes a name, role, goals, pain points, motivations, and a representative quote. The goal is to make 'the user' a concrete person the team can design and discuss for.
How many user personas do I need?+
Most products need 2-4 primary personas representing distinct user groups, plus 1-2 secondary personas for important edge cases. Beyond that, personas dilute focus. If you genuinely serve eight different user types, your product is probably too broad and the personas are masking a positioning problem.
What should a user persona include?+
At minimum: a name, role/title, primary goals, key frustrations, and a snapshot of behavior (tools they use, how often, decision-making style). Useful additions: a representative quote, a typical day, and what success looks like for them. Skip detailed demographics unless the product is age- or location-sensitive.
How do I create a user persona?+
Step one: gather data — interviews (5-8 per segment), surveys, support tickets, analytics. Step two: cluster patterns — who shares similar goals and frustrations. Step three: synthesize each cluster into one persona with a name and details. Step four: validate with stakeholders and revise. Avoid skipping to step three from intuition.
Are user personas still useful?+
Yes, when grounded in research and actively used in product decisions. They have fallen out of fashion compared to JTBD because too many teams created personas based on assumptions and then ignored them. A persona built on real research and referenced in every sprint review is still one of the highest-leverage UX artifacts.
Can I create user personas online for free?+
Yes. Open the CodePic user persona template — pre-formatted with sections for goals, frustrations, behavior, and quotes. Edit directly, export to PNG/SVG, or share a live link with your team. No sign-up required.
Start editing online
Open the template in CodePic, replace the sample nodes, and turn it into your own study board in a few minutes.
See examples: /templates/user-persona/examples
