30 Second Overview
User personas help teams build the right thing for the right people.
Without them, products are based on assumptions, leading to low adoption or poor UX. When grounded in research and used consistently, personas drive clarity, empathy, and smarter decisions across the product lifecycle.
1: Personas: What Success Looks Like
- Your personas are based on real user research and updated regularly.
- Teams use personas during prioritisation, design, and validation.
- Personas represent both demographics and behavioural insights.
- Cross-functional teams refer to personas in decision making.
- New features are evaluated against persona needs and behaviours.
2: Personas Case Study
“Meet Alex, a frequent solo traveller in his 30s, who values affordability and cultural authenticity.”
Airbnb used such personas to move beyond booking transactions and design for immersive travel experiences.
3: Personas: Step-by-Step How To
- Conduct qualitative and quantitative user research.
- Identify key user segments based on behaviour and needs.
- Create clear, concise persona documents (include goals, pain points, behaviours).
- Share and socialise across teams; keep the personas accessible.
- Validate and refine personas as you learn more from the market.
4: Persona Checklist
- Personas exist and are documented
- Personas are based on actual research, not internal assumptions
- They include goals, behaviours, and pain points
- Personas are used in prioritisation and design
- Accessible and regularly updated
5: Persona Pitfalls (and How to Avoid Them)
| Pitfall | Avoidance Strategy |
| Assumption-based personas | Base them on actual research and interviews |
| Too generic or too many personas | Focus on 2–4 key personas that drive the majority of usage |
| Not used after creation | Embed personas into rituals like planning and design reviews |
| Treating them as UX-only tools | Use personas in strategic and roadmap decisions |
6: Personas FAQ
What’s the ideal number of personas?: Typically 2–4 per product. Enough to capture variation, not so many they dilute focus.
How often should we update personas?: Annually, or when entering a new market or launching a major new feature.
Who creates personas?: Led by product managers or UX researchers, but validated with data and cross-functional input.
Do B2B teams need personas?: Yes. B2B personas should include roles, buying motivations, and usage goals.
