Non-Consumption JTBD
Core Concept
Non-consumption jobs can’t be validated through conversation. Nobody has pain about a job they’ve never hired anything for. You have to show the product to validate the demand — asking about it produces false negatives.
The Pattern
You interview potential users and ask about their current workflow. They describe it as working fine. No pain. No frustration. You conclude the problem doesn’t exist. But you were asking about the job they’re currently doing (well-served). The real opportunity is the job they’ve given up on entirely — the content they never consume, the tasks they never attempt, the value they’ve accepted losing. Non-consumption is invisible in interviews because people don’t miss what they never had.
Where I’ve Seen It
- Show Notes (Feb 2026): JTBD analysis revealed two jobs:
- Job A (“help me pick better”) — well-served by free solutions. 4/4 users satisfied.
- Job B (“help me get value from episodes I’ll never listen to”) — nobody hires anything for this because no solution existed. A typical heavy listener skips 35-40 episodes/week and is fine with it — but what if they could read all 50 in 20 minutes?
- Classic innovator’s dilemma pattern: You can’t validate non-consumption through conversation. You have to build the minimum viable product, put it in hands, and observe whether behavior changes.
The Countermeasure
- Look for what people have given up on, not what they’re struggling with.
- Ask about skipped content, abandoned tasks, accepted losses. “What episodes do you never listen to? What happens to them?”
- Accept that Mom Test has limits. For non-consumption jobs, set a small-cohort product test as the validation method.
- Set a clear kill threshold for the product test: “If 0/3 engage after 3 days, the job is dead.”
Related Patterns
- Validate-Before-Building — Validation method must match the job type
- Fishing-Pond-Effect — Non-consumption may be visible in some communities but not others