User Persona Markdown Template
Synthesize user research into behaviors, context, jobs to be done, needs, barriers, evidence, and confidence without demographic stereotypes.
# User Persona: [Behavior-Based Segment Name]
**Prepared by:** [Name or team]
**Last reviewed:** YYYY-MM-DD
**Confidence:** [High / Medium / Low]
## Research basis
- **Sources:** [Interview study, observation, analytics, support themes, or survey]
- **Research period:** [Dates]
- **Participants or records:** [Count and relevant sampling context]
- **Known gaps:** [Who or what may be underrepresented]
## Context and behavior
- **Situation:** [When and where this pattern appears]
- **Current approach:** [What people do today]
- **Constraints:** [Time, access, policy, knowledge, or environment]
- **Relevant tools or channels:** [Only if supported by research]
## Job to be done
> When [situation], I want to [job], so I can [desired outcome].
## Needs and desired outcomes
- [Need or outcome] - Evidence: [Source] - Confidence: [Level]
## Barriers
- [Observed barrier] - Evidence: [Source] - Confidence: [Level]
## Decision factors
- [Factor that affects choice or behavior]
## Representative evidence
- "[Anonymized research quote or observation]" - [Source reference]
## Product implications
| Evidence-backed insight | Possible response | Assumption to test |
| :--- | :--- | :--- |
| [Insight] | [Design or product implication] | [Open assumption] |
## Review triggers
- Revisit after [new study, product change, market change, or date].
User Persona: [Behavior-Based Segment Name]
Prepared by: [Name or team]
Last reviewed: YYYY-MM-DD
Confidence: [High / Medium / Low]
Research basis
- Sources: [Interview study, observation, analytics, support themes, or survey]
- Research period: [Dates]
- Participants or records: [Count and relevant sampling context]
- Known gaps: [Who or what may be underrepresented]
Context and behavior
- Situation: [When and where this pattern appears]
- Current approach: [What people do today]
- Constraints: [Time, access, policy, knowledge, or environment]
- Relevant tools or channels: [Only if supported by research]
Job to be done
When [situation], I want to [job], so I can [desired outcome].
Needs and desired outcomes
- [Need or outcome] - Evidence: [Source] - Confidence: [Level]
Barriers
- [Observed barrier] - Evidence: [Source] - Confidence: [Level]
Decision factors
- [Factor that affects choice or behavior]
Representative evidence
- "[Anonymized research quote or observation]" - [Source reference]
Product implications
| Evidence-backed insight | Possible response | Assumption to test |
|---|---|---|
| [Insight] | [Design or product implication] | [Open assumption] |
Review triggers
- Revisit after [new study, product change, market change, or date].
When to use this template
Use this after interviews, observation, analytics, or support research reveal a meaningful behavior pattern. It can help teams discuss needs without treating one participant as an entire market.
Section guide
- Research basis
- Make sources, recency, sample boundaries, and confidence visible.
- Context and jobs
- Describe what users are trying to accomplish and under which conditions.
- Evidence and implications
- Separate observed patterns from product assumptions.
How to use this template
- 1
Copy the Markdown
Click the Copy button above to put the full template on your clipboard.
- 2
Paste into your editor
Paste into the mdkit editor, a repository, a notes app, or another Markdown editor. Check tables and task lists in your target renderer because Markdown support varies.
- 3
Fill in your content
Replace bracketed examples with verified information, adapt fields to your context, and remove sections that do not apply.
- 4
Check before you use it
- A persona is a provisional synthesis, not a real individual or a substitute for continued research.
- Include demographic attributes only when evidence shows they are relevant to the use case; avoid unnecessary photos and stereotypes.
Template details
What it solves
A research-based persona makes recurring user contexts and jobs discussable while showing where evidence is strong, weak, or missing.
Key features
- Research sources, recency, and sample caveats
- Behavior and context rather than decorative demographics
- Jobs-to-be-done statement and desired outcomes
- Evidence, confidence, and product implications
Pro tips
- >Use a neutral segment label instead of inventing a lifelike biography.
- >Attach source references to important claims.
- >Set a review trigger when new research contradicts or expands the pattern.
Useful Markdown tools
Start in the Markdown editor, then use a relevant tool when you need to format or export the finished document.
Related templates
Product Requirements Document (PRD)
Define a product problem, users, goals, scope, requirements, acceptance criteria, metrics, dependencies, risks, rollout, and open questions.
SWOT Analysis
Assess strengths, weaknesses, opportunities, and threats with evidence and priority, then turn findings into testable strategic actions.
Literature Review
Plan and write a true literature review with scope, search method, synthesis matrix, themes, debates, methods, gaps, conclusion, and bibliography.