A research-based fictional character that represents a key segment of users, defined by their goals, behaviors, needs, and context. Personas give teams a shared reference point for design decisions, replacing abstract 'users' with specific, memorable people.
Common contexts
- Presenting three distinct user archetypes to a product team debating which features to prioritise in the next quarter
- Using a persona's technical comfort level to argue against auto-advancing form fields in a senior-citizen-facing government portal
- Referencing a persona's workflow context during a content audit to cut jargon-heavy copy that the real user segment would never encounter
Use when
Create personas when a product serves meaningfully different user segments whose goals, context, or constraints diverge enough to drive different design decisions — and when you have enough research to ground the character in real data rather than assumption.
Avoid when
Don't invest in polished personas when your product serves a single, well-understood user type or when the team already has deep first-hand domain knowledge — the artifact becomes a formality that adds process overhead without changing decisions.
A persona that nobody disagrees with is a persona that nobody uses — the productive ones have specific, sometimes uncomfortable constraints that force the team to make a real choice about who they are designing for.
Real-world examples
- Airbnb maintains two primary persona clusters — experience-seekers and comfort-prioritisers — that drive different UI decisions, from the 'Airbnb Categories' browse experience to the 'Plus' certification programme.
- Microsoft's inclusive design team created 'Persona Spectrum' cards pairing permanent, temporary, and situational disability contexts, helping engineers understand that designing for one improves experience for many.
- Nielsen Norman Group research shows that teams with documented personas make feature prioritisation decisions 40% faster and with fewer revisit cycles than teams relying on informal user descriptions.