Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

UX Design · Lesson 05 / 13

Personas & jobs to be done

How to turn research into personas, empathy maps and job stories that keep a whole team focused on real people — and how to avoid the fake personas that do more harm than good.

5 min read · 5 quiz questions

Why model users at all?

After research, you know a lot about your users — but that knowledge lives in notes and in the heads of the people who did the interviews. Models like personas, empathy maps and job stories package that knowledge into a form the whole team can share and use when making decisions.

Without them, teams design for "the user" — a vague figure who conveniently wants whatever each person in the meeting wants. With them, a product manager can ask "Would Sara actually use this?" and everyone knows who Sara is and what she needs.

Personas

A persona is a fictional character that represents a group of real users who share similar goals, behaviours and pain points. The details are fictional (the name, the photo), but everything that matters is based on research.

What a good persona includes

  • Name, photo and one-line description — to make the persona memorable.
  • Goals — what they are trying to achieve, in their words.
  • Behaviours and context — how, when and where they do the task; tools they use; skill level.
  • Pain points — what gets in their way today.
  • Motivations and concerns — what drives their decisions.
  • A representative quote taken from (or closely based on) research.

What to leave out

Demographic details that don't change design decisions — favourite colour, hobbies, a detailed life story — make personas feel richer but often distract. Ask of every detail: "Would this change what we design?"

Exampletext
SARA — the first-year freelancer
"I just want to look professional and get paid on time."

Goals
- Send invoices that look professional
- Get paid without chasing clients
Behaviours
- Works alone, mostly on a laptop, invoices 2–4 clients a month
- Uses Google Docs templates and her bank app
Pain points
- Unsure which tax details are legally required
- Forgets to follow up on late payments
Concerns
- Looking like an amateur in front of new clients

Common mistake: Creating personas from imagination or marketing segments ("Millennial Mike, 28, loves coffee"). A persona not based on research is a stereotype that confirms the team's assumptions — exactly what research is supposed to challenge.

How many personas, and how to use them

  • Most products need 2–4 personas. More than that and nobody remembers them.
  • Choose a primary persona — the one whose needs come first when there is a conflict.
  • Print them, put them in the team's workspace, and refer to them by name in design reviews.
  • Use them to prioritise: "This feature helps our secondary persona but makes things harder for our primary one."
  • Update them when new research shows they're wrong. Personas are living documents.

Empathy maps

An empathy map is a quick, collaborative way to capture what you know about a user type. It is split into four quadrants around the user:

QuadrantWhat goes hereExample
SaysDirect quotes from research"I never know if I've included everything."
ThinksWhat they might be thinking but not sayingWorries clients will judge her
DoesObserved actions and behavioursCopies a friend's invoice template
FeelsEmotionsAnxious before sending, relieved after payment

Empathy maps are excellent right after interviews: the team fills one in together in 30 minutes, which aligns everyone before deeper synthesis.

Jobs to be done (JTBD)

Jobs to be done is a different lens. Instead of asking who the user is, it asks what progress they are trying to make in a particular situation. The famous idea, associated with Clayton Christensen, is that people "hire" products to get a job done.

A job is stable over time even when solutions change. People have always needed to "get paid for work I've done"; they used paper invoices, then spreadsheets, then invoicing apps. Understanding the job helps you see competitors you'd otherwise miss — a spreadsheet, a phone call, or doing nothing at all.

Functional, emotional and social dimensions

  • Functional — the practical task: send an invoice with the correct details.
  • Emotional — how they want to feel: confident, in control.
  • Social — how they want to be seen: professional, trustworthy.

Writing job stories

A job story captures a job in a format that's easy to design from. It focuses on the situation and motivation rather than a persona:

User storyJob story
FormatAs a [role], I want [feature] so that [benefit]When [situation], I want to [motivation], so I can [outcome]
FocusWho the user is and what feature they wantThe context and the progress they want to make
RiskCan smuggle a solution into "I want…"Keeps the solution open
Exampletext
When  [situation]
I want to  [motivation]
so I can  [expected outcome]

When I finish a project for a new client,
I want to send a correct, professional invoice in minutes,
so I can get paid quickly without looking like an amateur.

Personas or JTBD?

You don't have to choose. Many teams use personas to remember who they're designing for and job stories to describe what those people are trying to get done in specific moments.

Do

  • Base every model on real research.
  • Keep models short enough to read in two minutes.
  • Use them actively in decisions and reviews.
  • Revisit them when you learn something new.

Don't

  • Invent personas in a workshop without data.
  • Fill them with irrelevant demographic trivia.
  • Create ten personas nobody can remember.
  • Make them once and forget them in a folder.

Key takeaways

  • Personas, empathy maps and job stories turn research into shared models the whole team can use.
  • A persona is fictional in detail but based on research in substance: goals, behaviours, pain points.
  • Keep to 2–4 personas and pick a primary one.
  • Jobs to be done focuses on the progress people want to make, with functional, emotional and social dimensions.
  • Job stories (When… I want to… so I can…) keep the solution open.

Exercise

Build a persona and three job stories

  1. Use your notes from the interview exercise (or interview two people now).
  2. Fill in an empathy map: Says, Thinks, Does, Feels.
  3. Write a one-page persona with goals, behaviours, pain points and a quote.
  4. Write three job stories for different situations this persona faces.
  5. For each detail in the persona, ask: would this change a design decision? Remove what wouldn't.

Test yourself

Personas & jobs to be done quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.What should a persona be based on?
  2. 2.How many personas do most products need?
  3. 3.Which four quadrants does an empathy map have?
  4. 4.A job story starts with…
  5. 5.'Look professional to clients' is which dimension of a job?