Apply Clayton Christensen's Jobs-to-be-Done framework to AI product strategy. Learn how to position AI tools around the actual jobs customers hire them for, not feature lists.
By OperatorRadar Editorial
Clayton Christensen's Jobs-to-be-Done (JTBD) framework reframes product strategy around the functional, emotional, and social jobs customers are trying to accomplish—not around product categories or demographics. Instead of asking "Who is my customer?" you ask "What job is my customer hiring this product to do?" A classic example: people don't buy quarter-inch drills; they hire drills to make quarter-inch holes. The framework emerged from Christensen's observation that most new products fail not because they're poorly executed, but because they solve the wrong problem or frame the solution around features rather than outcomes.
Christensen introduced JTBD thinking in his 1997 work "The Innovator's Dilemma" and developed it further in "Competing Against Luck" (2016). The framework gained traction in product management and marketing circles as companies realized that traditional segmentation (age, income, geography) often missed why customers actually chose one product over another. By the 2010s, JTBD had become standard language in product strategy, particularly among founders building for underserved use cases. The framework's power lies in its simplicity: it forces you to think like your customer's circumstances, not your product's capabilities.
Christensen argued that products succeed when they align with the specific job a customer is trying to accomplish in a particular context. A job has three dimensions: functional (the task to complete), emotional (how it should feel), and social (how it affects identity or status). Success means your product becomes the obvious choice for that job—not because it's the cheapest or most feature-rich, but because it's the most reliable, convenient, or trusted way to get that job done. Messaging and positioning should therefore center on the job, not the product. You're not selling software; you're selling the outcome or relief the software enables.
AI products have made JTBD thinking both more critical and more complex. AI tools often blur traditional product boundaries—a language model can do writing, coding, research, brainstorming, and tutoring depending on context. Without JTBD clarity, founders default to feature-first messaging ("Our AI has 70B parameters") that confuses buyers and dilutes positioning. Conversely, AI's versatility means the same product can serve radically different jobs for different users. A founder must identify which job is primary, which secondary, and which to ignore. Additionally, AI's novelty tempts marketing toward hype ("AI will transform everything") rather than specific job outcomes. JTBD forces you to be concrete: "This AI helps customer-support teams reduce response time from 4 hours to 15 minutes" beats "AI-powered support platform." Finally, AI products often require customer education about what's possible; JTBD thinking helps you teach customers the job they can now accomplish, not the technology itself.
The core principle holds: customers don't buy products; they buy progress toward a goal. For AI products, this means your positioning, pricing, and feature roadmap should all ladder back to the specific job. A founder should still ask "What job is my customer hiring this for?" before writing a single line of marketing copy. Emotional and social dimensions remain as relevant as ever—a founder building AI for creative professionals must understand not just the functional task (generate images faster) but the emotional need (feel like a capable creator, not a tool operator) and social dimension (maintain professional credibility). JTBD also remains the best antidote to feature creep: if a feature doesn't directly serve the core job, it's distraction. Finally, the framework still works as a competitive moat. If you deeply understand the job and your competitors don't, you'll outposition them even if their AI is technically superior.
JTBD was developed in an era of slower product cycles and clearer product categories. In the AI era, jobs can shift rapidly as capabilities improve. A founder might identify a job correctly in month one, but by month six, the job has evolved or split into multiple jobs. This requires more frequent JTBD re-validation than Christensen's framework originally anticipated. Additionally, JTBD assumes customers have clarity about what job they're trying to accomplish. Many AI product buyers are still figuring out what's possible; they may not yet know the job they want to hire AI for. Traditional JTBD research (interviews, observation) can miss emergent use cases that only appear once users have hands-on experience. Finally, JTBD thinking can sometimes over-focus on the primary job and miss the secondary jobs that drive adoption. For example, an AI writing tool's primary job might be "write faster," but the secondary job—"avoid the blank page anxiety"—may be what actually drives daily usage. Founders need to hold both.
As a founder, start by identifying 3–5 candidate jobs your AI product could serve. For each, interview 5–10 customers or prospects in that role and ask: "Walk me through the last time you needed [this capability]. What were you trying to accomplish? What got in your way? How did you solve it before?" Listen for the job, not the feature. Then pick one primary job and ruthlessly align your messaging, onboarding, and initial feature set around it. Your positioning statement should sound like: "We help [customer type] [accomplish specific job] by [concrete outcome]." Example: "We help support teams reduce first-response time from hours to minutes by automating ticket triage." Not: "AI-powered support platform." Once you've nailed the primary job, document the secondary jobs and plan your roadmap to serve them in sequence. Finally, use JTBD to make trade-off decisions: if a feature doesn't serve your primary job, don't build it yet. This clarity will also help you price correctly—customers will pay for job completion, not for features.
Think about your AI product. What is the single most important job a customer is trying to accomplish when they use it? Now describe that job without mentioning your product, AI, or any features. Can you do it in one sentence? If you can't, or if your sentence includes product language, you haven't isolated the job yet. Try again, focusing on the customer's goal, not your solution.
Clayton Christensen
The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail
“Christensen introduced the foundational concept that products fail not due to poor execution but because they solve the wrong problem or are positioned around features rather than customer outcomes.”
Clayton Christensen
Competing Against Luck: The Story of Innovation and Customer Choice
“Christensen expanded JTBD framework to emphasize that jobs have three dimensions—functional, emotional, and social—and that successful products align with all three dimensions of the job customers are trying to accomplish.”
Bob Moesta and Chris Jones
Demand-Side Sales: Stop Selling and Help Customers Buy
“Modern JTBD practitioners emphasize that customer research should focus on understanding the circumstances and context in which customers hire products, not demographic segments.”
Struggling to articulate what job your AI product solves? Book a 30-minute positioning session with an OperatorRadar strategist. We'll help you isolate the job, validate it with your customers, and rewrite your messaging to lead with outcomes, not features.
Request implementationNeed a custom implementation?
Have Ekofi Lyrae design and implement AI agents and automations.