# 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.

- Type: framework
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/jobs-to-be-done/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Choose a real decision or struggle to investigate, not a hypothetical preference.
2. Interview people about the timeline, circumstances, anxieties, habits, and alternatives surrounding that decision.
3. Describe the desired progress without embedding a particular product or feature.
4. Identify functional, emotional, and social dimensions plus forces promoting or blocking a switch.
5. Use the job and its success criteria to shape concepts, positioning, and experiments.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/jobs-to-be-done/#visualization-jobs-to-be-done>)

## Sources

1. [Jobs to Be Done Theory](<https://www.christenseninstitute.org/theory/jobs-to-be-done/>) — Christensen Institute · Primary theory overview
2. [What Is Jobs to Be Done Theory?](<https://www.christenseninstitute.org/video/what-is-jobs-to-be-done-theory/>) — Christensen Institute · Institutional explainer

## Related topics

- [Value Proposition](<https://wiki.soroush.uk/topic/value-proposition/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
