All 29 modules are open from the start — nothing here is
locked, and nothing costs anything. Sign in so your progress, titles and
credentials stay with you, on every device you use.
Free forever, with your Google account. No password, no payment.
Why people really "hire" products, explained from zero
New to product management? Start here. Jobs-to-be-Done (JTBD) is the single most useful
lens for understanding what users actually want. Learn it through stories, quick quizzes,
and a hands-on statement builder.
Ready?
1
The Milkshake Story & the Core Idea
People do not buy products. They hire them to make progress in a particular situation — and when the product stops making that progress, they fire it.
That is the central claim of Jobs to be Done, and the word doing the work is situation. The job is the progress someone is trying to make at a specific moment, under specific constraints. It explains behaviour that demographics cannot, because two people with nothing in common on age or income can be in identical situations, and two people with identical demographics can be in completely different ones.
The practical shift this forces is in what you consider your competition. If you define yourself by your category, you will benchmark against products that look like yours and add the features they have.
If you define yourself by the job, you compete with everything else the customer might hire — a spreadsheet, a colleague, a manual process, and doing nothing at all. That last one is very often the incumbent you are actually losing to, and it never appears on a competitive matrix.
The left panel is the list a competitive matrix produces; the right one is the list the customer is actually choosing from. Only one of them has “doing nothing at all” on it, and that is usually what you are losing to.
Everyday example, the drill and the hole
There's a famous line: "People don't want a quarter-inch drill, they want a quarter-inch
hole." And really, they don't even want the hole. They want to hang a photo of their kids
so their living room feels like home. The drill is just something they "hired" to
make that progress. If someone invented a cleaner way to hang the photo, the
drill gets "fired." JTBD keeps your eyes on the progress people are chasing, because
that's what they're loyal to, not your product.
The famous milkshake study
A fast-food chain wanted to sell more milkshakes. They asked customers what flavors
they'd like. Nothing worked. Then researchers simply watched when people bought
milkshakes, and discovered half were sold before 8:30 AM, to commuters.
The commuters had a problem: a long, boring drive. Bananas were gone in a minute,
donuts made fingers sticky on the wheel, bagels were too dry. A thick milkshake lasted
25 minutes, fit the cupholder, and kept them full until lunch.
The "job" was: keep me occupied, clean, and full during my morning drive.
Quick check
Imagine you work on Spotify. Which of these sounds like
Jobs-to-be-Done thinking, rather than standard marketing?
2
The Anatomy of a Job Statement
A job statement is a specific format, and the format exists to stop you smuggling a solution into the description of a problem.
It has three parts. When… — the situation, with its constraints. I want to… — the motivation, stated without naming any product. So I can… — the outcome that would tell you it worked. Put together: When I am leaving the office and it is getting dark, I want to know whether it is safe to cycle home, so I can decide before I have committed to the ride.
The middle line is where it goes wrong. “I want to open the weather app” is a solution — it presupposes the answer and closes off every other one. “I want to know whether it is safe to cycle home” is a job, and it leaves open a notification, a widget, a message from a colleague, or something nobody has built.
The “so I can” clause does quiet, important work too. It is your success criterion. If you cannot say what the person is trying to achieve, you have no way of telling whether any solution helped, and you will end up measuring usage instead of progress.
The middle line is where solutions sneak in. “I want to open the app” is a solution; “I want to know if it is safe to leave now” is a job — and only the second one lets you build something other than what already exists.
Everyday example, three parts, one sentence
Think of telling a friend why you grabbed takeout: "When I got home late
and starving (situation), I wanted a hot meal with zero effort (motivation),
so I could just eat and collapse on the sofa (outcome)." Same three parts
every job statement uses: the situation you're in, the thing you want to do, and the
deeper reason behind it. The trick is that the outcome ("collapse and relax") is
the real target, the takeout is just one way to get there.
When…
The Situation
The real-life trigger. Where is the person? What's happening around them?
I want to…
The Motivation
The immediate thing they're trying to do to deal with that situation.
So I can…
The Outcome
The deeper reward, the convenience, relief, or feeling they're really after.
The job hidden under the request
Customers asked repeatedly for more chart types. Interviewed with a job lens, what they were hiring the product for was to walk into a Monday meeting and not be asked a question they could not answer. More chart types was one solution; a shareable summary that anticipated the three usual questions was a better one, and nobody had asked for it.
Quick check
You work on Netflix and you're writing a job statement for a tired parent:
"When my kids are finally asleep on Friday night, I want to easily find a light, funny
movie, so I can [_____]." Which option is the outcome?
3
The Three Dimensions of a Job
Every job has three dimensions running at once, and products fail regularly because a team solved one of them perfectly and never noticed the other two.
The functional dimension is the practical task: close the books, get home, find the file. It is the one that ends up in requirements documents, because it is the easiest to write down.
The emotional dimension is how the person wants to feel — or, more often, what they want to stop feeling. Confident rather than anxious. In control rather than behind. The social dimension is how they want to be seen by others: competent in front of their boss, generous in front of their friends, careful in front of an auditor.
The practical use of this is as a checklist when a well-built thing is not being adopted. Ask what the person is afraid of feeling, and who is watching them use it. The answers are rarely in the requirements, and they are frequently the reason the requirements were not enough.
A finance tool solved the functional job — closing the books faster — and stalled. What mattered to the accountants was social: they needed to be seen as accurate, and a tool that closed fast but could not show its working made them look careless. Ask what they are afraid of feeling, and who is watching.
Everyday example, a luxury watch
Why pay thousands for a Rolex when a $20 watch tells time just as well? Because telling
time (the functional job) is the least of it. Wearing it makes you feel
successful and put-together (the emotional job), and it signals status to
everyone who notices it (the social job). The cheap watch wins on
function and loses everywhere else. Most products people love are quietly doing all three
jobs at once, and beginners see only the first.
F
Functional, the practical task
The thing that literally needs doing: get from A to B, write a document, boil water.
E
Emotional, how they want to feel
The feeling they want (or want to avoid) while doing it: safe, calm, in control.
S
Social, how they want to be seen
What it says about them to others: professional, stylish, successful.
The social dimension nobody put in the brief
A finance tool was built entirely around the functional job of closing the books faster. Adoption stalled. The dimension that mattered to the accountants was social — they needed to be seen as accurate, and a tool that closed fast but could not show its working made them look careless. The functional job was solved and the product still failed.
Quick check
Someone buys premium headphones, wears them in an open office, and listens to…
nothing. They just want colleagues to think they're in deep-focus mode and leave them
alone. Which dimension are they "hiring" the headphones for?
4
The Four Forces of Progress
A customer agrees your product is better. They say so, enthusiastically, more than once. They do not switch. This is not indecision — four forces are acting on them at the same time, and two of those forces are on the side of doing nothing.
Pushing them toward change: the push of their current situation (what is bad about how they do it today) and the pull of your solution (what looks better about yours). These are the two forces every pitch deck is built around.
Holding them still: anxiety about the new thing (will migration lose my data? will I look foolish if this fails?) and habit — the pull of the existing way, which is understood, already learned, and requires no explanation to anybody.
Switching only happens when push and pull together beat anxiety and habit. Most teams spend all their effort making the pull stronger, which is the natural instinct and often the least efficient move available.
One team opened a stalled switch with an importer and a migration guide. Neither added a single capability to the left panel — they only cut the two forces on the right, which is generally the cheaper side to work on and almost never the side a roadmap is aimed at.
Everyday example, switching gyms
Picture deciding whether to leave your gym for a new one.
Push: your current gym is always crowded and the showers are broken.
Pull: the new place has fancy equipment and a pool.
Anxiety: what if the new one is a hassle to get to, or I'm locked into a
contract? Habit: I know everyone at my old gym and my routine there.
Even when the new gym is clearly better, you only switch when push + pull beat anxiety +
habit. Great products don't just add pull, they actively shrink the anxiety and habit
holding people back (free trials, easy imports, "cancel anytime").
Drives the switch
1. Push of the present
Frustration with what they use today. "My current tool keeps losing my edits!"
Drives the switch
2. Pull of the new
The appeal of your solution. "Wow, no downloads required!"
Holds them back
3. Anxiety of the new
Fear of switching. "What if this app loses my old files during setup?"
Holds them back
4. Habit of the present
Comfort with the current way. "But I already know all the shortcuts here…"
The forces that kept them where they were
A team could not understand why a clearly better product was not being switched to. The push and the pull were both strong; so was the anxiety about migrating three years of history, and the habit of a process the whole team already knew. The winning move was an importer and a migration guide, which added no new capability at all.
Quick check
A riddle: "I am the whisper of doubt right before someone clicks 'Sign Up.'
I make them ask 'Will this take too long to learn?' and 'What if it breaks my current
workflow?' I am the invisible anchor holding them back." Which force am I?
Drill what you learned
Scenario 1
easy
You join a sleep-tech startup. Everyone hates their alarm clock, and you're asked to redesign the wake-up experience for busy professionals.
What is your first move, thinking in Jobs-to-be-Done?
Scenario 2
easy
Peloton sells a stationary bike for several times the price of a normal one — and people happily pay it.
Which explanation best captures the job Peloton is hired for?
Scenario 3
easy
A competitor just launched a free feature that overlaps with your paid product. Leadership is nervous and wants a response this week.
What does the Four Forces model tell you to do?
Scenario 4
easy
A user says: "I bought a $5 self-help book, but honestly I've never opened it. It just sits on my nightstand and I feel better having it there."
What job did the book get hired for?
Scenario 5
easy
You run a note-taking app. In interviews you keep hearing: "I don't use fancy features — I just need to dump a thought before I forget it while walking between meetings."
What should this steer your roadmap toward?
Scenario 6
medium
You're the PM for a budgeting app. A competitor analysis lists only other budgeting apps. Your churn interviews reveal users quit because "I just went back to a spreadsheet / a notebook / not tracking at all."
What JTBD lesson does this reveal?
Scenario 7
medium
A teammate writes this job statement: "When users open our app, they want to use our new AI summary feature, so they can enjoy our product."
What's wrong with it?
Scenario 8
medium
Your onboarding is beautiful, but analytics show most new users abandon at the "import your existing data" step, even though importing would clearly help them.
Which of the four forces is likely to blame?
Scenario 9
medium
A luxury-handbag brand asks you to explain, in JTBD terms, why customers pay 20x more than a functionally identical bag.
What's the sharpest JTBD explanation?
Scenario 10
medium
Two users both "hire" a food-delivery app, but for very different reasons: one is a busy parent with no time to cook; the other is showing off by ordering a trendy restaurant for friends.
What does this tell a product team?
Scenario 11
hard
In a churn interview, instead of asking "what features do you want?", a skilled PM asks: "Walk me through the day you decided to cancel — what happened right before?"
Why is the second question more JTBD-aligned?
Scenario 12
hard
Your product is objectively better than the incumbent on every feature, yet enterprise customers won't switch. Interviews reveal: "Our whole team knows the old tool, and re-training 200 people terrifies us."
Which forces are blocking the switch, and what's the play?
Scenario 13
hard
A founder insists: "Our target market is women aged 30–45 with high income." When you interview them, their reasons for buying are wildly different from one another.
What's the JTBD critique of this targeting?
Scenario 14
hard
Slack famously described a big part of its job as "make my team feel less overwhelmed by email and more connected." A rival copies every Slack feature but users say it "feels cold and corporate."
What did the rival miss?
Scenario 15
hard
You're tempted to add a flashy new capability because a competitor has it. Before committing, you apply JTBD.
What's the right JTBD question to ask first?
Drilled it. Now apply it to a real situation.
Put it to work
From lesson 1
Milkshakes at seven in the morning
A fast-food chain, via Clayton Christensen
A chain wanted to sell more milkshakes. It had done the obvious research:
profile the milkshake buyer, ask them what would make the milkshake
better, change it accordingly. Thicker, sweeter, chunkier. Sales did not
move.
Christensen's team asked a different question — what job are people
hiring this milkshake to do? Standing in the restaurant, they found that
nearly half of all milkshakes were sold before 8am, to solo drivers, who
took them away.
Why did profiling the buyer fail where the job question worked?
What actually happened
The morning job turned out to be: make my boring commute more
interesting, and keep me from being hungry until eleven. The competition
was not other milkshakes — it was bananas, doughnuts and bagels, each of
which loses on some dimension of that job.
Which reframes every improvement. Thicker is better because it lasts the
drive. Small chunks of fruit are better because they make the straw
interesting. Neither idea comes out of asking a milkshake buyer what
they want in a milkshake.
People do not buy products. They hire them to make progress in a
circumstance — and the circumstance, not the customer, is the unit of
analysis.
From lesson 2
Four attempts at one job statement
A password manager
The team is writing the core job for their product. Four versions go on
the wall.
Order them from strongest to weakest.
Drag the rows, or use the arrows, then check.
"When I sign up for a new service on a device I do not normally use, I want to create and store a strong password without breaking my flow, so I can get on with the thing I was actually doing."Strongest. Situation, motivation and expected outcome, all in the customer's terms. The awkward part of the circumstance — an unfamiliar device — is exactly where the product usually fails, and naming it makes that testable.
"When I sign up for a new service, I want a strong password, so my accounts are secure."Second. The right shape but generic. Every competitor satisfies it equally well, so it cannot discriminate between designs.
"Users want their passwords to be secure and easy to use."Third. No situation, so nothing about when or why the need arises. It is a summary of the category, not a job.
"Users want a browser extension that autofills credentials."Weakest. A solution written as a need. It rules out every other way of doing the job before anyone has examined the job.
What actually happened
The first version led directly to the feature that mattered: a
one-time-use code to authenticate on a borrowed device without signing
the whole vault into it. Nobody would have reached that from "users want
an autofill extension".
When [situation], I want to [motivation], so I can [expected outcome].
The situation is the part teams skip, and it is where the design
constraints live.
From lesson 3
The functional job was fine; the product still lost
A will-writing service
An online will-writing product does the functional job well: a valid will
in under twenty minutes, cheaper than a solicitor, legally sound. Yet
two-thirds of people who start abandon partway, and most of those go on
to book a solicitor instead.
Exit interviews with fifteen of them.
What they said, grouped
What they said
Count
"I wanted someone to tell me I'd got it right"
9
"It felt wrong to do this on my phone in the kitchen"
6
"I didn't want my sister to think I'd cut corners on it"
5
"The form was confusing"
2
Which dimensions of the job is this product failing?
Select all that apply — there are 3 to find.
What actually happened
They added a solicitor review step — optional, paid, and slower. It made
the functional job worse on every measure the team had been optimising,
and completion rose from 34% to 61%.
Every job has functional, emotional and social dimensions. A product that
only serves the functional one loses to a slower competitor that serves
all three.
From lesson 4
Why nobody switched
A business banking app
A challenger bank is winning on every feature comparison and losing on
switching. Small businesses say the incumbent is worse and stay anyway.
The team maps the four forces on twenty interviews.
Work the forces.
Step 1 of 3
Push and pull are both strong — the incumbent is genuinely frustrating and the new app is genuinely better. So why is nobody moving?
So the question is what specifically people are anxious about, and what habit they would have to break.
Step 2 of 3
The most-cited anxiety: "what happens to my standing orders and my accountant's access during the move?" What kind of intervention does that call for?
Note that none of this makes the product better on any comparison table. It makes the switch survivable.
Step 3 of 3
What does this say about where the roadmap should go?
Four forces, and two of them are usually the ones nobody has budgeted for.
What actually happened
Parallel running and automatic standing-order migration shipped over two
quarters. Switching from the largest incumbent rose 3.4x, with no change
to the feature set anyone had been comparing.
Push and pull get people wanting it. Habit and anxiety decide whether
they actually move. Most roadmaps fund the first two and wonder why the
number does not shift.