Research Governance

Persona

A persona is a research-grounded representation of a user group that summarizes goals, behaviours, context, constraints, and needs relevant to a product or service decision.

Concept facts

A persona is a research-grounded representation of a user group that summarizes goals, behaviours, context, constraints, and needs relevant to a product or service decision.

Also known as
User persona, design persona, research persona, service persona.
Used in
UX research, product design, service design, content design, stakeholder alignment, journey mapping, and requirements framing.
Interpret with
User need, research finding, UX insight, journey mapping, recruitment criteria, service ecosystem, and assumption mapping.

Plain-language explanation

A persona helps teams keep real user contexts in mind during design and delivery decisions. It should represent patterns found in research, not an invented character. A useful persona explains goals, constraints, support needs, and service risks.

Why it matters

Teams often design for themselves, a generic average user, or stakeholder assumptions. Personas can help correct this when they are evidence-grounded, but poor personas can mislead teams if they become stereotypes.

Use contexts

  • synthesising research about user groups
  • aligning teams around user contexts
  • planning journeys, content, and requirements
  • preparing recruitment criteria
  • comparing needs across user groups
  • evaluating whether a design serves priority users
  • supporting stakeholder communication

Application guidance

Build personas from research evidence and focus on behaviours, goals, constraints, and service context. Avoid unnecessary demographic detail. Show what decisions the persona helps with and review personas when service conditions change.

Practical example

A healthtech platform creates a persona for clinic staff who manage appointment referrals. Research shows that staff often work under time pressure, switch between paper slips and digital records, and need to identify urgent cases quickly. The persona helps the product team prioritise visible referral status, keyboard-friendly workflows, and clear urgency labels. The UX consequence is reduced staff workflow burden, fewer missed urgent referrals, and lower decision risk in clinical coordination.

Interpretive boundaries

A persona is not a fictional stereotype, market segment, or demographic profile. Personas should not replace direct research with users, and one persona cannot represent all users.

Applied at Userhub

Userhub uses personas carefully as evidence-based synthesis tools, especially when they help teams understand user context, service risk, and decision implications. In UX Lab work, personas may support journey mapping, content design, requirements framing, and stakeholder alignment.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Pruitt, J., & Adlin, T. (2006). The persona lifecycle: Keeping people in mind throughout product design. Morgan Kaufmann.

Cooper, A., Reimann, R., Cronin, D., & Noessel, C. (2014). About Face: The essentials of interaction design (4th ed.). Wiley.

International Organization for Standardization. (2019). ISO 9241-210:2019 Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. https://www.iso.org/standard/77520.html

Government Digital Service. (n.d.). 1. Understand users and their needs. GOV.UK Service Manual. https://www.gov.uk/service-manual/service-standard/point-1-understand-user-needs

Cite this entry

APA

Userhub. (2026). Persona. UX Reference. https://userhub.com.bd/reference/persona/