All frameworks and cheat sheets

Reference table

Two schools of Jobs to Be Done

Jobs as progress versus jobs as activities

Table comparing the two schools of Jobs to Be Done, Christensen and Moesta against Ulwick's ODI, on definition, method, output and best use.
Most teams end up using both: switch interviews for the why, outcome mapping for the what. Source: Clayton Christensen, Bob Moesta and Tony Ulwick

Jobs to Be Done has two main interpretations that people often mix up. Christensen and Moesta treat a job as progress in a circumstance and study it with switch interviews. Ulwick's Outcome-Driven Innovation treats it as a process with measurable outcomes and adds large surveys. This table helps you choose which school fits the question you are asking.

Where this appears

What's in this reference table

Christensen and MoestaUlwick (ODI)
What a job isThe progress a customer wants to make in a circumstanceThe functional process a customer executes
Unit of analysisThe struggling momentThe job process with measurable outcomes
Research methodSwitch interviews with 10 to 20 participantsJob mapping plus surveys of 200 to 500+
OutputNarrative insight into demandPrioritized opportunity map with scores
Best forUnderstanding why customers switchDeciding what to build next

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/jobs-to-be-done-two-schools-comparison"><img src="https://www.koji.so/visuals/jobs-to-be-done-two-schools-comparison/jobs-to-be-done-two-schools-comparison.png" alt="Table comparing the two schools of Jobs to Be Done, Christensen and Moesta against Ulwick's ODI, on definition, method, output and best use." width="1200" height="745" /></a>
<p>Source: <a href="https://www.koji.so/visuals/jobs-to-be-done-two-schools-comparison">Two schools of Jobs to Be Done</a>, Koji</p>