A persona is a semi-fictional profile representing a real segment of a product's users, built from actual patterns rather than guesswork — a tool for keeping a whole team designing for the same real person instead of an unspoken assumption in each person's head.
| Section | What goes here |
|---|---|
| Name and a representative photo | Makes the persona feel like a real person the team can reference by name in conversation |
| Goals | What this person is actually trying to accomplish with the product |
| Frustrations / pain points | What currently gets in their way — the real problems being designed against |
| Behaviors | How they actually use technology — device, context, technical comfort level |
| A representative quote | One sentence, in their own voice, that captures their core need |
A weak persona is built around surface demographics — age, job title, hobbies — that rarely predict actual product behavior. A strong persona is built around behavior and goals relevant to the product: how tech-comfortable they are, what they're trying to accomplish, what's stopping them — the details that actually change a design decision.
Ideally, personas are built from real user interviews or support data — actual patterns noticed across real people. When no research exists yet (common for a small project or a course exercise), a "provisional persona" built from reasonable assumptions is a fine starting point, as long as it's treated as a guess to be tested, not a fact.
The document is a means, not the goal
A persona's value isn't the document itself — it's the discipline of asking "would this actually help [persona name] achieve their goal?" during design decisions, instead of designing for an unstated assumption of "the average user."