Jobs to Be Done
A lens for understanding the progress people seek in particular circumstances and why they choose, switch, or reject products and services.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/jobs-to-be-done/
01What it means
Jobs to Be Done examines what people are trying to accomplish or become in a specific situation. Rather than segmenting only by demographics or product categories, it studies the functional, social, and emotional progress behind a choice, plus the forces that encourage or resist change.[1][2]
- Situation
- Context of the struggle
- Functional
- What must get done
- Emotional
- How the person wants to feel
- Social
- How they want to be perceived
- Forces for change
- What encourages a switch
- Forces against change
- What preserves the status quo
Research the real decision and forces encouraging or resisting change.
02Why it matters
Products compete with every way a person might make progress, including workarounds and doing nothing. A job-based view can reveal non-obvious competitors, clarify purchase and adoption criteria, and help teams design around outcomes and circumstances instead of copying feature lists.
03When to use it
Use it when adoption is puzzling, customers switch between unlike alternatives, or a team needs a durable way to organize customer needs. It is valuable in interviews about recent decisions, churn, switching behavior, and underserved situations.
04How it works
- Choose a real decision or struggle to investigate, not a hypothetical preference.
- Interview people about the timeline, circumstances, anxieties, habits, and alternatives surrounding that decision.
- Describe the desired progress without embedding a particular product or feature.
- Identify functional, emotional, and social dimensions plus forces promoting or blocking a switch.
- Use the job and its success criteria to shape concepts, positioning, and experiments.
05A practical example
A team studying a meal-planning app learns that busy parents are not merely “organizing recipes.” They are trying to feel confident that dinner will happen despite unpredictable evenings. The team tests flexible fallback meals and shared household decisions rather than adding a larger recipe catalog.
06Where it breaks
The term “job” has several schools and templates, which can cause teams to talk past one another. Job statements may become vague slogans unless grounded in observed decisions. The framework also needs complementary market sizing, usability, feasibility, and business analysis.
Common mistakes
- Writing a job as a feature request, such as “manage tasks in an app.”
- Asking people what they would buy instead of reconstructing an actual decision.
- Ignoring emotional, social, and situational forces around switching.
07Sources
- Jobs to Be Done TheoryChristensen Institute · Primary theory overviewJobs to Be Done Theory
- What Is Jobs to Be Done Theory?Christensen Institute · Institutional explainerWhat Is Jobs to Be Done Theory?