Plug, Play, Persona: A one-page persona template and step-by-step guide

# What this guide delivers

This guide explains a compact persona format and a step-by-step process for turning research into a practical, one-page persona your team will actually use. It rejects long demographic-heavy profiles and focuses on the elements that influence decisions: name, photo, key behaviors, roles, context of use, and obstacles.

# Why small personas work

Large persona reports are rarely read and rarely used. A single-page persona is fast to scan, easy to remember, and more likely to appear in day-to-day conversations. The guiding rule: every item on the page must have a clear purpose for design or business decisions. If a detail doesn't change what you build or how you prioritise, leave it out.

# The one-page template: what to include

• Name and photo: Choose a natural name that fits the context so teammates ask "What would Helena want?" Use real participant photos when available or context-appropriate action shots.
• Minimal demographics: Include only age, occupation, location, education, or family status when those specifics affect behavior with your product.
• Roles: List the different roles the person occupies during their interactions (for example: customer, guest, remote worker). Different roles surface different needs and priorities.
• Context of use: Describe where, when, and why the person interacts with the product or service.

• Key goals and motivations: Short, action-oriented goals tied to measurable outcomes.
• Decision-driving insights: One or two bullets that tell the team what to stop assuming and what to prioritise.

# How to build a persona now

1. 1Start with research you already have: interviews, support logs, analytics, and field observations.
2. 2Pick behaviors and pain points that directly influence feature decisions. Exclude neutral demographics unless they change behavior.
3. 3Give the persona a realistic name and choose a photo that matches the context (action shot preferred).
4. 4Map roles and how priorities shift across them so you design a unified journey that covers transitions.
5. 5Write one or two compact insights that state what the team should build or test next.

# Photo guidance and authenticity

Real participant photos create the strongest empathy. When you cannot use participant photos, use an image that matches the persona's environment — a teacher in a classroom, a restaurant owner in their kitchen — instead of a generic posed portrait. Action shots reveal tasks and pressures better than staged headshots.

# Demographics: use them sparingly

# Roles: map behavior shifts, not labels

List the different identities a person assumes during a journey. Each role may require distinct features or information. Mapping transitions prevents building separate fragmented experiences and helps you create a single service that anticipates changing needs.

# Immediate outcomes

A minimal persona helps teams make faster decisions, run targeted experiments, and focus product work on problems that matter to real people. Because it's short and actionable, it's more likely to be referenced in planning, design reviews, and stakeholder conversations.