Jobs-to-be-Done framework theory and interview methodology
Jobs-to-be-Done (JTBD) is a theory that consumers purchase products and services to fulfill a 'job,' and the JTBD interview methodology is a specific, causal research technique that uncovers the underlying, often unarticulated, motivations and contexts behind those purchases.
This skill is highly valued because it shifts focus from correlation (what customers buy) to causation (why they buy), enabling organizations to create products that achieve true market pull. It directly impacts business outcomes by reducing product failure rates, informing breakthrough innovation, and improving marketing message alignment.
1Careers
1Categories
8.7 Avg Demand
25%
Avg AI Risk
How to Learn Jobs-to-be-Done framework theory and interview methodology
Focus on three areas: 1. Core theory: Read Clayton Christensen's 'Competing Against Luck' and understand the 'struggling moment,' 'push/pull forces,' and 'four forces of progress.' 2. Terminology: Define and distinguish between 'Job Executor,' 'Job Beneficiary,' 'Job Statement,' and 'Needs.' 3. Passive listening: Begin passively listening to user stories, identifying emotional and social dimensions alongside functional ones.
Move to practice by conducting 'Switch' interviews: document a user's timeline of events leading to a purchase, the forces at play, and their struggling moment. A common mistake is leading with product questions or surveying for satisfaction instead of investigating causality. Intermediate practice involves diagramming the 'Job Map' for a common product and identifying underserved outcomes.
Mastering JTBD at a strategic level involves synthesizing multiple job maps into a 'Job Architecture' for a product portfolio, identifying unmet 'Needs Statements' for competitive differentiation, and using causal data to justify R&D and marketing investments. This includes mentoring teams to conduct interviews independently and integrating JTBD insights into the formal product development and governance process.
Practice Projects
Beginner
Case Study/Exercise
Deconstructing a Personal Purchase
Scenario
Analyze your own recent purchase of a productivity app (e.g., Notion, Todoist) or a significant consumer good.
How to Execute
1. Write your personal 'Job Statement' for the purchase. 2. Map the 'Timeline of Events' leading to the decision. 3. Identify the 'Push' factors (frustrations with the old solution) and 'Pull' factors (appeal of the new). 4. Note the 'Anxiety' (risks) and 'Inertia' (habits) you had to overcome.
Intermediate
Case Study/Exercise
Conducting a 'Switch' Interview
Scenario
Interview a colleague who recently switched SaaS tools (e.g., from Slack to Teams, or Zoom to Google Meet) within their work context.
How to Execute
Advanced
Case Study/Exercise
Competitive Job Map Analysis
Scenario
Your company is entering a crowded market (e.g., project management software). Analyze the competition not by features, but by the jobs they are hired to do.
How to Execute
1. Select 3 competitors. 2. Construct a 'Job Map' for the core customer job (Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, Conclude). 3. Analyze which job steps each competitor excels at or neglects. 4. Identify the most underserved job steps and associated 'Needs Statements' as a strategic opportunity for differentiation and messaging.
Tools & Frameworks
Mental Models & Methodologies
The Forces of Progress (Push, Pull, Anxiety, Habit)Job Map (8-step model by Strategyn)Needs Statements (Desired Outcome Statements)
The Forces of Progress diagram is used during interview synthesis to visualize why a switch happened. The Job Map provides a stable structure for analyzing any job, independent of solutions. Needs Statements are measurable, stable metrics used to quantify unmet demand and guide solution innovation.
Affinity mapping helps researchers group raw interview quotes into themes (forces, job steps). Timeline diagrams visualize the causal sequence of events. ODI software applies quantitative analysis to JTBD needs data to prioritize opportunities.
Interview Questions
Answer Strategy
This tests conceptual clarity. Answer by defining both terms precisely. A 'job' is the higher-level goal or problem to be solved (stable over time). A 'need' is a desired outcome statement that is part of getting the job done (also stable, but measurable). Then, provide an example: The job is 'Be a more effective parent.' A need is 'Minimize the likelihood of my child missing important developmental milestones.' This distinction moves the roadmap from vague themes ('parenting features') to specific, measurable outcomes to design against.
Answer Strategy
This tests methodological rigor. Describe the 'Switch' interview structure: start with the purchase, then rewind to the 'first thought' and walk forward through the timeline. Explain the importance of specific, open-ended questions ('What was going on in your life when you first started looking for a solution?' 'Tell me about the moment you decided to switch.') and active listening for emotional language, forces, and struggles. Emphasize that you do not mention the product or ask about features until the very end, if at all.
Careers That Require Jobs-to-be-Done framework theory and interview methodology