The Jobs-to-be-Done framework helps startups understand why customers buy, not just what they buy—but it comes in two distinct flavors, and choosing the wrong one can waste scarce research time. The "Forces of Progress" approach developed by Clayton Christensen and Bob Moesta digs into the causal story behind a purchase through in-depth interviews. The "Outcome-Driven Innovation" approach associated with Tony Ulwick aims to make customer needs measurable so product decisions can be prioritized with data. Neither is definitively better; each fits a different startup stage and market context, and this guide explains how to tell them apart and pick your path.
Understanding the Core of Jobs-to-be-Done
At its heart, Jobs-to-be-Done (JTBD) is a lens rather than a technique. The Christensen Institute, the organization founded around Clayton Christensen's disruption research, describes JTBD as "a lens that reveals the circumstances—or forces—that drive people and organizations toward and away from decisions." The core premise is that customers essentially "hire" products to accomplish something in their lives, and that hiring decision is shaped by more than product features.
Those decisions are never purely functional. The Institute emphasizes that all jobs incorporate "functional, social, and emotional forces at play in decision-making." A startup selling tax software, for example, is not just competing on calculation accuracy—the customer may also want to feel competent and avoid the social embarrassment of a filing error. The framework's practical power is illustrated by an analysis the Institute recounts in which the main job for many customers turned out to be spending less time on their taxes; that insight led to product simplification and an increase in sales.
For startups chasing product-market fit, this reframing matters because demographic profiles and feature checklists say little about why a customer switches from one solution to another. JTBD shifts the question from "who is the customer" to "what is the customer trying to accomplish, and what is holding them back."
The 'Forces of Progress' Approach (Christensen & Moesta)
The Forces of Progress school grew out of work in the mid-nineties, when Bob Moesta—now president and CEO of the consultancy The Re-Wired Group—helped develop the JTBD framework alongside Harvard Business School professor Clayton Christensen. Moesta has continued developing and applying the framework to everyday business challenges since then, according to The Re-Wired Group's own account of the theory's origins.
The defining question of this approach is what is pushing or pulling a customer toward a new idea or product—and, implicitly, what anxieties and habits hold them back. The Re-Wired Group frames the demand side of the framework around these competing forces, treating a purchase as the outcome of a struggle in which the push of dissatisfaction with the current situation and the pull of a new possibility must overcome inertia and fear of change.
Methodologically, this school is qualitative and narrative-driven. JTBD research in this tradition "often consists of Jobs interviews," The Re-Wired Group explains, and the emphasis is on "listening to people who have recently made a change—not about what they bought, but rather why they bought." Reconstructing the timeline of a real decision—the first thought, the evaluation, the anxiety before the switch—reveals the hiring criteria customers actually used and the intersection of the hiring criteria and demand frameworks.
The output is not a statistical ranking of needs. It is a set of causal stories: rich, contextual narratives of customer struggle that expose the emotional and social dimensions of the job alongside the functional ones. That makes the approach especially valuable when a startup does not yet know its market well enough to know what to measure.
The 'Outcome-Driven Innovation' Approach (Ulwick)
Tony Ulwick's school, formalized in Outcome-Driven Innovation (ODI), takes the same underlying insight in a more measurable direction. In his books What Customers Want and Jobs to be Done: Theory to Practice, Ulwick redefined how innovators think about their customers, in the words of Strategyn, the firm he founded: his "importance and satisfaction framework for a customer's 'jobs to be done' has influenced a generation of marketing and innovation professionals."
Where the Forces of Progress school asks why a customer switched, the ODI school asks how well any solution helps the customer get the job done, and where the measurable gaps are. The importance and satisfaction framework evaluates customer needs on both dimensions—which outcomes matter most, and how satisfied customers are with current solutions—so that unmet needs can be identified and prioritized rather than merely described. Strategyn's material stresses that innovation's core principle is "to help customers complete their jobs better or more affordably."
ODI also widens the unit of analysis beyond the end user. Strategyn notes that the approach "ensures that products not only perform well for end-users but also satisfy the concerns of those involved in their acquisition and upkeep"—an important consideration for B2B startups selling into organizations where the person executing the job is rarely the only party involved in the purchase.
For growth planning, Strategyn packages ODI into what it calls the JTBD Growth Strategy Matrix, which outlines five key strategies for helping customers complete jobs better or more affordably, along with guidance on when to use each strategy and what is needed for success. The output of an ODI engagement is therefore closer to a prioritized, data-grounded roadmap than to a set of interview narratives.
Comparing Jobs-to-be-Done Methodologies for Startups
The table below contrasts the two schools across the dimensions a founder actually needs to weigh: what each assumes, what it produces, and what kind of startup situation it serves. Neither methodology was designed to be universally superior, so the comparison's purpose is fit, not ranking.
| Dimension | Forces of Progress (Christensen/Moesta) | Outcome-Driven Innovation (Ulwick) |
|---|---|---|
| Core concept | Customers are pushed and pulled toward or away from new solutions by forces at play in their circumstances; jobs combine functional, social, and emotional elements. | Customer needs are defined as the outcomes people want when executing a job, evaluated through an importance-and-satisfaction framework. |
| Primary goal | Understand why customers made a change—uncovering the causal mechanisms behind purchase decisions and struggle. | Identify and prioritize unmet needs so innovation efforts can reduce risk and help customers complete jobs better or more affordably. |
| Research method | Qualitative Jobs interviews with people who recently made a change, focused on why they bought rather than what they bought. | Framework-based evaluation of needs by importance and satisfaction, applied through a structured practice developed at Strategyn. |
| Typical output | Narratives of customer struggle revealing hiring criteria and demand, including emotional and social dimensions of the job. | Prioritized innovation direction; Strategyn's JTBD Growth Strategy Matrix outlines five growth strategies with conditions for each. |
| Best for | Startups in nascent or unfamiliar markets that need to understand the "why" behind behavior before deciding what to build. | Startups refining an existing product or entering a market where the job is known and needs must be measured and prioritized. |
The "Best for" row is an inference from each methodology's emphasis rather than a tested rule: the qualitative, causal focus of Forces of Progress suits the uncertainty of early exploration, while ODI's measurable, framework-driven approach suits situations where the job is understood and the question is where to invest next.
Practical Steps for Startups to Apply JTBD
Whichever school a startup leans toward, the first practical move is the same: talk to people who have recently switched. The Re-Wired Group's guidance is explicit that JTBD research often consists of Jobs interviews with people who have recently made a change, and that the discipline lies in asking about why they bought rather than what they bought. For a resource-constrained startup, a handful of these conversations produces more actionable material than a large survey of people who have never wrestled with the problem.
Second, map who is actually involved in getting the job done. Strategyn's account of the framework distinguishes the end user from "those involved in their acquisition and upkeep," and its approach is designed to satisfy the concerns of that wider group. A startup selling to businesses should therefore identify both the person executing the job and the others—the buyer, the maintainer, the budget approver—whose concerns shape whether the product sticks.
Third, structure the inquiry around the forces at play. The Re-Wired Group's framing offers a concrete prompt for interview design: what is pushing or pulling the customer toward the new idea or product? Paired with the Christensen Institute's insistence that functional, social, and emotional forces all operate in decision-making, this gives an early-stage team a repeatable question set without needing any proprietary tooling.
This is an introduction to applying the JTBD mindset, not a full research training program, and the detailed worksheets and matrices that consultancies like Strategyn offer are proprietary. A startup can begin with interviews, customer-type mapping, and the forces framing before deciding whether to invest in a more formal ODI engagement.
Making Your JTBD Decision: A Startup's Next Steps
Startup founders should choose between the 'Forces of Progress' and 'Outcome-Driven Innovation' methodologies based on whether their primary need is deep qualitative understanding of customer struggle (Forces of Progress) or quantitative validation and prioritization of unmet needs (Outcome-Driven Innovation). If your team cannot yet explain why anyone abandons their current solution for yours, start with Jobs interviews in the Moesta tradition. If the job is well understood but you are deciding among many possible improvements, evaluate needs on importance and satisfaction the way Ulwick's framework prescribes.
The measurable indicator of having made this decision well is concrete: a clear articulation of the chosen JTBD methodology in the startup's product strategy document, followed by the initiation of customer interviews or surveys aligned with that methodology. Once those first conversations or need evaluations are underway, the next milestone is whether the resulting insights change your roadmap—and, as the Christensen Institute's tax-software example shows, whether simplifying around the real job moves sales.
Sources
- Jobs to Be Done Theory - Christensen Institute
- What is the Jobs to be Done framework? — The Re-Wired Group
- Jobs-to-be-Done — Strategyn




