Guide6 min readUpdated
What Is a User Persona? Example, Template and Uses
What is a user persona? A plain explanation with a user persona example, a simple persona template and when a small project can skip one.
By Tithi Mondal, UI/UX Designer
Suppose a founder in Kolkata says her app is "for everyone who wants to learn". Then someone asks a simple question: who is the one student who opened the app last night? She has no answer. A user persona gives you that answer.
A user persona is a short profile of one typical person who will use your product, based on what you know about your real customers. It has a name, a situation, a goal and a few problems. It turns a vague crowd into a person you can design for.
What is a user persona, and what is it not?
A user persona is a made-up but realistic character that stands for a group of real users. The character is built from facts you collected, such as interviews, enquiries, WhatsApp chats and sales records. The name and photo are invented. The needs are not.
A persona is not a guess about "women aged 25 to 40". Age and city alone do not tell a designer what to build. A persona is also not a marketing fantasy of your dream customer. It describes the real person who shows up today.
You may also hear the words customer persona or target user. A customer persona is usually about who buys. A target user is about who uses the product. In many apps these are two different people, and each may need a persona.
What does a user persona example look like?
A useful persona fits on one page and talks about behaviour, not only facts. Here is a hypothetical example for a coaching app aimed at students in a small town.
Rina, 17, Class 12 student in a district town. She uses a shared family Android phone with a small amount of storage. Mobile data is limited, so she watches videos on her father's Wi-Fi in the evening. She studies in Bengali, and reads English with effort.
Goal: finish the physics syllabus before the board exams without travelling 40 minutes for tuition.
Frustrations: videos that stop to load, long English sign-up forms, and no way to ask a doubt without paying again.
Habits: studies from 8 pm to 10 pm, shares notes on WhatsApp, pays with UPI from her mother's account.
What this means for design: the sign-up should need only a phone number and an OTP. Lessons should download over Wi-Fi and play offline. The first screen should be in Bengali. Payment should work through UPI collect or a QR.
Notice the last part. A persona is only useful when it ends in decisions. Rina's page produces four product rules in one minute.
Why does a user persona matter for a business owner?
A persona helps you spend money on the right features, because every idea can be tested against a real person. When someone says "let us add a social feed", the team asks: would Rina use this at 9 pm on a shared phone? If not, the feed waits.
This saves design cost. Each extra screen costs time, and a designer works from the number of screens and user roles. You can read how that affects price in my guide on UI/UX design cost in India. A persona stops you from paying for screens that nobody needs.
A persona also ends internal arguments. Without a persona, the loudest opinion wins. With a persona, the team has a shared reference. It also helps new team members and freelancers understand the audience in 5 minutes. For first-time and low-confidence users, read designing for first-time internet users.
How do you make a user persona step by step?
You make a persona by gathering facts about real users, finding patterns, and writing one short profile per pattern. Most small teams can finish in 1 to 2 days.
- Collect real facts. Use customer calls, WhatsApp messages, support questions, order history and reviews. If you have none, talk to 5 people who match your audience. My guide on user research for startups shows how to do this cheaply.
- Look for patterns. Note repeated goals, devices, languages and problems. If three people say they pay only by UPI, that is a pattern.
- Group the people. Make two or three groups. Do not make ten.
- Write one profile per group. Use the template below.
- Add a decision line. For each persona, write 3 or 4 design rules.
- Check it against real people. Show the persona to a customer. Ask: does this sound like someone you know?
- Update it. When your customers change, the persona should change.
A simple persona template
You can copy this list into a document or a slide.
- Name and role: an invented first name and one line, such as "shop owner in a tier-3 town".
- Situation: where they are, what device and network they use, what language they read.
- Main goal: what they want to finish, in one sentence.
- Frustrations: 2 or 3 things that stop them today.
- Habits: when and how they use similar tools, including WhatsApp and UPI.
- Design rules: 3 or 4 decisions that follow from the above.
What should a good persona contain?
A good persona contains real behaviour, one clear goal and a few design rules, and it is short enough that people remember it. If a persona needs three pages, nobody will read it.
Check these points.
- It is based on real conversations or data, not on assumptions.
- It names a goal, not only a description.
- It includes device, network and language, because these shape Indian app design more than age does.
- It describes frustrations in the person's own words where possible.
- It leads to decisions you can use on a screen.
What mistakes make personas useless?
The biggest mistake is writing a persona from imagination and then treating it as fact. That gives you a confident story with no evidence behind it.
- Too many personas. Five personas means the team follows none of them. Two or three is a good limit.
- Stock details that change nothing. "Loves coffee and travel" does not affect any screen.
- Mixing the buyer and the user. A school owner pays. A teacher uses the app. Make both if both matter.
- A persona for "everyone". If the profile fits every person, it fits no one.
- Filing it away. A persona on a shared drive that nobody opens does nothing. Put the one-line goal at the top of every design discussion.
- Ignoring edge users. A person with weak eyesight or a very old phone may need extra care. See designing for low-end phones and slow networks.
Can a small project skip the persona?
Yes, a small project can use a very short persona or skip it. If your site has one page, one audience and one action, such as a salon booking by WhatsApp, a 5 line description of your typical customer is enough.
You should still make a persona when the product has several user roles, such as buyer, seller and admin. A marketplace app is a good case. On the seller app I designed for a marketplace in Tanzania, the people selling and the people verifying sellers had very different needs, so each role had to be thought through separately.
A persona also helps most when the audience is new to you. If you are building for farmers, patients or students you have not met, a persona based on a few real conversations will save you from wrong guesses.
If you want help turning customer conversations into clear screens, you can read about my UI/UX design service or get in touch through the contact section.
Frequently asked questions
What is the difference between a persona and a target audience?
A target audience is a broad group, such as students in small towns. A persona is one realistic person from that group, with a goal, a device and real frustrations.
How many user personas do I need?
Most small products need two or three. More than that and the team stops using them.
Can I make a persona without user research?
You can, but it will be a guess. Even 5 short conversations with real customers will make the persona much more reliable.
Should a persona include a photo and a name?
A name helps the team talk about the person. A photo is optional, and it should be a neutral image, not a stereotype.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.