Skip to content
Back to Idea Validation

Jobs To Be Done

Frame the problem as a 'job' the user is hiring a product to do, revealing true motivation.

Why

People do not buy products; they hire them to make progress in their lives. The Jobs-to-be-Done (JTBD) frame reveals why someone switches from one product to another: a new product does a job the old one does poorly. "I hire Slack to keep my team in sync without email threads" is more actionable than "Slack is a messaging app" — it tells you what job you must do better to win their business. JTBD is especially powerful for understanding switching: people switch when their current product fails at a job that newly matters to them (e.g. a team grows and Slack's channel chaos becomes a problem). This frame prevents you from competing on features and instead competes on the underlying progress the user is trying to make.

When

After the problem statement, to deepen understanding of motivation. Takes half a day. Use in every user interview.

How

1. Identify the functional job
   - What practical task are they trying to accomplish?
   - "Compile a changelog from git history" (not "use a changelog tool")

2. Identify the emotional job
   - How do they want to feel (or avoid feeling)?
   - "Feel professional to my users" / "avoid the dread of release day"

3. Identify the social job
   - How do they want to be perceived by others?
   - "Look like a serious maintainer who ships clean releases"

4. Write the job story
   - "When [situation], I want to [motivation], so I can [expected outcome]"
   - Example: "When I ship a weekly release, I want to auto-generate a clean changelog, so I can look professional and save 2 hours"

5. Identify the current hire and its struggles
   - What product/method do they hire today?
   - Where does it fail the job? (this is your opportunity)

6. Look for the "push" and the "pull"
   - Push: what frustration with the current hire pushes them to switch?
   - Pull: what does a new solution offer that pulls them over?
   - Anxiety: what fear of the new holds them back?
   - Habit: what inertia keeps them on the current hire?
   - Switching happens when push + pull > anxiety + habit

Example

Product: an AI-powered changelog generator.
JTBD analysis:

Functional job: "Compile an accurate, user-facing changelog from git commits and PRs"
Emotional job: "Feel proud of my releases, not embarrassed by a messy changelog"
Social job: "Look professional to my open-source users and contributors"

Job story: "When I ship a weekly release, I want to auto-generate a clean, grouped changelog from my commits, so I can look professional, save 2 hours, and stop dreading release day."

Current hire: manual copy-paste from PR titles into a markdown file
  - Struggles: misses fixes, inconsistent grouping, takes 2h, feels unprofessional

Switching forces:
  - Push: "my users keep asking 'what changed in v1.3?' and my changelog is empty"
  - Pull: "this tool generates a grouped changelog in 10 seconds from my commits"
  - Anxiety: "will the AI hallucinate changes that did not happen?"
  - Habit: "I already have a CHANGELOG.md template, it is fine"

Strategy: maximize pull (show 10-second demo) + reduce anxiety (show it only uses commit text, no hallucination) → overcome habit.

Common Problems

  • ⚠Confusing the job with the product — "the job is to use a changelog tool" is circular; the job is the progress they want, the product is one hire.
  • ⚠Ignoring emotional and social jobs — "save time" is functional only; "feel professional" is often the stronger motivator and the real differentiator.
  • ⚠Not identifying the four switching forces — without push/pull/anxiety/habit, you cannot design a strategy that overcomes inertia.
  • ⚠Writing job stories that are too generic — "when I work, I want to be efficient" applies to everything and nothing; ground it in a specific situation.

Best Practices

  • ✓Always write the full job story with situation + motivation + outcome — the situation is what triggers the hire and makes it specific.
  • ✓Identify all four forces (push, pull, anxiety, habit) — your strategy must increase pull, reduce anxiety, and overcome habit; push is not in your control.
  • ✓Use JTBD in user interviews — ask "when was the last time you switched tools? what pushed you? what pulled you to the new one?" to reveal real switching dynamics.
  • ✓Compete on the job, not the product — "we do the changelog job 10x faster" is stronger than "we have better AI than competitor X".