The principle. Clayton Christensen's Jobs-to-be-Done (JTBD) framework: customers "hire" a product to make progress in a specific situation. The product is a means; the job is the end. Discover the job, and you stop selling features.
The classic milkshake story. McDonald's wanted to sell more milkshakes. Researchers asked existing buyers why they bought one. Answer: morning commuters needed something to occupy their hand and stay full until lunch — the job was "make my boring drive less boring without messing up my shirt." Competitors weren't other shakes. They were bagels (too crumbly), bananas (gone in 2 minutes), and donuts (greasy fingers). The fix: thicker shakes, faster checkout. Sales jumped.
The four-question JTBD discovery.
- The trigger. "What was happening when you started looking for a solution like this?" — surfaces the real pain moment, not the vague problem.
- The hire. "What does success look like — what's the outcome that would let you stop thinking about this problem?"
- The competition. "What else did you consider, including doing nothing?" — the do-nothing option is your real competitor 60% of the time.
- The anxieties. "What would have to be true for you to not buy a solution at all?" — surfaces the forces of inertia.
Why this beats feature-led discovery. Feature-led discovery ("do you need integrations? reporting? SSO?") gets you a spec sheet. JTBD discovery gets you the story — and stories close deals because they tie your product to a moment of progress the buyer is desperate to make.
Sales asset that comes from JTBD. A one-page "before/after" map: their world today (anxiety, friction, bad outcomes) → the moment of progress your product creates → their world after. Send it to them. They'll forward it to their boss for you.