Jobs-to-be-Done (JTBD) analysis

JTBD Is a Lens, Not a Process, and Most Teams Use It Wrong

Jobs-to-be-Done is one of the most powerful frameworks in product management. It is also one of the most misunderstood. When Clayton Christensen popularized the concept with his famous milkshake example, he gave product teams a deceptively simple insight: people do not buy products, they hire them to do a job. What happened next was decades of teams treating JTBD as a fill-in-the-blank template rather than a fundamentally different way of seeing customers.

The framework's popularity is well-deserved. According to a study by Strategyn, companies using outcome-driven innovation based on JTBD principles achieve an 86% success rate for new products, compared to the industry average of around 17%. A separate analysis by the Harvard Business Review estimated that over 30,000 new products are introduced each year, and 95% of them fail. The difference between success and failure often comes down to whether the team understood the job the customer was trying to get done.

The Problem

Most teams adopt JTBD by memorizing the job statement format: "When I [situation], I want to [motivation], so I can [expected outcome]." They fill in the blanks, add it to their PRD, and move on. This is like learning a musical scale and believing you can now compose a symphony.

The real power of JTBD lies in three insights that most teams miss:

• Jobs are stable over time. The job of getting from point A to point B has not changed in centuries. Only the solutions change. This means JTBD analysis should inform long-term strategy, not just feature development.
• Customers hire and fire solutions. Understanding what a customer is switching from, and why, reveals more than any feature request.
• Functional jobs have emotional and social dimensions. A project management tool is hired to track tasks (functional), reduce anxiety about deadlines (emotional), and signal competence to leadership (social).

How This Prompt Works

The JTBD Analysis prompt guides you through a structured exploration of the jobs your customers are hiring your product to do:

• Core functional jobs broken down into steps of the job map
• Related emotional and social jobs that influence purchasing decisions
• Current solutions being hired and fired, including non-obvious competitors
• Underserved outcomes where current solutions fall short
• Overserved outcomes where you may be over-investing

You provide your product and customer context, and the prompt produces a comprehensive JTBD analysis that goes beyond surface-level job statements.

When to Use It

• During early discovery when defining who your customer really is and what they need
• When entering a new market and you need to understand the competitive landscape through the customer's lens
• When feature prioritization feels arbitrary and you need a framework for evaluating competing demands
• When customer research has produced data but not insight

Common Pitfalls

• Defining jobs too broadly. "Manage my business" is not a job. "Ensure I never miss a customer follow-up" is.
• Confusing jobs with solutions. "I need a dashboard" is a solution. The job might be "Quickly assess whether my team is on track this week."
• Ignoring the switching cost. Customers do not switch to a new solution just because it is better. The pain of the current situation must outweigh the cost of change.
• Treating JTBD as a one-time exercise. Jobs evolve in context and importance. Revisit them quarterly.

Sources

• Competing Against Luck by Clayton Christensen is the definitive book on JTBD theory and its application to innovation.
• Strategyn: Outcome-Driven Innovation details how to operationalize JTBD into a repeatable innovation process.
• Intercom on Jobs-to-be-Done provides a practical, product-focused guide to applying JTBD in a technology company.