Personas

Thinking Tools5.1 Defining the Evaluation CriteriaAlso known as User personas

Introduced by Alan Cooper (The Inmates Are Running the Asylum, 1999) and developed by John Pruitt and Tamara Adlin (The Persona Lifecycle, 2006).

Builds a few composite customers from real research, each with goals, frustrations, and habits, picks one as primary, and tests decisions against what that person would make of them.

Eight feature ideas for a technicians' app, tested against two personas

Marisol, the primary persona, does six heating jobs a day alone, often in basements without signal, gloves on; Ken, the secondary, dispatches from the office. Select a feature, then the box for who would use it: the box says what the primary-persona rule does with it. The first is placed as an example. Illustrative.

Items (select one, then a box)
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it
  • Not placedPlacedBuild it firstBuild itOnly if she pays nothingDrop it

Ken, the dispatcher, would use it

YesNo
Only if she pays nothing
Build it first
Drop it
Build it
NoYes

Marisol, the technician, would use it

Works offline. Job records save on the phone and sync later; ride-alongs found half of all jobs are below ground.Not placed yet.Works offline. Job records save on the phone and sync later; ride-alongs found half of all jobs are below ground.Build it first: It serves the primary persona and the secondary one: top of the list.Works offline. Job records save on the phone and sync later; ride-alongs found half of all jobs are below ground.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Marisol cannot finish a job without it. Ken never sees the difference, which is fine.Works offline. Job records save on the phone and sync later; ride-alongs found half of all jobs are below ground.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Works offline. Job records save on the phone and sync later; ride-alongs found half of all jobs are below ground.Drop it: Neither persona would use it, however good it sounded in the meeting.Buttons usable in gloves. Large targets on every screen; technicians keep gloves on near hot equipment.Not placed yet.Buttons usable in gloves. Large targets on every screen; technicians keep gloves on near hot equipment.Build it first: It serves the primary persona and the secondary one: top of the list.Buttons usable in gloves. Large targets on every screen; technicians keep gloves on near hot equipment.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Built for her hands in her situation. Nothing about it affects dispatch.Buttons usable in gloves. Large targets on every screen; technicians keep gloves on near hot equipment.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Buttons usable in gloves. Large targets on every screen; technicians keep gloves on near hot equipment.Drop it: Neither persona would use it, however good it sounded in the meeting.Voice notes on the job. She speaks the job notes; dispatch reads them as text.Not placed yet.Voice notes on the job. She speaks the job notes; dispatch reads them as text.Build it first: It serves the primary persona and the secondary one: top of the list.Her one free hand stays free, and Ken gets notes he can read before the next booking.Voice notes on the job. She speaks the job notes; dispatch reads them as text.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Voice notes on the job. She speaks the job notes; dispatch reads them as text.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Voice notes on the job. She speaks the job notes; dispatch reads them as text.Drop it: Neither persona would use it, however good it sounded in the meeting.Customer signs on phone. The customer signs on the phone screen at the end of the job.Not placed yet.Customer signs on phone. The customer signs on the phone screen at the end of the job.Build it first: It serves the primary persona and the secondary one: top of the list.No paper for Marisol to carry, and the office has the signed record at once.Customer signs on phone. The customer signs on the phone screen at the end of the job.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Customer signs on phone. The customer signs on the phone screen at the end of the job.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Customer signs on phone. The customer signs on the phone screen at the end of the job.Drop it: Neither persona would use it, however good it sounded in the meeting.Live map of technicians. Dispatch sees where every technician is, from the phone's location.Not placed yet.Live map of technicians. Dispatch sees where every technician is, from the phone's location.Build it first: It serves the primary persona and the secondary one: top of the list.Live map of technicians. Dispatch sees where every technician is, from the phone's location.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Live map of technicians. Dispatch sees where every technician is, from the phone's location.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.For Ken alone, and it runs in the background, so it costs Marisol nothing. It stays.Live map of technicians. Dispatch sees where every technician is, from the phone's location.Drop it: Neither persona would use it, however good it sounded in the meeting.Detailed time sheets. Technicians log start and end times for each task within a job.Not placed yet.Detailed time sheets. Technicians log start and end times for each task within a job.Build it first: It serves the primary persona and the secondary one: top of the list.Detailed time sheets. Technicians log start and end times for each task within a job.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Detailed time sheets. Technicians log start and end times for each task within a job.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Ken wants them, and they would cost Marisol a dozen taps a job. They wait until times can be logged without her.Detailed time sheets. Technicians log start and end times for each task within a job.Drop it: Neither persona would use it, however good it sounded in the meeting.Team social feed. Technicians post photos and comments to each other.Not placed yet.Team social feed. Technicians post photos and comments to each other.Build it first: It serves the primary persona and the secondary one: top of the list.Team social feed. Technicians post photos and comments to each other.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.Team social feed. Technicians post photos and comments to each other.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.Team social feed. Technicians post photos and comments to each other.Drop it: Neither persona would use it, however good it sounded in the meeting.Marisol has no time for it on the job, and Ken has no use for it.3D boiler manuals. Rotating 3D models of common boilers, with every part labeled.Not placed yet.3D boiler manuals. Rotating 3D models of common boilers, with every part labeled.Build it first: It serves the primary persona and the secondary one: top of the list.3D boiler manuals. Rotating 3D models of common boilers, with every part labeled.Build it: It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.3D boiler manuals. Rotating 3D models of common boilers, with every part labeled.Only if she pays nothing: It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.3D boiler manuals. Rotating 3D models of common boilers, with every part labeled.Drop it: Neither persona would use it, however good it sounded in the meeting.Too heavy to load without signal and too fiddly in gloves; she uses the printed card on the unit.

