The JTBD framework builds on Clayton Christensen’s idea that when we buy a product, we “hire” something to get the job done. If executed well, we hire that same product or service to do the job again and again. If it provides poor quality work, we “fire” the job and look for something else to solve the problem. Such an approach can be applied to our daily work to pursue more outcome-driven results. Follow these three steps to learn how.

2:00 min

Identify the essentials

All tasks are not created equal, and some require more attention than others to achieve maximum returns. When evaluating a project or goal, look for the following three key characteristics: are the jobs (i) stable and do not change over time, (ii) devoid of geographical or cultural boundaries, and iii) solution agnostic. The answers will help you categorise, define and capture the most important parts in any business scenario to focus on what matters and drive tangible results. To learn more about real-world examples, click here.

Create “job maps”

Serving as a blueprint, job maps are visual representations that deconstruct our goals and projects into distinct, bite-sized processes or steps. We can see the broader picture alongside the more granular parts, which can help pinpoint opportunities for improvement or allow us to connect the dots in new ways. Follow these 8 steps to generate a job map for your next project.

It’s never one-and-done

The JTBD method is a flexible approach to problem-solving and should be frequently adapted to the changing purpose of the task at hand. Within this context, we ought to exercise caution in using the JTBD method to avoid misapplications, warns Stephen Wunker, an entrepreneur and corporate venturer. Here are five ways to prevent such mistakes and reap the right business benefits.