The Two Schools of JTBD: Christensen's Stories vs Ulwick's Metrics

The Jobs-to-be-Done debate splits into two schools because two different people built two different tools. Clayton Christensen and Bob Moesta treat a job as a story — the anxious, emotional narrative behind why someone "hires" a product. Tony Ulwick treats a job as a measurable process, scoring dozens of outcomes to rank opportunities. Both are legitimate; they answer different questions.

Quick answer: Christensen and Moesta's school treats "job" as a story — a switch interview reveals the struggle, anxieties, and social forces behind a purchase. Ulwick's Outcome-Driven Innovation (ODI) treats "job" as a process to measure — desired outcome statements get scored for importance and satisfaction. Most experienced JTBD practitioners use both, in sequence, rather than picking a side.

The Christensen-Moesta School: Jobs as Stories You Uncover

Clayton Christensen framed Jobs-to-be-Done as a theory of causation — people don't buy products, they "hire" them to make progress against a specific struggle. Bob Moesta turned that theory into a method: the switch interview, which reconstructs the timeline, anxieties, and social pressures that pushed someone from an old solution to a new one.

The milkshake study that started it

The clearest origin story is the milkshake research Christensen describes with Scott Cook and Taddy Hall in their 2005 Harvard Business Review article, "Marketing Malpractice: The Cause and the Cure." A fast-food chain wanted to sell more milkshakes and had already tried the obvious demographic tweaks — thicker, cheaper, more flavors — with no real lift. Researchers instead watched who bought milkshakes, when, and what else those people considered buying instead.

It turned out a large share of milkshakes were bought alone, in the morning, by commuters who wanted something dense enough to make a long drive less boring and clean enough to eat one-handed. The "job" had nothing to do with dessert. The milkshake was competing against bagels, bananas, and boredom — not against other milkshakes.

That reframing is the entire Christensen-Moesta contribution: stop asking what customers want in a product, and start asking what progress they're struggling to make. For a fuller walkthrough of that vocabulary — hire/fire language, functional versus social and emotional dimensions — see our complete guide to Jobs-to-be-Done, which both schools in this article build on.

Forces of Progress: push, pull, anxiety, habit

Moesta and longtime collaborator Chris Spiek packaged the switch interview's findings into a four-force diagram, later popularized in Alan Klement's 2016 book When Coffee and Kale Compete. It explains why customers switch even when a new product isn't objectively "better": progress requires enough push and pull to overcome the anxiety and habit anchoring someone to their current solution.

The four forces behave like a small system in their own right — push and pull reinforcing a switch, anxiety and habit balancing against it. It's the same reinforcing/balancing dynamic covered in our systems thinking guide, just scoped down to one customer's decision instead of an entire market or org.

Because the switch interview reconstructs a timeline — first thought, event, active looking, decision, early use — it overlaps heavily with timeline-based work like customer journey mapping. Teams that already run customer journey mapping often find the switch interview slots in as a deeper, causally-focused version of the same exercise.

The Ulwick School: Jobs as Outcomes You Score

Tony Ulwick built Outcome-Driven Innovation over more than a decade at IBM and later at his consultancy Strategyn, publishing the approach in a 2002 Harvard Business Review article and the 2005 book What Customers Want. ODI treats a job as a process decomposed into measurable desired outcomes, each scored by customers for importance and satisfaction.

Desired outcome statements

ODI's atomic unit isn't a persona or a feature request — it's a desired outcome statement, written in a strict grammar: a direction of improvement (minimize or increase), a metric, and the object being acted on, often with a contextual clarifier. For example: "Minimize the time it takes to confirm a shipment has cleared customs."

That grammar is deliberately narrower than Christensen's broad job statement or the "job story" format Intercom's product team popularized in the mid-2010s. If you're deciding which job statement format to standardize on for your team, it matters which school you're borrowing the format from — a Christensen-style statement and an Ulwick-style outcome are not interchangeable templates.

The Opportunity Score formula

Once outcomes are collected — often 50 to 150 per job, surfaced through qualitative interviews — Ulwick fields them in a quantitative survey, asking customers to rate each for importance and current satisfaction on a numeric scale. The resulting formula, Opportunity Score = Importance + max(Importance − Satisfaction, 0), surfaces outcomes that are important but poorly served: the ones worth building for.

The mechanics of that formula, including how to read a high opportunity score versus an already-satisfied outcome, are broken down in our Opportunity Score explainer. In practice, teams field ODI surveys across dozens to hundreds of respondents, which is why Ulwick's school reads as market research where Christensen's reads as ethnography.

Strategyn has applied variations of this methodology across telecom, medical device, industrial equipment, and software engagements for more than two decades, and Ulwick's later book, Jobs to Be Done: Theory to Practice (2016), formalized ODI into a repeatable, roughly eight-step process meant to run inside large product organizations rather than a one-off research project. That repeatability is the point: ODI is built to be run again next quarter, on a different feature set, by a different team, and still produce comparable scores.

Christensen-Moesta vs. Ulwick, side by side

Why the Same Word "Job" Starts So Many Arguments

Online JTBD debates are rarely about substance — they're about vocabulary collision. A "job story" (Intercom's template), a "job statement" (Christensen's broad functional, social, and emotional job), and a "desired outcome statement" (Ulwick's ODI) all get shortened to "job" in casual conversation, so two PMs can disagree loudly while describing entirely different artifacts.

The three formats aren't just stylistic variants — they're built for different jobs of their own:

