Personas are fictional but research-based representations of key user types. First developed and popularised by Alan Cooper in the 1990s, they give design teams a concrete, human face to design for rather than an abstract average user. A well-crafted persona distils research findings into a memorable character whose goals, frustrations, behaviours, and contexts the team can refer to throughout a project. The goal is not demographic accuracy but motivational and behavioural truth grounded in real data.
What It Is
A persona is a one to two page document describing a specific type of user, built from patterns identified across multiple research participants rather than modelled on any single individual. It includes a name, a representative photograph, a biographical sketch, key goals, primary frustrations, relevant behaviours, and direct quotes drawn from research. The best personas also include a short narrative that brings the character to life in context. Personas are most powerful when they represent meaningfully different goals and mental models rather than merely different demographics.
How to Run It
Personas should be derived from research, not invented from assumptions. After completing your user research phase, analyse the data to identify distinct clusters of goals, behaviours, and motivations. Each meaningful cluster becomes the basis for one persona. Build three to five personas maximum: more than this and the team cannot hold them in mind simultaneously. Involve the whole team in the creation process using a workshop format. Share the finished personas widely and display them visibly in the workspace throughout the project so they are continuously referenced rather than filed and forgotten.
When to Use It
Personas are most useful during the synthesis and framing phase of a project, after research has been completed and before design begins. They serve as a reference throughout ideation, prototyping, and evaluation to ensure that design decisions are always grounded in real user needs rather than stakeholder preferences or team assumptions. They are also valuable in client presentations and stakeholder workshops to build empathy for users among people who are not directly involved in the research process.
Tips for Success
Avoid creating vanity personas that flatter the product team by describing an ideal user who loves the product. Personas should be honest about frustrations and limitations. Include a primary persona, the person you are designing primarily for, and secondary personas who represent other important but less central user types. Revisit and update personas when new research reveals that the original characterisation has become outdated. A persona that no longer reflects current user behaviour is worse than no persona at all.
