UX Foundations · Step 2 · 4 min read
User needs and jobs to be done
People don't want features; they want progress in their lives. How to tell a need from a request, what "jobs to be done" means and where the milkshake story comes from, how to write job stories, and how to use them to judge design ideas.
Users ask for features; what they need is something else. "Can you add an export to Excel?" may mean "I need to show my manager these numbers every Monday". If you build the export, they'll still spend an hour formatting it. If you understand the need, you might send the manager a weekly summary instead. The skill is to listen past the request to the need underneath.
What you'll be able to do after reading:
- Tell a user need from a feature request
- Explain "jobs to be done" with a real example
- Write job stories: "When… I want to… so I can…"
- Use needs to judge and compare design ideas
1. Requests, needs and goals
- Request"Export to Excel"
The solution someone imagines.
- Ask why"What would that let you do?"
Ask it again until you reach the need.
- NeedShow my manager the numbers on Monday
What they are missing.
- GoalExplain why we are behind
Where they want to end up.
A request is the solution someone imagines. A need is what they're missing. A goal is where they want to end up (see Users, tasks and context). Ask "what would that let you do?" until you reach the need.
2. Jobs to be done
Clayton Christensen and colleagues describe a job as "the progress that the customer is trying to make in a given circumstance" (HBR, Know Your Customers' "Jobs to Be Done", Sep 2016). People "hire" a product to make that progress, and "fire" it when something does the job better.
The best-known example is the milkshake. A fast-food chain found that many milkshakes were bought "first thing in the morning, by commuters", who had "(at most) one free hand" and a long, boring drive. The milkshake was hired to make the commute bearable and keep them full until lunch; its competitors were bananas and bagels, not other milkshakes (HBS Working Knowledge, 2011).
3. Job stories
Job stories put the situation first. The format was popularised at Intercom (Klement, Designing features using Job Stories, 2013):
When [situation], I want to [motivation], so I can [expected outcome].
| Feature request | Job story |
|---|---|
| "Export to Excel" | When it's Monday morning, I want to show my manager last week's numbers, so I can explain why we're behind before the meeting |
| "Dark mode" | When I check my messages in bed, I want the screen not to dazzle me, so I can fall asleep afterwards |
The situation ("when…") is where design ideas come from: a Monday deadline and a manager suggest very different solutions than "export".
4. Using needs to judge ideas
Once the needs are written, every idea can be asked: which need does this meet, and how well? An idea that meets no written need is a nice-to-have at best. Two ideas that meet the same need can be compared directly, without arguing about taste.
5. Common mistakes
- Building exactly what was requested without asking why.
- Writing needs as features ("users need a filter").
- Describing people by demographics instead of situations.
- Collecting needs and never using them to choose between ideas.
6. Vocabulary
| Term | Meaning |
|---|---|
| Feature request | A solution someone asks for |
| User need | What a person is missing, in their own situation |
| Job to be done (JTBD) | The progress someone is trying to make in a given circumstance |
| Job story | "When… I want to… so I can…" |
| Hire / fire | Choosing a product to do a job, or dropping it for something better |
7. Try it (no tools needed)
- Write down three feature requests you've heard (or would make yourself) about an app you use.
- For each, ask "what would that let you do?" twice, and write the need.
- Rewrite each as a job story. Then sketch one solution that meets the need without the requested feature.
Reflection questions: Which request turned out to hide a different need? What did the "when…" part change about your idea?
8. If you already practise
- Keep a list of job stories per product area and refer to it in prioritisation, not only in design.
- Compare personas and jobs: NN/g argues they work well together, with personas describing who and jobs describing why (NN/g, Personas vs. Jobs-to-Be-Done).
- Jim Kalbach's The Jobs To Be Done Playbook turns the idea into practical steps.
Checklist
Learn more
- Theory: Christensen et al., Know Your Customers' "Jobs to Be Done" (HBR, 2016) · Clay Christensen's Milkshake Marketing (HBS Working Knowledge, 2011)
- Practice: Alan Klement, Designing features using Job Stories (Intercom, 2013)
Books, courses and videos to go deeper
- Competing Against LuckClayton M. Christensen, Taddy Hall, Karen Dillon and David S. DuncanBook · Harper Business, 2016
- The Jobs To Be Done PlaybookJim KalbachBook · Two Waves Books, 2020 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Problem statements and "How might we" · Personas and archetypes · Users, tasks and context · Defining success