Jobs To Be Done (JTBD)… I believe I have a reasonable command of the framework, but I need to learn more about how to apply JTBD to the procedures used by my team.
When is it most useful during the product development process? While developing a plan in the beginning, or when creating the roadmap later on?
What do you do after you’ve located the JTBD? Start developing a remedy right now, or take additional time to comprehend the issues preventing your consumers from completing those JTBDs?
How does the result appear? Just a list of JTBD with priorities?
How are user stories and JTBD handled in comparison to other widely used concepts? Do you make an effort to connect every user story to a particular JTBD?
Never heard of such a framework but, here’s my two cents on your topic of JTBD:
After you have located the Jobs To Be Done (JTBD) using the framework, it is important to take some time to understand the issues preventing your customers from completing those JTBDs. This can be done through additional research and customer interviews to gain a deeper understanding of their needs and pain points.
Once you have a clear understanding of the problem, you can start developing potential solutions. It is important to remember that JTBD is an iterative process and it’s important to validate your assumptions about the problem and the potential solutions with your customers.
It’s also important to involve your team in the process, as they can provide valuable insight and expertise to help you develop effective solutions. Additionally, it’s important to consider the feasibility of the solutions and how they align with your organization’s goals and resources.
Therefore, it’s important to take additional time to comprehend the issues preventing your consumers from completing those JTBDs, before starting to develop a remedy.
A similar topic, this is an invaluable thread on the topic of product frameworks by Shreyas Doshi on Twitter:
Very useful thread @JuanAllo, but, it’s just a giant list of frameworks which isn’t that useful without understanding when/why each framework should be employed.
Fair evaluation @AnaRodriguez. I use it to browse through and create my own list of things I need for a particular task I’m attempting to do. There is no one framework that will work for all the products, efforts, and collaborations you need to complete, but that thread offers some useful examples of the questions and considerations you should make before starting something new.
I agree that there is no magic solution, however I have noticed that when I’m starting something, I read through that and get wonderful ideas from it.
On each framework, there is a ton of supporting information. It gives more insight into each one.
JTBD is a pain in the neck.
Anytime. If starting from scratch, the first step. You should always try to determine what tasks need to be completed.
Depending on the problem you’re attempting to address. Start solving if you’re in break/fix mode. You must better comprehend what is broken in this phase.
Output is completing the task. and using metrics to confirm that the work is being done in a way that the individuals enjoy.
A user story describes a task that needs to be completed. Yes, it ought to be connected to a job.
The JTBD framework is the closest thing to design thinking you can find, albeit I haven’t used it much. Here, it is intended to comprehend and illustrate in as much detail as possible the tasks that users are attempting to carry out. One option is to innovate and discover new solutions to the issue. Or it can be to provide a more thorough explanation of a well-known issue so that new solutions can be found. Discovery is unquestionably involved, and it should start as soon as feasible. Even so, a continuous workstream is really beneficial.
Since much has been said and written about JTBD framework, I would like to add about its implementation and output.
The output of the Jobs To Be Done (JTBD) framework can vary depending on the specific research and analysis methods used. However, typically the output is a prioritized list of JTBDs, along with an understanding of the problems and pain points that are preventing customers from completing those JTBDs.
The output can take many forms, depending on the needs of the project, but generally it will provide the following information:
- A clear definition of the JTBDs that the customers are trying to achieve
- A detailed understanding of the customers’ needs, wants, and pain points
- A prioritized list of JTBDs that are most important to the customers
- A set of potential solutions or product features that address the JTBDs
- A plan for validating the solutions and features with customers
This information can be used to inform product development, marketing, and customer service strategies. The output can be presented in a variety of forms, including a report, a presentation, or a set of user stories.
It’s important to note that the output should be tailored to the specific needs and goals of your organization, and it should be communicated effectively to the stakeholders.
Jobs To Be Done (JTBD) and user stories are related but different concepts that can be used together to inform product development.
JTBD is a framework that helps you understand the underlying problem that customers are trying to solve, and the pain points they are experiencing. It provides a clear, customer-centric view of the problem and can be used to inform the development of products and features that truly meet the customers’ needs.
User stories, on the other hand, are a way to express the requirements for a product or feature in a way that is easily understandable by both the development team and the customer. They are typically written in the format of “As a [customer], I want [this], so that [I can achieve that].” User stories are a way to capture the requirements for a product or feature, and they are a key tool for agile software development.
It is possible to tie each user story to a specific JTBD. By doing this, you can ensure that each user story is aligned with the customers’ needs and the underlying problem that they are trying to solve. This can help you to create more effective and user-centered products and features.
To tie user story with JTBD, you can use JTBD as a filter to validate if your user stories match the jobs that your customers are trying to achieve. Additionally, you can use JTBD language to write user stories, which can make it easier for the development team to understand the customer’s perspective and to create solutions that align with their needs.
It’s important to remember that JTBD and user stories are both important tools that can be used together to create more effective and user-centered products.
The Jobs To Be Done (JTBD) framework is a customer-centric approach to understanding and solving problems. It can be used in a variety of ways, depending on the specific needs and goals of your organization. Here are some general steps for using the JTBD framework:
- Identify the problem: Understand the problem that you are trying to solve and the customers that you are trying to serve.
- Research your customers: Conduct research to understand your customers’ needs, wants, and pain points. This can be done through interviews, surveys, or other research methods.
- Identify the JTBDs: Use the information from your research to identify the jobs that your customers are trying to accomplish. A JTBD is a specific problem or task that a customer is trying to solve.
- Prioritize the JTBDs: Prioritize the JTBDs based on their importance to the customers and the potential impact on your business.
- Understand the problems: Understand the problems and pain points that are preventing customers from completing the JTBDs.
- Develop solutions: Develop solutions or product features that address the JTBDs and the problems identified.
- Validate with customers: Test your solutions and features with customers to validate your assumptions and gather feedback.
- Iterate: Use the feedback from your customers to iterate on your solutions and improve them over time.
It’s important to remember that JTBD is an iterative process, and it’s important to validate your assumptions and solutions with your customers at every step of the way. Additionally, it’s important to involve your team in the process, as they can provide valuable insight and expertise to help you develop effective solutions.
Identifying the pain points is an important step in the Jobs To Be Done (JTBD) framework. It involves understanding the problems and difficulties that customers are experiencing while trying to accomplish the JTBDs. Some ways to identify pain points can be:
- Customer research and interviews: Conducting research and interviews with customers can provide valuable insights into the pain points they are experiencing. This can include conducting surveys, user testing, and focus groups.
- Observing customers in their natural environment: Observing customers in their natural environment can provide insights into the pain points they are experiencing. This can include watching customers use a product or service or observing them in the context of their daily lives.
- Analyzing customer feedback: Analyzing customer feedback from various channels such as social media, customer service interactions, or reviews can provide insights into the pain points customers are experiencing.
- Identify their current solutions: Understanding the current solutions that customers are using to accomplish the JTBD can also provide insights into the pain points they are experiencing. For example, if a customer is using a product that is not working well, this can indicate a pain point.
- Identify the unmet needs: Once you have a clear understanding of the JTBDs and the current solutions, you can identify the unmet needs of your customer.
Once you have identified the pain points, it’s important to prioritize them based on their importance to the customer and the impact they have on the customer’s life. This can help you to focus on the most important pain points and develop solutions that address them. It’s also important to validate your assumptions about the pain points with your customers to ensure that you are accurately identifying and addressing their needs.
The Jobs to be Done framework can be used to gain a deeper understanding of customers’ needs and motivations by focusing on the specific tasks or jobs they are trying to accomplish. To use this framework, start by identifying the job and defining it in a clear and specific way. Next, segment the market, develop solutions based on your understanding of the job and the customer segments, test your solutions with customers, and iterate based on their feedback. By following these steps, you can use the Jobs to be Done framework to tailor your product or service to specific customer needs and refine it over time.