User Persona Template (UX Research)
A one-page user-persona card — name, archetype, demographics, a representative quote, goals, pain points, behaviors, and motivations — to align teams on who they are designing for.
Live preview
USER PERSONA +-----------------+ | | | [ PHOTO ] | Maya Chen — "The Time-Starved Team Lead" | | Age 34 · Marketing manager at a 50-person SaaS company | (paste a | Austin, TX (hybrid) · Tech: High | photo) | +-----------------+ "I do not have time to learn another tool — it has to show me value in the first ten minutes or I am gone." ABOUT Maya runs a small marketing team and owns the number for pipeline. She juggles five tools, lives in Slack and her calendar, and evaluates new software between back-to-back meetings. She is the buyer and the daily user. GOALS (what success looks like for them) - Prove marketing's impact on revenue to leadership - Ship campaigns faster with a small team - Consolidate tools and reduce busywork - Look competent and in-control in front of the CEO PAIN POINTS (what frustrates them today) - Reporting takes a full day every month, by hand - Tools that need a sales call and a long setup - Data scattered across five disconnected apps - Getting blamed for results she cannot fully measure BEHAVIORS (how they actually act) - Researches on mobile, buys on desktop - Trusts peer reviews (G2, Reddit) over vendor claims - Abandons signup flows that ask too much up front - Prefers self-serve trials to demos MOTIVATIONS (what drives them) - Career growth and credibility - Efficiency — hates wasted effort - Autonomy — wants to try before talking to sales CHANNELS (where to reach them) LinkedIn, marketing newsletters, peer Slack communities, G2 Note: personas are evidence-based composites of real research, not invented individuals. Keep this card to one page and update it as you learn more.
About this template
A user persona is a one-page, evidence-based portrait of a target user that gives a whole team a shared, memorable answer to "who are we building this for?" Done well, it stops the most expensive failure mode in product and marketing: everyone quietly designing for a slightly different imagined user. The components that make a persona useful are not the demographics — age and location are the least important part — but the **goals, pain points, and behaviors**, because those are what your product actually has to serve. A representative **quote** captures the persona's mindset in their own voice and is often the single most-remembered element. The fields that earn their place: an archetype/tagline ("The Time-Starved Team Lead") that makes the persona instantly recallable; goals framed as what success looks like for them; pain points that describe today's frustrations you can relieve; and behaviors (how they research, buy, and use tools) that drive real design and funnel decisions. The cardinal rule — and the reason this template ends with a reminder — is that **personas must be grounded in research** (interviews, surveys, support tickets, analytics), not invented at a whiteboard; a made-up persona just encodes the team's existing biases with a stock photo on top. Build three to five personas at most, give each a clear primary, and treat them as living documents you revise as you learn. Use them to align design and engineering, prioritize features against real goals, write copy in the user's language, and brief new team members fast.
When to use it
- Kicking off product, UX, or marketing work and aligning the team on the target user.
- Synthesizing user interviews, surveys, or support data into a shareable summary.
- Prioritizing features or messaging against a specific user's goals and pains.
- Onboarding new teammates to "who we build for."
What to include
- A memorable name and archetype/tagline (kept fictional).
- Light demographics: age, role, location, tech savviness.
- A representative quote in the user's own voice.
- Goals, pain points, and behaviors — the parts that drive decisions.
- Motivations and channels; a note that personas are research-based composites.