As product managers, we're obsessed with understanding our users. But often, we get caught in the trap of features and functionality. We focus on what we think users need, instead of uncovering the underlying reasons why they buy our products. This is where the Jobs-to-Be-Done (JTBD) framework enters the scene. It's a powerful tool that helps us shift our perspective from product-centric thinking to a customer-centric approach.

​

Understanding different approaches within the JTBD framework through an example ‘Users want to keep a track of their water intake’:

1. Tony Ulwick's Outcome-Driven Innovation (ODI):

 --> Approach: Ties customer success metrics to their jobs-to-be-done, making innovation measurable and predictable. It identifies customer needs as "outcomes" and designs products to meet these precisely.

--> Example: ODI would begin by identifying the specific outcomes users desire from a water tracking app. These might include accurately logging water intake, receiving reminders to stay hydrated or improving overall health. The approach would quantify the importance of these outcomes and the users' satisfaction with current solutions, aiming to innovate where the gaps are largest.

 

2. Clayton Christensen's JTBD framework:

--> Approach: Suggests consumers "hire" products to do a job. It's useful for identifying disruptive innovation opportunities by exploring the actual customer needs and motivations.

--> Example: Tracking daily water intake is about more than hydration; it’s tied to users’ broader goals around health, wellness, and self-improvement. The job might be framed as helping users feel better, stay healthy or achieve personal wellness goals. A solution might not only focus on tracking but also integrate motivational elements, wellness tips and personalized hydration needs based on the user's lifestyle.

​

3. Bob Moesta's JTBD framework:

--> Approach: Emphasizes understanding the emotional and psychological "push" and "pull" factors that influence consumer decisions. Moesta uses deep-dive interviews and "Forces Diagrams" to map out the decision-making process, offering insights into complex consumer behaviors. 

--> Example: The focus would be on understanding why users start thinking about tracking their water intake and what makes them switch from not tracking to tracking. It could be dissatisfaction with their physical condition, forgetting to drink water regularly or learning new information about hydration's benefits. The innovation would directly address these triggers, possibly through a user-friendly app that makes tracking effortless and educates users about the importance of hydration.

 

Determining the "best" Jobs to Be Done (JTBD) framework depends on your specific objectives, the nature of your business, the complexity of the customer decision-making processes you're addressing, and the type of innovation you're pursuing.

• Tony Ulwick's Outcome-Driven Innovation (ODI):

  • Best for: Companies looking for a structured, measurable approach to innovation.

  • Strengths: Provides a systematic way to identify and prioritize customer needs based on specific outcomes. It's highly actionable for product development.

  • Use it when: You have access to detailed customer data and want to align product development closely with customer-defined success metrics.

• Clayton Christensen's JTBD Framework

  • Best for: Organizations seeking to understand the broader context of customer choices and uncover disruptive innovation opportunities.

  • Strengths: Focuses on the narrative and circumstances around customer decisions, offering deep insights into consumer behavior.

  • Use it when: You're exploring new market opportunities or trying to understand the root causes behind customer preferences and behaviors.

• Bob Moesta's JTBD Framework

  • Best for: Projects that require a deep understanding of the emotional and psychological factors influencing customer decisions.

  • Strengths: Emphasizes the emotional journey and the push/pull dynamics in customer decision-making, using tools like Forces Diagrams for insights.

  • Use it when: You need to delve into complex consumer behaviors, especially where emotional and psychological factors play a significant role.

 

How to integrate the Jobs to Be Done (JTBD) framework with other user research methods using the example of users wanting to keep track of their water intake. This example will show how different research techniques can complement JTBD insights to develop a product that meets this specific need.

1. Ethnographic Research

• Application: Observe users in their daily routines to see when and how they think about hydration. Note the contexts that remind them to drink water, any existing solutions they use, and the struggles they face in staying hydrated.

• Insight: You might discover that users remember to drink water only when they see a water bottle or feel thirsty, indicating potential solutions that make water intake more visible or preemptively remind users before they feel thirsty.

2. Surveys and Questionnaires

• Application: Distribute surveys asking about water intake habits, satisfaction with current tracking methods, and the importance of hydration. Include questions about features they would value in a water tracking app.

• Insight: Survey results could highlight a demand for features like personalized hydration goals, integration with fitness trackers, or social sharing capabilities.

3. User Personas and Segmentation

• Application: Create user personas based on different hydration goals and struggles identified through JTBD interviews. For example, a fitness enthusiast, a busy professional, and a health-conscious parent might have distinct jobs related to water intake.

• Insight: Tailoring app features to these personas, such as workout hydration plans for the fitness enthusiast or easy tracking for the busy professional, can make the solution more appealing to diverse user segments.

4. Customer Journey Mapping

• Application: Map out the customer journey of trying to stay hydrated throughout the day. Identify touchpoints where users feel the need to track their intake, potential obstacles, and opportunities for intervention.

• Insight: This might reveal that users often forget to drink water during busy work hours or lack motivation in the evening, suggesting features like smart reminders or gamification to encourage consistent intake or a simple, intuitive water tracking app.

5. Usability Testing

• Application: Conduct usability tests with prototypes that address identified jobs, observing how easily users can log their water intake, set goals, and interact with hydration reminders.

• Insight: Testing might show that users prefer logging intake with minimal taps or using voice commands, leading to design optimizations for ease of use.

6. Employ Prototyping and Concept Testing with JTBD

• Application: After initial feedback, you develop a feature allowing users to log water intake with a single tap and test this concept with users.

• Insight: Feedback indicates that this feature significantly reduces the effort to track water intake, effectively fulfilling the job users hired your product to do.

 

Integration and Development Outcome

Through this integrated approach, you've identified that users hiring a solution for tracking water intake are primarily looking to maintain health effortlessly and be reminded to stay hydrated. Based on these insights, you develop an app that is simple to use, integrates reminders, and offers an intuitive single-tap log feature, directly addressing the identified jobs and improving the likelihood of adoption and satisfaction.