Jobs to Be Done Explained: A Practical Guide for Product Teams

Jobs to Be Done is a way of understanding why people choose a product: they hire it to make progress in a particular situation. Instead of asking who your customer is, you ask what they're trying to get done and what made them look for help.

It's one of the most useful lenses a product team can learn. It explains switching, reveals your real competitors and gives you language customers actually use.

What Jobs to Be Done Is

The idea was popularised by Clayton Christensen and colleagues, most fully in the book Competing Against Luck. Tony Ulwick developed a related approach called Outcome-Driven Innovation, which focuses on measuring the outcomes people want from a job. The two schools differ in method, but they share the core idea.

The famous line is that people don't want a drill. They want a hole in the wall. Push a little further and they don't really want the hole either. They want the shelf up before the in-laws arrive. That's the job.

A job has a situation, a motivation and an outcome. It's stable over time, even as the products people hire for it change.

When to Choose Jobs to Be Done

Choose it when you need to understand why people really choose a product and who your real competitors are. It's especially helpful when:

• people sign up but don't stick, and you can't see why
• your team defines competitors only as similar products
• personas describe demographics but don't predict behaviour
• you're looking for new markets for something you already make

How to Use Jobs to Be Done, Step by Step

1. Find recent switchers. Talk to people who chose a product like yours in the last few months. Recent choices are remembered in detail.
2. Find the trigger. Ask what was happening when they started looking. Something changed, and that moment is gold.
3. Map the struggle. Ask what they tried first, what they worried about and what nearly stopped them.
4. Write the job statement. A simple shape works well: "When I..., I want to..., so I can..."
5. List everything hired for that job. Include rival products, workarounds, other people and doing nothing.
6. Look for the outcomes that matter. Note how people judge whether the job went well, such as speed, certainty or avoiding embarrassment.
7. Use the job to shape decisions. Features, messaging and pricing should all serve the progress the customer is trying to make.

A Worked Example

Picture a small accounting app for sole traders. The team assumed its customers wanted "easy bookkeeping". Interviews with people who'd signed up in the last month told a sharper story.

The trigger was almost always the same. A tax deadline was approaching and the person realised their receipts were in three places. The struggle was a Sunday night of guilt and spreadsheets.

The job statement became: "When my tax deadline is close, I want to get my receipts in order without losing a weekend, so I can stop worrying and get back to my clients."

That changed the competition. It wasn't just other accounting apps. It was a shoebox, a spreadsheet, a friend who's good with numbers and hiring a bookkeeper once a year. It also changed the product. The team moved receipt capture to the front of the app and started sending a gentle nudge six weeks before the deadline. The marketing stopped talking about features and started talking about getting the weekend back.

Common Mistakes

Naming Your Product in the Job

If your job statement mentions your product or a feature, it's a solution, not a job. Strip it out and describe the progress instead.

Making the Job Too Broad

"Be happier" is true of everyone and useful to no one. Anchor the job in a specific situation.

Asking People What They Want

Customers are poor at predicting their own behaviour. Ask about what they actually did, step by step, the last time it happened.

Forgetting the Emotional and Social Side

People hire products to feel competent or look good to others, as well as to get tasks done. These motives often decide the choice.

How Jobs to Be Done Compares with Related Tools

Personas describe who someone is. Jobs describe what they're trying to achieve. The two can live together, but jobs usually predict behaviour better.

Customer interviews are the main way to uncover jobs. Ask about past behaviour, not future intentions.

An opportunity solution tree is a natural next step. The struggles you find become the opportunities on the tree.

The Kano model helps once you know the job. It sorts features by whether customers expect them, compare on them or are delighted by them.

Questions That Uncover the Job

Good Jobs to Be Done interviews feel like gentle detective work. These questions tend to put people at ease.

• When did you first realise you needed something to help with this?
• What were you using before? What made it stop being good enough?
• What else did you consider? Why didn't you choose those?
• What nearly stopped you from switching?
• How did you know it was working after you started?

Listen for specific moments, places and feelings. "It was the Sunday before the deadline and I was sitting at the kitchen table" tells you far more than "I wanted something easier".

Bringing It Together

Jobs to Be Done shifts the question from "what should we build?" to "what progress is our customer trying to make?" That small change reshapes strategy, product and messaging. The Product Field Kit includes a fillable Jobs to Be Done worksheet to help you capture triggers, struggles and job statements from your own interviews.

Questions People Ask

← More Field Notes