II.
Methodology overview
Reference · livemethodology:jobs-to-be-done
Jobs to Be Done (JTBD) overview
A framework focusing on understanding the progress customers are trying to make rather than on products, features, or personas. Central insight: people hire products to make progress on jobs. Analyzes switching behavior through four forces: Push (current problems), Pull (new solution appeal), Anxiety (concerns about switching), and Inertia (habit of current solution). Job stories replace traditional user stories.
Attributes
displayName
Jobs to Be Done (JTBD)
description
A framework focusing on understanding the progress customers are trying to make
rather than on products, features, or personas. Central insight: people hire
products to make progress on jobs. Analyzes switching behavior through four
forces: Push (current problems), Pull (new solution appeal), Anxiety (concerns
about switching), and Inertia (habit of current solution). Job stories replace
traditional user stories.
methodologyKind
design-thinking
origin
Clayton Christensen, Alan Klement, Intercom
yearIntroduced
2016
Outgoing edges
applies_to1
- domain:software-engineering·DomainSoftware Engineering
Incoming edges
follows_methodology1
- lib-process:shared--jobs-to-be-done·LibraryProcessjobs-to-be-done