Your sort matched 0 of 8.Your sort matched 1 of 8.Your sort matched 2 of 8.Your sort matched 3 of 8.Your sort matched 4 of 8.Your sort matched 5 of 8.Your sort matched 6 of 8.Your sort matched 7 of 8.Your sort matched 8 of 8.

Build it first
It serves the primary persona and the secondary one: top of the list.
Build it
It serves the primary persona, and the primary drives the design. Check only that it does not get in the dispatcher's way.
Only if she pays nothing
It serves the secondary persona alone: keep it only if it adds no step, screen, or delay for the primary.
Drop it
Neither persona would use it, however good it sounded in the meeting.

The sort

  • Works offline: Build it. Marisol cannot finish a job without it. Ken never sees the difference, which is fine.
  • Buttons usable in gloves: Build it. Built for her hands in her situation. Nothing about it affects dispatch.
  • Voice notes on the job: Build it first. Her one free hand stays free, and Ken gets notes he can read before the next booking.
  • Customer signs on phone: Build it first. No paper for Marisol to carry, and the office has the signed record at once.
  • Live map of technicians: Only if she pays nothing. For Ken alone, and it runs in the background, so it costs Marisol nothing. It stays.
  • Detailed time sheets: Only if she pays nothing. Ken wants them, and they would cost Marisol a dozen taps a job. They wait until times can be logged without her.
  • Team social feed: Drop it. Marisol has no time for it on the job, and Ken has no use for it.
  • 3D boiler manuals: Drop it. Too heavy to load without signal and too fiddly in gloves; she uses the printed card on the unit.

An example

A heating services company was building a phone app for its eighty field technicians, and the backlog held sixty feature ideas. Every review argued about the same features, each person picturing a different user, usually themselves.

The product lead spent two weeks riding along with technicians and sitting with dispatchers, then wrote up two composite people from what she saw. Marisol, the primary persona, works six jobs a day alone, half of them in basements without signal, with gloves on and a customer watching. Her quote: I have one free hand and no time. Ken, the dispatcher, assigns jobs from the office and wants to know where everyone is.

From then on, each feature was tested with one question first: would Marisol use this on a Tuesday in a basement? Offline job records and large buttons moved to the top. A live map of technicians stayed, because it cost Marisol nothing. A team social feed was dropped. The first release shipped twelve features in place of sixty, and technicians logged ninety percent of jobs in it within a month.

Why it works

A product designed for everyone is designed for no one in particular, and arguments about features go in circles because each person is picturing a different user. A persona replaces that crowd with one specific person whose habits and constraints everyone has read. The question changes from what users want, which anyone can answer however they like, to whether this person, in this situation, would use the feature, which has an answer.

Naming one primary persona does the deciding. When a feature helps one persona and burdens another, the primary wins, and the others are checked only for harm. Grounding the persona in observation keeps it from becoming the team's own preferences with a name attached: Marisol's gloves and missing signal came from ride-alongs, and nobody in the office would have guessed them.

The thinking behind it

Alan Cooper Alan Cooper, a software designer often called the father of Visual Basic, introduced personas to interaction design: specific archetypal users, built from interviews with real ones, for whom a product is designed. He began using them in 1983, and The Inmates Are Running the Asylum (1999) made the method widely known. Designing for one specific person, instead of for users in general, is the core of the method he made known.

John Pruitt John Pruitt, a user experience researcher, wrote The Persona Lifecycle: Keeping People in Mind Throughout Product Design (2006) with Tamara Adlin, a practitioner's book that treats personas as a managed process: gathering the data, building the personas, using them in design decisions, and finally retiring them. They argue that personas give abstract customer data a human face that a team can remember when it decides.

How to run it

  1. Watch and interview real users. Spend time where the product will be used, and talk to people across the likely groups.
  2. Group them by goals and constraints. Cluster people by what they are trying to do and what gets in the way, more than by demographics.
  3. Write each group as one person. Give a name, a role, goals, frustrations, habits, and a line in their own words.
  4. Choose the primary persona. Pick the one person the product must serve first.
  5. Test every feature against the primary. Ask whether this person, in their real situation, would use it.
  6. Check the others for harm. Keep a feature for a secondary persona only if it costs the primary nothing.
  7. Refresh from new data. Revisit the personas when the users or their work change, at least once a year.

Where it goes wrong

The personas are invented in a workshop. They reflect what the team believes about users, and they confirm the features the team already wanted. Spot it when nobody can name the research behind a persona; go and watch real users before writing any.

There is no primary persona. Four personas get equal weight, every feature serves one of them, and the product does everything a little. Make the team choose, and write the primary at the top of the backlog.

The personas are pinned to a wall and never used. Decisions are made as before, and the posters become decoration. Ask the persona question out loud in every feature review, and record the answer beside the decision.

When to use something else

  • Jobs to Be Done. When the same person wants different things in different moments, and the purchase moment matters more than who they are.
  • Empathy Map. When the team needs a quick shared picture of what one user says, thinks, does, and feels, before writing a full persona.
  • Customer Journey Mapping. When the question is where in a sequence of steps the experience breaks for the user.

Where it sits in SOLVE eX

Go to the source

  • The Inmates Are Running the Asylum, Sams, 1999
  • The Persona Lifecycle: Keeping People in Mind Throughout Product Design, Morgan Kaufmann, 2006

Back to the catalog