By Quick answer: What should a user persona template include?
- Core fields — goal, context, behaviour, pains, motivations, constraints.
- Evidence — built from interviews and data, not imagination.
- Quote — a real line from research.
- Count — two or three core personas.
- Use — decisions, not decoration.
Key takeaways
- Personas are summaries of research, not creative writing.
- Behaviour and context predict needs better than demographics.
- Indian personas should capture devices, data, language and payments.
- Proto-personas are hypotheses — label them and test them.
- If no one uses a persona to decide anything, retire it.
Personas get a bad name because many are fiction: "Priya, 28, loves yoga and coffee." Nothing in that helps a designer decide anything. A good persona is a compact summary of research that changes decisions. The Nielsen Norman Group describes personas as a way to make users memorable to the team — when they're grounded in data1.
The template
| Field | What to write | Example prompt |
|---|---|---|
| Name and role | A memorable name and situation | "Ravi, kirana owner in Indore" |
| Goal | What they're trying to achieve | "Get paid faster by regular customers" |
| Context | Where, when, how often | "Busy evenings; between customers" |
| Current behaviour | How they do it today | "Notebook ledger, WhatsApp reminders" |
| Pains | What goes wrong | "Forgets who owes what; awkward follow-ups" |
| Motivations | What drives them | "Cash flow, respect, less hassle" |
| Constraints | Device, data, language, payments | "Budget Android, shared phone, Hindi-first, UPI" |
| Quote | A real line from an interview | "I don't want to ask twice." |
| Evidence | Where this came from | "12 interviews, Indore and Bhopal, Sept 2026" |
Two filled examples
Ravi — the kirana owner
Goal: collect dues without awkwardness. Behaviour: paper ledger, UPI QR. Pains: forgotten credit, chasing customers. Constraints: budget Android, Hindi, intermittent data. Design implications: voice input, Hindi-first UI, automatic UPI reminders, offline ledger.
Ananya — the first-time investor
Goal: start investing safely with small amounts. Behaviour: watches finance videos, asks friends. Pains: jargon, fear of losing money. Constraints: limited time, low trust. Design implications: plain language, small SIP defaults, clear risk explanations, no pressure tactics.
How to build personas from research
The Interaction Design Foundation's overview is a good primer on persona types and uses3.
- Interview 8–15 users per segment — see user interview questions.
- Note behaviours and goals — not just opinions.
- Cluster similar people — by goals and behaviours, not age.
- Check with data — analytics and surveys confirm group sizes.
- Write the persona — using the template, with evidence noted.
- Use it — in design reviews, prioritisation and journey maps.
NN/g distinguishes lightweight, qualitative and statistical personas — choose the level of rigour your decisions need2.
Common mistakes
- Demographics without goals or behaviours
- Personas invented in a workshop and never validated
- Too many personas, none prioritised
- Stereotyped photos and details
- Personas filed away and never used
Put your persona in motion with a customer journey map.
Key terms, defined
Persona — a research-based profile of a user group. Segment — a group of users with shared needs. Proto-persona — an assumption-based draft persona. Behavioural data — what users actually do. Design implication — a decision that follows from a persona insight.
Frequently asked questions
What is a user persona?
A research-based profile representing a key group of users — their goals, behaviours, pains and context — used to guide design and product decisions.
How many personas should I have?
Usually two or three for core segments. More dilutes focus.
What's the difference between a user persona and a buyer persona?
A user persona describes who uses the product; a buyer persona describes who makes the purchase decision. In B2B they're often different people.
What is a proto-persona?
A hypothesis persona based on team assumptions, created before research. Label it clearly and replace it with evidence as research arrives.
Should personas include photos and names?
A name and a neutral illustration help memory. Avoid stereotypes, and keep the focus on behaviour and goals.
How often should personas be updated?
Review them when your market, product or research findings change — at least yearly.
Sources
- Nielsen Norman Group — Personas make users memorable for product team members
- Nielsen Norman Group — 3 persona types: lightweight, qualitative and statistical
- Interaction Design Foundation — Personas
- Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- User interview questions — gather the evidence
- Customer journey map template — put the persona in motion
- Templates & toolsCustomer journey map template: stages, lanes, a filled food-delivery example and how to run a mapping sessionA customer journey map template with stages and lanes, a filled food-delivery app example, how to run a mapping session and how to turn pain points into fixes.
- Templates & toolsCompetitor analysis template: how to analyse rival apps, with a scoring grid and a worked exampleA competitor analysis template for apps and startups: who to include, a scoring grid, UX teardown prompts, review mining and a worked example.
- Templates & tools50 user interview questions that uncover real problems — grouped by goal, with the questions to avoid50 user interview questions for discovery and usability research, grouped by goal, with a simple script and the leading questions to avoid.
- How to make an appHow to build an app with AI in one weekendA Friday-to-Sunday plan to build a working app with AI tools — pick the tool, write the brief, prompt in small steps, test with users and check security.
- Templates & toolsApp cost calculator: estimate your app development budget in India in four stepsA free app cost calculator for India: pick your app type, platforms, design and team to estimate a build budget, plus GST and yearly running costs.
- Templates & toolsFree product roadmap template: the Now–Next–Later format, with examples and how to run itA free product roadmap template in the Now–Next–Later format, with a filled example for an app, how to tie items to outcomes, and mistakes to avoid.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
Evidence helps more.
A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.