The Jobs to be Done (JTBD) Framework

[admin]

The Jobs to be Done (JTBD) Framework1. Core Definition and PhilosophyThe Jobs to be Done (JTBD) framework is a theory of customer action developed by Clayton Christensen and popularized by others like Tony Ulwick and Bob Moesta.The core philosophy is simple: Customers don't buy products; they hire them to do a "job."Instead of focusing on who the customer is (demographics) or what the product is (features), JTBD focuses on the progress the customer is trying to make in a specific circumstance.The JTBD PrincipleA "Job" is a stable, enduring process or problem that a customer is trying to solve. Technology and products change, but the underlying job remains constant.

• Example: People in the 19th century and the 21st century both had the job of "connecting with distant loved ones." The product they hired changed from the telegraph to landlines to email to smartphones, but the job is the same.

The job itself is comprised of three main dimensions:

1. Functional Job: The practical, measurable task the customer is trying to achieve (e.g., "Transport me from Point A to Point B").
2. Emotional Job: How the customer wants to feel, or avoid feeling, by completing the task (e.g., "Feel safe and relaxed during the journey").
3. Social Job: How the customer wants to be perceived by others when using the product or service (e.g., "Look environmentally conscious or successful").

2. Key Framework Components and ExamplesThere are generally two major schools of thought within JTBD, often used in conjunction: the Needs-Based (or Outcome-Driven) approach and the Activities-Based approach.A. The Classic "Needs-Based" Example (The Milkshake Job)This is the most famous example used to explain the concept of hiring a product.The Product: A McDonald's Milkshake. Traditional Analysis: Focuses on improving the product (better flavor, cheaper price, thicker consistency). JTBD Analysis: Researchers interviewed customers buying milkshakes early in the morning.The Customer's Job to be DoneThe Context and ProgressWhy the Milkshake was Hired

Functional: "Make my long, boring morning commute interesting."	Driving alone, needing something to consume that takes a long time and isn't messy.	It's thick (takes 20 minutes to drink), it's easy to hold, and it fills them up until lunch. It beat out bananas (too fast) and bagels (too messy).
Emotional: "Feel productive and momentarily happy during a dull task."	The small indulgence provides a feeling of progress and satisfaction.

The Innovation: McDonald's didn't change the flavor; they changed the product delivery based on the job: making the straw smaller (to slow down consumption) and putting the purchase station closer to the drive-thru window (to speed up hiring).B. The Structured "Activities-Based" Example (The Job Statement)This approach focuses on defining a precise, solution-agnostic statement that captures the core job.The Job Statement Formula:$$\text{Verb} + \text{Object} + \text{Contextual Clarifier}$$Product AreaJob StatementImplications (Competition)

Drilling/Construction	Minimize the time required to secure an item to a surface.	The customer doesn't want the drill or the hole; they want the picture hanging on the wall. Competition is anything that solves this: adhesive strips (Command Strips), specialized hooks, or strong magnets.
Video Conferencing	Enable a remote team to collaborate effectively on a shared project.	The competition isn't just other software (Zoom/Teams); it's also a lack of collaboration (doing it via email) or flying everyone into the office.
Personal Finance	Ensure my family can maintain its lifestyle if I become disabled.	The job is not "buy insurance." It's about securing future well-being. This job competes with savings accounts, investment portfolios, and life insurance policies.

3. Pros and Cons of the JTBD FrameworkThe JTBD framework is a powerful tool, but it presents specific challenges, particularly during implementation. Pros (The Benefits)ProDescription

Focus on Innovation	JTBD encourages non-obvious competition. Instead of only competing with product clones, you look at all products or methods a customer currently hires to do the job, which opens the door to radical, job-specific innovation (e.g., Milkshake vs. Bagel).
Better Segmentation	Customers are segmented not by their age or income, but by the job they are trying to do. This allows product teams to serve specific needs with higher precision (e.g., separating the job of "morning commute" milkshake buyers from "afternoon treat" buyers).
Drives Marketing Clarity	Once the job is understood, marketing copy can focus entirely on the customer's desired progress and outcome, rather than just listing features. (e.g., “Get that picture hung in 30 seconds” vs. “Our drill has 18V power.”)
Stable Product Roadmap	Since the job itself is stable and enduring, the product roadmap becomes less vulnerable to short-term trends. It provides a long-term anchor for development efforts.

Cons (The Challenges)ConDescription

Difficulty of Initial Research	Uncovering the true job requires deep, qualitative interviews (often called "Job Interviews"). It's easy to mistake a solution for a job (e.g., "I need a better spreadsheet" vs. "I need to visualize trends quickly").
Requires Abstraction	The framework requires practitioners to think on a higher, solution-agnostic level, which can be unnatural for product teams accustomed to features and specs. The definition of the "core job" can be highly subjective and difficult to align across teams.
Measuring Success is Hard	While functional jobs can be linked to metrics (e.g., "minimize wait time"), emotional and social jobs are often harder to quantify and measure success against. Standard business metrics (e.g., conversion rate) may not capture progress on the job itself.
Risk of Over-Simplification	Complex enterprise products often satisfy hundreds of sub-jobs for different stakeholders. Reducing this complexity to a single, elegant "Job Statement" risks overlooking crucial functionality needed by specific user groups.