User persona
A user persona is a research-based profile that represents people with similar goals, behaviors and needs. It helps a team make product decisions for a specific kind of user rather than an imagined "average customer."
How it works
Start with interviews, observation and product-usage data. Group people by shared goals and behavior, then write a short profile covering their tasks, context, obstacles and the evidence behind it.
A name or photo is optional. Age and hobbies matter only if they change a product decision. A profile built mainly from guesses is a proto-persona: a hypothesis to test, not a research finding.
Choosing which scheduling feature to build
Hypothetical interviews with 12 scheduling-app users reveal two patterns:
| Persona | Interviewees who fit | Main goal | Product priority |
|---|---|---|---|
| Maya, a cafe owner covering absences | 8 | Fill today's open shift from her phone | Mobile shift alerts |
| Chris, an office-based scheduler | 4 | Plan next month's staffing | Desktop bulk scheduling |
Eight of 12 interviewees fit the first pattern: 8 ÷ 12 × 100 = approximately 67%. If that group is the startup's intended market, mobile shift coverage gets priority over desktop planning.
The persona connects evidence to a product choice. It does not prove that 67% of the wider market behaves this way.
Questions people ask
What are user personas used for?
They guide feature choices, onboarding and usability tests. In business software, separate the user persona from the buyer persona: an employee may use the product while a manager controls the budget. Designing only for the buyer can leave the actual user poorly served.
What are the three main types of personas?
There is no universal set of three. Some design frameworks distinguish primary personas, whose needs take priority; secondary personas, whose needs also matter; and negative personas, whom the product deliberately does not serve. Other frameworks use different categories.
