Unlock the power of AI to decode the hidden needs of consumers and redefine industry landscapes by discovering the true "Job-to-be-Done." While there are people that try to teach you this, it's a very nuanced thing.

So, would you rather start from scratch staring at the wall? Or would you like a swift kick in the rear that moves you down the road to success quickly, and inexpensively?

Dive into the fascinating complexity of identifying the end user in the Jobs-to-be-Done framework, where you'll unravel the "chicken and egg" relationship between the end user and the job they aim to accomplish. This lesson offers you invaluable tools to rigorously assess and select the right end user, ensuring that your solutions are laser-focused on meeting real-world needs.

© 2023 Practical JTBD, LLC. All rights reserved. This work is provided for the exclusive use of authorized individuals in industry innovation and strategy roles and may not be reproduced, distributed, or commercially exploited in any manner whatsoever. Unauthorized use is strictly prohibited and subject to legal action.

Understanding context is vital in JTBD because it defines how and why customers use products or services differently. The specific setting—be it a government agency with its regulations or a healthcare environment prioritizing patient care—affects the job's requirements and constraints. Collecting diverse context data is key for nuanced solutions, as it highlights variations in customer needs and informs more targeted and effective product development.

Situations (or Complexity Factors) describe the environment in which people are trying to get the Job done. In most cases, they may face multiple situations and these will help you to explain why one group of people responding to a survey struggle differently than another group.

In some ways you can look at related jobs as job steps, but the purpose of them is to look for organic growth paths beyond the Core Job your are studying. It’s possible that Job has been almost completely automated and at that point you need to know where to look next. They very well could be steps in a Core Job that is one level higher than your current focus. 

Getting to the right job statement is sometimes very hard. Everyone has a different opinion. Instead of coming up with ideas or iterating through expensive interviews or time-consuming stakeholder workshops, simply generate a set of statements above and below your current hypothesis and use these to accelerate your alignment.

Emotional Jobs are merely statements that respondent rate a scale of importance and satisfaction / difficulty related to how a respondent wants to feel, or avoid feeling when trying to get a job done.  Social Jobs are merely statements that respondent rate a scale of importance and satisfaction / difficulty related to how a respondent wants to be perceived, or avoid being perceived when trying to get a job done. Using them in combination will help you to understand what might drive desired behaviors when communicating with specific segments, or sub-groups. 

Financial Metrics help use to understand what is most important to either people who are the purchase decision-maker, or to those who are providing products and services. They are fundamentally different, so each job considers that perspective when offering such success measures.

This is a list of ideal states that an end user might be trying to achieve; similar to the top end of a capability maturity scale. Each of these will have a set of potential root causes that you can use in your survey, e.g., Select all that Apply, if you’d like to capture additional information.

These outputs complement the the Ideal State and provide you with a means to externally, or internally make determinations about what is preventing your end users from achieve the ideal state. This is a foothold into the solution-space and solutioning.

This is what most tools try to output for you. However, this prompt is on steroids because I know all of the rules, I've learned how to interrogate OpenAI. I've been trained by the best and there is only a small universe of practitioners that can claim that. If you want Job Maps this'll give you job maps!

This is the heart and soul of identifying customer needs. Using Large Language Models (LLMs) as the foundation to replace interviewing a handful of biased end users with biased researchers is the breakthrough we've all been waiting for.

Eliminate the repeated time and cost required to create customer success metrics for any Job-to-be-Done you can imagine in the blink of an eye and without someone hoovering money out of your wallet over and over again.

There's nothing like seeing something unfold to better understand it. This module will be the place where I can demonstrate from beginning to end, how we might build a value model for a specific problem.

A new demonstration every week - sometimes with guest appearances.