The idea
Jobs to Be Done is a way of understanding why people choose products. The Christensen Institute describes it as the progress a person is trying to make in a particular circumstance. The product is "hired" to help with that progress.
Two people with the same age and job title may want entirely different things. Two very different people may be trying to do the same job. Looking at the job removes the guesswork.
A job statement
Template“When [situation], I want to [motivation], so I can [outcome].”
Example: "When I join a new team and need to share designs, I want everyone to see the latest version, so I can avoid rework." The statement is about the situation and the outcome, not about a feature.
How to find jobs
- Interview recent customers about the moment they decided to switch or sign up.
- Ask what they used before, what was frustrating, and what finally made them act.
- Listen for forces: what pushed them away from the old way and what held them back from the new one.
- Look for patterns in their circumstances, not in their profiles.
Using jobs in practice
| Use | How jobs help |
|---|---|
| Prioritization | Rank features by how well they help the main job |
| Messaging | Describe the progress users get, not the feature list |
| Competition | Include anything people use for this job, including spreadsheets and manual work |
| Onboarding | Guide users toward the first moment of progress |
Keep it practical
You do not need a formal program. Start by writing down the top three jobs your product serves, and check each against a few customer conversations. Use them in planning meetings as a quick test: which job does this serve?


