Personas help me keep users front of mind. But, they work best when they focus on what people need to do, the questions they ask, and what might stop them. In this deep dive I define personas, explain why traditional demographic customer personas often fail, and walk through how to create functional personas you can use on real projects.
What Are Personas
I use personas as concise summaries of user groups. Classic write‑ups lean on age, job title, lifestyle and hobbies. That helps with tone and brand, yet it rarely tells you how to improve a flow or remove friction. Functional personas flip the model. They describe goals, tasks, questions and objections that appear during a journey. That shift makes personas practical for my UX and CRO work where outcomes matter.
Quick definition
A functional persona is a task‑led profile that lists goals, key questions, pain points and objections tied to a specific job(s) to be done.
If you came here to learn the basics, that covers the heart of defining personas. Everything that follows shows how to put them to work.
Why Demographic Customer Personas Fall Short
Customer personas that focus on demographics sound like a good idea. But, they age fast, demand constant research and rarely help you fix a form, a message or a checkout. They also encourage debate about the person rather than the task. I have sat in meetings where teams argue about whether our buyer is 35 or 42. None of that helps the user get a quote, find a price or trust a claim.
When a persona is built around tasks and doubts, the team talks about evidence. We ask what proof the user needs, which step feels slow, and what content removes risk. That is how personas drive better journeys and higher conversion.
Functional Personas Explained
Functional personas shift attention from who users are to what they need to get done. Start with the top jobs. Map the questions people ask at each step. Add the pain points that block progress. Capture the objections that stall commitment. Then decide what proof, reassurance or features remove those blockers. Because this model mirrors how work happens, it stays current for longer and becomes easy to maintain.
Exactly what you include in your personas will depend on your circumstances. But, I typically focus on:
- Goals and tasks the person wants to complete
- Key questions that appear during the journey
- Pain points that cause delay or doubt
- Objections the person might raise
- Who or what influences them
- How we could support this audience better
That said, it is important to adapt to the organization or project. For example, below you can see a persona I created for Network Rail that has a slightly different approach that was appropriate for their organization.
How To Create Personas the Functional Way
The workflow below is the fastest way I know to create personas and keep them fresh. It uses AI to speed research, yet it still relies on your judgment. Follow the steps in order.
1. Create a repository of research
Set up a single project space to store research, transcripts and other information you have on users. A Notion database or a simple folder works, but I tend to favor adding it all into a project in ChatGPT. This will inform the AI’s research.
2. Gather existing research
Gather what you have on users. Pull surveys, analytics, support logs and search data. Even rough notes help. Add that to your repository. Use interview transcripts, call logs and live chat history if you have it. Collect real phrases people use when they describe problems. Tools like Dovetail and Aurelius make this easier, though a spreadsheet also works.
3. Identify and plug gaps
Identify any glaring gaps that you really feel must be filled and carry out additional research as required. If you need a quick refresher on gathering evidence, read the GOV.UK guide on user research and the Nielsen Norman Group primer on personas.
4. Ask AI to carry out online research
Ask AI to carry out deep research into any mention of your brand online. Ask it to identify any questions asked, objections mentioned and other related insights. Add the report it produces to your repository.
5. Ask AI to propose segments
Ask AI to look at all of the data that you have gathered as well as its own research and identify segments based on need (not demographics). This is how you build personas that help design decisions. If you need a second lens, borrow the jobs to be done model. Intercom has a template you can use.
6. Ask AI to generate your personas
Ask AI to generate the first draft of each segment. Use a simple template with the six bullets above. Produce one page per persona. Keep language plain and testable. If a claim cannot be tied to a user quote, a data point or a session replay, mark it as an assumption.
7. Validate your personas and refine
Validate with users if possible. Otherwise speak to people who talk to customers. Sales and support hear the raw truth every day. Have them mark what feels right and what feels off.
Refine the personas based on the feedback you have gathered.
8. Make your personas easily available
Publish in a place the whole team can find. Link each persona to journeys, patterns and components so the work stays connected. If you maintain a design system, add a short section on how each persona behaves at key steps.
That workflow creates useful UX personas in hours not weeks. More important, it sets you up to maintain them with a light touch.
Easy To Say, Harder To Do
I realize that the above steps are much harder to do in practice than I make it sound here. However, this article is long enough as it is!
If you need help producing your personas, get in touch. I will happily walk you through the process or take the work on myself if you like.
Using Personas in Real Work
Personas only help when they change what we design, write or prioritize. Tie each persona to a key flow such as quote, booking or checkout. Map questions to specific screens and messages. Place proof near the moment of doubt. Keep the changes small and focused so you can measure impact.
Here is a simple way I use personas during delivery.
- Write copy that answers the persona question on the same screen
- Place reassurance near likely objections such as price, security or timing
- Add smart defaults that speed the main task
- Use progressive disclosure for advanced choices
- Track impact with task completion, support contact reasons and conversion on key CTAs
Connect this work to your research and testing practice. Run short usability tests with people who fit the tasks in each persona. Pair that with analytics and session replays. When a change helps the task, keep it. When it does not, roll back and try the next idea. For a refresher, scan these primers on usability testing, analytics for UX and microcopy for trust.
How Many Personas Do You Need
Less than you think. Three to five is normal on a project. If you have more, you probably listed roles rather than needs. Merge segments that follow the same journey and share the same doubts. Create variants only when the tasks or objections diverge in a way that changes design or content.
How To Keep Personas Alive
Stale personas are a common failure. Set a light maintenance rhythm so the work stays useful.
- Store evidence in a research repository so updates are easy to make. A shared folder works. A tool helps at scale.
- Tag notes by task or objection rather than by project. That makes cross‑project patterns visible.
- Add a change log to each persona and keep edits short and dated
- Review personas when a product, policy or price changes
- Archive personas that no longer map to a journey
This is the boring part that protects quality. It is also how you show the use of personas to stakeholders who ask whether personas are worth the effort.
Customer Personas vs UX Personas
People use these phrases in different ways, so here is how I separate them in practice. Customer personas often describe market segments and brand tone. UX personas focus on the tasks and objections that shape interfaces. You can keep both if they serve different jobs. If you have to pick, keep the ones that drive decisions in the product or service.
Common Mistakes When Teams Create Personas
I see the same traps on most projects. Avoid these and the work gets easier.
- Writing long backstories that no one reads
- Treating personas as a one‑off deliverable rather than a living asset
- Letting demographics drive structure rather than tasks and doubts
- Creating personas without evidence from research or analytics
- Skipping validation with sales and support
- Forgetting to tie personas to journeys, screens and CTAs
If any of these sound familiar, revisit the earlier workflow and trim the scope. Small, accurate and useful beats big, vague and ignored.
Frequently Asked Questions About Personas
This short FAQ answers common questions I hear when teams start to build personas.
What are personas used for
Use personas to align teams, guide content and support design decisions. They keep conversations focused on tasks and evidence rather than hunches.
How do I define personas without much research
Start with what you have. Pull analytics and support logs. Draft lightweight personas built around tasks and objections. Mark assumptions. Validate with three to five quick user tests and update the documents.
How many examples of personas should I include in a deck
Two or three is enough. Pick the ones that cover the most critical journeys. Keep them to one page each so the audience stays with you.
Are demographics useless
No. Demographics can inform tone and channel choice. They do not help you fix a form field or design a flow. Use them as garnish, not the main course.
Can AI create personas on its own
AI can draft, cluster and summarize. It cannot replace your judgment. Feed it evidence, ask for tasks and objections, then verify with research.
Do personas help conversion
Yes when you link them to journeys, messages and proof. Track a small number of metrics for each persona such as task completion, support contact reasons and conversion on one key CTA.
Putting Personas To Work Today
Ready to build personas that help the team make better choices? Start with one flow that matters this quarter. Draft two functional personas that match that journey. Use them to guide microcopy, structure and reassurance. Publish small updates, measure the result and iterate next week. That is how personas become part of normal delivery rather than a dusty PDF.
If you want more detail, these resources are worth a look. They cover research, journey mapping and content that removes doubt.
- NNG on User Journeys
- GOV.UK on Content Design
- Hotjar for Behavior Monitoring and Feedback
- User Interviews on Recruiting
- Card Sorting for IA
- Empathy Mapping
Final Thoughts and a Simple Template
Copy this starter and adapt it to your product. Keep it to one page so teams will use it.
Functional Persona Template
- Persona type (e.g. regular buyer)
- Name (e.g. John Smith)
- Summary (An at a glance summary of the person)
- Quote: (Ideally a real user quote that sums up the personas attitude)
- Key questions
- Goals and Pain points
- Tasks
- Likely objections
- Who or what influences them
- How we could support this audience better
It feels like to some extent personas have fallen out of favor. However, I would argue that is only because they are rarely done right. Personas can be incredibly valuable if they include the right information and are produced in a fast, lightweight way. That is what functional personas provide.
