Job-To-Be-Done
Synonyms: JTBD, Jobs Theory, Jobs-to-be-Done Framework, Customer Jobs, Job Stories
Definition
Use cases
- Feature planning: A banking app team learns that customers want to check whether their salary has arrived before paying bills. This gives the team a clear user need to investigate.
- Product positioning: A person may choose a meal delivery app because they need dinner after a long workday. The job involves saving time and getting a meal, not simply ordering food.
- Understanding drop-offs: A user may abandon a new budgeting app because moving financial data feels risky. Studying that decision can reveal concerns the team needs to address.
How it's used in practice
- Interview people who recently started, stopped, or changed how they use a product.
- Ask about a real situation and what happened before, during, and after their decision.
- Identify the functional, emotional, and social goals behind their actions.
- Write job stories using: "When [situation], I want to [motivation], so I can [expected outcome]."
- Compare findings across interviews before deciding which product changes to make.
Challenges & limitations
- Vague job statements: Broad statements such as "save time" don't give designers enough detail to make decisions.
- Research bias: Leading questions can push people toward answers that support the team's existing ideas.
- Different methods: JTBD has several approaches, including job stories, switch interviews, and Outcome-Driven Innovation. Teams need to choose one that fits their research goal.
Free resources
- NN/g: Personas vs. Jobs-to-Be-Done — explains how personas and JTBD can work together in UX research.
- User Interviews: Jobs to Be Done (JTBD) in UX Research — explains JTBD in UX research, its strengths and limitations, and how teams can apply it.
- JTBD: The Four Forces of Progress — explains push, pull, anxiety, and habit in customer switching decisions.
