Key Principle
Putting JTBD into practice is itself a switching problem: organizations have existing habits-in-use (current processes, frameworks, mental models) and anxiety-in-choice about new methods. Successful adoption follows the same forces-of-progress logic the book teaches. You do not sell JTBD as a framework -- you demonstrate results first, reveal the methodology second, and sequence your analysis so demand signals (push and pull) are confirmed before friction (anxiety and habit) is investigated.
"It's easier to sell 'consumer research' as due diligence and verification of existing assumptions. It's hard to sell a new process framework." -- Alan Klement, Chapter 14 (Ritzenthaler)
Why This Matters
Most JTBD initiatives fail not because the theory is wrong but because practitioners reverse the correct sequence -- starting with friction analysis before confirming demand, or presenting a pre-packaged framework before earning credibility through results. The adoption strategies in Chapters 14-15 treat the organization itself as a customer with push forces (dissatisfaction with current methods), pull forces (vision of better outcomes), anxiety (fear of new processes), and habits (entrenched workflows). Ignoring these forces produces the same failure mode as ignoring them in product design.
The practitioner heuristics from the appendix chapters provide concrete checkpoints: a litmus test for whether you have identified a real Job, a sequencing rule for the forces of progress, and displacement questions that prevent feature-level thinking from contaminating strategy.
Good Examples
Bottom-up adoption (Wu at Meetup): Wu interviewed churned customers quietly, built a track record of insights, then presented findings in an emotionally resonant format -- photos of departed customers alongside their anxiety quotes under the title "Why People Fire Meetup." The audience volunteered solutions before Wu revealed the JTBD method. He kept data separate from synthesis so the team could participate in sense-making rather than receiving pre-packaged conclusions. (Ch. 14)
Top-down adoption (Martell at Clarity): Martell practiced JTBD interviewing alone first, then explained the concepts to his team, then co-interviewed with them. The sequence -- demonstrate, explain, collaborate -- mirrors the principle that results must precede methodology. (Ch. 14)
Stealth reframing (Ritzenthaler): Converted teammates' existing intuitions into testable hypotheses using four questions that map directly to push, pull, anxiety, and habit -- without ever naming the forces-of-progress framework. Research was positioned as "due diligence," not a new process. (Ch. 14)
Counterpoints
Selling the framework first: Introducing JTBD as a new methodology triggers organizational change-aversion -- the same anxiety-in-choice that blocks consumer switching. Teams resist because they hear "replace your current process" rather than "here is evidence that changes what we should build." (Ch. 14)
Starting with friction instead of demand: Teams that begin by asking "Why aren't people switching?" without first confirming push and pull forces may optimize onboarding for a product nobody wants. The correct sequence is: study push and pull first (demand signal), then dig into inertia and anxiety (friction). (Ch. 17)
Commingling data with synthesis: Presenting pre-packaged conclusions blocks team buy-in. When data and interpretation are delivered together, colleagues cannot engage in collaborative sense-making and default to skepticism or passive acceptance. (Ch. 14)
"I made sure not to commingle my data with my synthesis of them." -- Alan Klement, Chapter 14
Key Quotes
"Before you make anything, have a clear picture in your mind of what customers will stop doing." -- Alan Klement, Chapter 17 (referencing Ch. 8)
"Be suspicious of the 'impulse purchase' concept. No purchase is random." -- Alan Klement, Chapter 17 (referencing Ch. 5)
"A Job to be Done is the process a consumer goes through whenever she aims to transform her existing life-situation into a preferred one but cannot because there are constraints that stop her." -- Alan Klement, Chapter 16
Rules of Thumb
- Show results first, reveal the method second. Adoption follows credibility, not curriculum.
- Sequence analysis as: push/pull (demand) before anxiety/habit (friction). Friction analysis without demand confirmation wastes resources.
- Apply the litmus test: "Does this describe an action? Can I visualize someone doing it?" If yes, you have a solution, not a Job. (Ch. 17)
- Do not stratify Jobs into functional/social/emotional types. Every Job is a blend of emotional forces acting simultaneously. (Ch. 17)
- Ask "From which budget will my product take away money?" to identify the real competitive set. (Ch. 17, referencing Ch. 4)
- Start broad (struggle/aspiration), then narrow progressively. Starting with a specific product idea reverses the correct sequence and produces feature-level thinking. (Ch. 10)
- Name what the customer will stop doing. If you cannot identify what your product displaces, you do not understand the Job.
- Keep data and synthesis separate when presenting to teams -- invite collaborative sense-making.
Sequencing Summary
Demand (push + pull) then friction (anxiety + habit) then adoption (show results, reveal method, co-create).
Related References
- JTBD Research and Interview Methods - the research methods to use
- How to Describe and Validate a JTBD - how to articulate findings
- Jobs to Be Done as Self-Betterment - the theory being implemented