• Job statement (Christensen): "When I'm commuting alone in the morning, I want something filling and easy to eat one-handed, so I can make the drive feel less boring." Broad and narrative; it deliberately carries social and emotional weight alongside the functional need.
• Job story (Intercom-popularized): "When [situation], I want to [motivation], so I can [expected outcome]." A lightweight template for writing tickets without accidentally specifying a solution.
• Desired outcome statement (Ulwick): "Minimize the time it takes to locate a parking spot near the office." Narrow and measurable, purpose-built to be scored across a survey population.

Picture a typical product-strategy thread. One commenter insists "the job is to feel like a competent parent" — a social/emotional job statement straight out of the Christensen school. Another replies "no, the job is to minimize the time it takes to get a toddler to sleep" — an Ulwick-style desired outcome. Both are legitimate research artifacts about the same underlying situation; they're just standing at different altitudes of it.

Layer a second disagreement on top: the two schools also disagree about what counts as evidence. A Christensen-style interview treats one vivid, well-reconstructed struggle as diagnostic — closer to anthropology than market research. An Ulwick-style survey treats a single interview as an anecdote, not evidence, until it's scored across a broader sample. Neither approach is wrong. One is optimized to answer "what should we even build," the other to answer "which of the forty things we could build should we build first."

Most JTBD arguments online collapse the moment someone asks: "Are we disagreeing about a story, or about a score?" Usually, the answer is that nobody was arguing about the same thing at all.

Most practitioners who've used both schools stop arguing about which is "correct" once they notice they were never competing for the same decision.

Where the Two Schools Actually Agree

Strip away vocabulary and the two schools agree on more than the average online thread suggests. Both reject demographics and firmographics as a valid basis for segmentation. Both insist the job stays stable over time even as the solutions competing for it change. Both treat progress, not features, as the real unit of customer value.

1. The job outlives the solution. Commuters have wanted a filling, one-handed breakfast for decades; the milkshake, the breakfast bar, and the smoothie have each taken a turn competing for that same stable job.
2. Segment by struggle, not by who the customer is. Neither school leans on age, income, or firmographic tier as the primary way to cut a market.
3. Competitors are defined by the job, not the category. A milkshake competes with a bagel; expense-report software competes with a shoebox of receipts and a spreadsheet.
4. Both distrust asking customers what feature they want. Christensen calls that "solution-space" thinking; Ulwick's entire methodology exists to separate a desired outcome from a proposed solution before anyone scores it.
5. Both care about non-consumption. Christensen's idea of competing against nonconsumption and Ulwick's underserved-outcome scoring point at the same overlooked opportunity: people currently doing the job badly, expensively, or not at all.

That shared foundation is exactly why the two schools combine so cleanly once a team stops treating them as rivals.

A Synthesis Playbook: Running Both Schools in One Project

The two schools aren't rivals to pick between; they're sequential stages of the same research. Run Christensen-style switch interviews first to find the job and its forces of progress, then convert what you heard into Ulwick-style outcome statements and score them at scale before you prioritize.

1. Interview 8-12 recent switchers. Reconstruct the full timeline — first thought, the event that forced the issue, active looking, decision, and early use. This is the Christensen/Moesta stage.
2. Extract the forces of progress from each story. Note the push, pull, anxiety, and habit named or implied; these explain hesitation that survey data alone won't surface.
3. Translate outcomes into ODI grammar. Turn "I wish it were faster to reconcile the report" into "Minimize the time it takes to reconcile a monthly expense report."
4. Field the outcome survey at scale. Score each outcome for importance and satisfaction across a broader sample, then compute Opportunity Scores to rank them.
5. Cross-check top-scoring outcomes against the forces of progress. A high-scoring outcome tied to strong habit or anxiety forces may need positioning and messaging work, not just a feature, before it converts anyone.
6. Write the job statement or job story for engineering. Make sure the underlying struggle and outcome survive translation into tickets — this is where teams most often lose the "why" behind the work; see how job statements survive the handoff to engineering for the specific failure modes to watch for.

Skipping straight to step 4 without step 1 is the most common mistake: teams score outcomes nobody validated qualitatively, and the survey dutifully returns a precise number for the wrong job.

Where Prodinja Fits Into This Debate

Most teams don't run this synthesis, not because they disagree with it, but because it requires two different research skillsets and two different tools that rarely talk to each other. Prodinja's Customer Jobs tool is built to hold both traditions in one workspace: it pairs Ulwick-style opportunity scoring with a Forces-of-Progress read drawn from the Christensen-Moesta school, so a job captured once can be scored quantitatively and interrogated narratively without switching contexts.

As a prototype, Prodinja's Customer Jobs module is designed to walk a PM through both lenses against the same underlying job data — the outcome-statement scoring on one side, the push/pull/anxiety/habit read on the other — rather than forcing a choice between the two schools before the research even starts.

Key Takeaways

• Christensen and Moesta's JTBD is qualitative and narrative — built around the switch interview and the forces of progress; Ulwick's ODI is quantitative — built around desired outcome statements and the Opportunity Score.
• Most online JTBD arguments are vocabulary collisions between job statement, job story, and desired outcome statement, not real disagreements about the underlying theory.
• Both schools reject demographic segmentation and agree the job stays stable even as the solutions competing for it change over time.
• Use switch interviews for discovery and positioning; use ODI scoring for prioritization and roadmap ranking — they're built to answer different questions.
• The four forces (push, pull, anxiety, habit) explain why a high-scoring outcome can still fail to convert a customer who's anchored by habit.
• The original struggle behind a job is most often lost in the handoff to engineering tickets — preserve it deliberately, in whichever format you standardize on.