Jobs to Be Done (JTBD)
Level 3 Β· Finding the right problem
Why people hire a product to get a job done, and who the real rivals are. How a job story turns that job into one sentence.
Course contentsLesson 6 of 13
Level 1 Β· The job
Level 2 Β· Where the product is going
Level 3 Β· Finding the right problem
Level 4 Β· Choosing what goes first
Level 5 Β· Shipping and measuring
After this lesson you can
- Describe a user's need as a job
- Write a job story in three parts
- Name rivals that are not like your product
11 mincovers 3 glossary entries
Worth reading first: Product Discovery Basics
What job a product is hired to do
Jobs to be done, or JTBD, is the idea that people buy a product to get a job done in their life. The job is the progress they want, not the product. Nobody wants a drill. They want a hole in the wall, or really, a shelf that holds their books. The job lasts longer than any tool for it.
This changes who the rivals are. A bus tracker app is not only up against other bus apps. It is up against a printed timetable, a text to a friend and just standing at the stop and hoping. Anything people use for the same job is a rival, even when it looks nothing like your product.
A job comes up in a moment. The bus is late, it is raining, and you need to know whether to wait or walk. Studying that moment tells a team far more than studying the type of person. A student and a retired teacher can have the exact same job at the same stop.
A job story writes one job down in three parts. When, the situation. I want to, the motivation. So I can, the outcome. When my bus is late, I want to see where it is, so I can plan my wait. Notice that no product and no button is named anywhere in it.
That is the test of a good job story. It should make sense even if your product did not exist. If the motivation reads I want to tap the map button, it names a fix, not a need. Rewrite it until a rival could meet the same job a different way.
Job stories and user stories look alike and come from different places. A user story starts from a type of person and is usually a piece of work to build. A job story starts from a moment and is a need to understand. Many teams find the job first and write user stories for the fix later.
Worked example
Jack's recipe app finds its rival
Jack runs a recipe app. Talks with 12 users show the job is not finding a recipe. It is deciding what to cook tonight with what is already in the fridge.
His real rival is a text to a partner asking what is left, not other recipe apps. He builds a search by ingredients, and weekly use rises from 2 visits to 3.
The words for this lesson3
Check yourself
Which of these is a well-written job story?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.