In 30 seconds
- A persona represents a group of users with similar goals.
- Built from research, not guesswork.
- Used to make decisions and write better user stories.
What goes in a persona
- Name and short description
- Goals and motivations
- Frustrations and pain points
- Context: where, when and how they use the product
- Skills and constraints that matter
Building one
Alan Cooper introduced personas for software design in his 1999 book The Inmates Are Running the Asylum. Base them on interviews, observation and data. Three to five personas usually cover a product's main users.
Using them in agile
- Write user stories for a named persona instead of "a user"
- Check new ideas against each persona's goals
- Map each persona's experience with journey maps
Myth vs reality
Myth · Personas are made-up characters.
Reality · Good ones are grounded in research.
Myth · More personas is better.
Reality · Too many dilutes focus; pick the primary ones.
Myth · Demographics are the key detail.
Reality · Goals and behaviours matter more than age or job title.
FAQ
How often should personas be updated?
When research shows users or their needs have shifted.
Can we start with proto-personas?
Yes, as assumptions to validate quickly.
Who uses personas?
The whole team, not just designers.