Is the specification of the jobs to be done within an organization and the ways in which those jobs relate to one another?

The jobs-to-be-done framework is an approach to developing products based on understanding both the customer’s specific goal, or “job,” and the thought processes that would lead that customer to “hire” a product to complete the job.

When using this framework, a product team attempts to discover what its users are actually trying to accomplish or achieve when they buy a product or service.

How Does the Jobs-to-be-Done Theory Apply to Product Development?

Like other prioritization frameworks for product development, the jobs-to-be-done (JTBD) approach removes the focus from the product itself, and places it on the customer.

Where this framework differs, though, is that it then takes the next step to explore customers’ true motivations for buying. In the often-used example, the surface-level explanation is, “I need a drill.” Probing a little deeper, we discover the customer actually needs a well-drilled hole.

But the jobs-to-be-done theory takes this probing deeper still. As a result, it can help a product team uncover the underlying goal that users are trying to achieve: the enjoyment of seeing a picture hanging in their living room.

As entrepreneur and author Guerric de Ternay explains, product managers can use the jobs-to-be-done framework in two ways:

1. To get a better understanding of what their market wants or needs

2. To create a compelling customer experience

As the book The Innovator’s Toolkit explains, a job to be done is neither a product nor a solution itself; rather, it is the higher purpose for which a customer would buy a product and solution.

Is the specification of the jobs to be done within an organization and the ways in which those jobs relate to one another?

What is the Origin of the Jobs-to-be-Done Framework?

The jobs-to-be-done framework was developed by Tony Ulwick, founder of the innovation consulting firm Strategyn. In fact, JTBD began as Ulwick’s patented process called Outcome Driven Innovation (ODI), a framework focused on identifying outcomes that customers seek, as opposed to products they want.

According to Ulwick’s book, Jobs to Be Done, since taking the theory to market in 1991, his company Strategyn has used the JTBD framework with hundreds of client companies, and those businesses have enjoyed an 86% success rate applying the jobs-to-be-done theory to develop and improve their products.

What are Pros and Cons of JTBD?

Pros of jobs-to-be-done

1. It can help you better align what you’re building with what your users really want.

Because the job metaphor forces product teams to delve deeper into what their customers actually want, JTBD can help focus product development on solving problems as opposed to building features.

2. It can keep you from building “a faster horse” that nobody wants.

Part of the JTBD approach involves asking “Why” and “What.” Why do your customers want a specific feature? What is their true desired outcome? What is the emotional state they’re hoping your product will give them?

With many approaches to product development, organizations ask their target user personas what they want —and then build what their users tell them to. The problem with this approach is that your users often don’t have the vision or vocabulary to explain exactly what they want, especially if nothing like it has reached the market yet.

This is why when Henry Ford asked potential customers what they wanted in terms of better transportation, many answered, “A faster horse.” By applying the jobs-to-be-done framework, you can help uncover not just what your users think they want, but what your users actually want — and why.

Cons of jobs-to-be-done

1. It can lead your user research to become too abstract and high-level.

Although it involves a lot of probing to uncover your customers’ true motivations, JTBD still requires you to translate those underlying customer goals or “jobs” into practical tools or solutions to build.

One risk with this framework is that product teams can get lost in the abstract — “Our users want to become the hero at work” — which can lead to difficulty in prioritizing the strategic roadmap for the actual product.

2. Some product teams believe it can lead to lackluster design and user experience.

JTBD has become extremely popular with the product and innovation community. But some worry that because the framework places so much emphasis on the product’s ultimate purpose for a user, the product team will focus only on this purpose — to the exclusion of other important elements such as design aesthetics and overall user experience.

In other words, if your users want a drill only for the enjoyment of seeing a beautiful painting hanging on their wall, your product team might become exclusively focused on meeting that single objective, which could lead to a drill that isn’t designed with comfort or ease-of-use as a priority.

Is the specification of the jobs to be done within an organization and the ways in which those jobs relate to one another?

Is Jobs-to-be-Done is Worth a Try for Any Product Team?

JTBD begins with the logical theory that people buy any product or service to get something done or to achieve a specific desired state.

Even if your team typically uses a different prioritization framework in your product development, applying the jobs-to-be-done theory is a worthwhile effort. It can help give your team a different perspective — and possibly a deeper level of understanding — about why your customers buy your products, and how you can make them better.

Learn more about prioritization in the following webinar.

Is the specification of the jobs to be done within an organization and the ways in which those jobs relate to one another?

“Job-to-be-done” changed the way I am looking at the startup I am involved with. It forces you to look at other perspectives and for many people “jobs to be done” involves a mindset change. It forces you to look at our product the way customers do.

Clayton Christensen described this concept in this paper he wrote with one of the best tech entrepreneurs and product marketers of all-time, Scott Cook of Intuit. Recently one of the pioneers of this concept, Bob Moesta, started a consultancy and great podcast around this concept. They even have a Twitter hashtag (#JTBD) about the topic.

The theory simply asks, “What job your product is hired to do?”. For instance, most people would say they buy a lawnmower to “cut the grass,” and this is true. But if a lawnmower company examines the higher purpose of cutting the grass, say, “keep the grass low and beautiful at all times,” then it might forgo some efforts to make better lawnmowers in lieu of developing a genetically engineered grass seed that never needs to be cut.

This is the power of the JTBD concept and technique: It helps the innovator understand that customers don’t buy products and services; they hire various solutions at various times to get a wide array of jobs done. You may need light survey design and sampling help from a statistician to apply this technique, but for the most part it requires no expert assistance, so you can try to use it right after you finish reading this article.

1. Identify Jobs Customers Are Trying to Get Done

Henry Ford didn’t think about the “job” as a “faster horse” but as “getting from Point A to Point B as quickly as possible.”

You want to study customers and find out what they are trying to accomplish — especially under circumstances that leave them with insufficient solutions relative to available processes and technologies. What jobs have ad hoc solutions or no good solutions? When you see customers piecing together solutions themselves, these are great clues for innovation.

Christensen would assert that people buy any product to get a job done. The best example he gives is describing market research he and his team did to understand fully why people bought milkshakes. This was after the milkshake selling company had carried out traditional market research and marketing with no success. Clay and his team found people were actually buying milkshakes because they were easy to drink in the car and helped break up the boredom of the morning commute. I won’t delve to deep into this case study if you want to read more look here.

2. Categorize the Jobs to be Done

The “job” has a lot of “requirements” — not just functional but also emotional and social, which suggests that context and circumstances are important.

There are two different types of JTBDs:

  1. Main jobs to be done, which describe the task that customers want to achieve.
  2. Related jobs to be done, which customers want to accomplish in conjunction with the main jobs to be done.

Then, within each of these two types of JTBDs, there are:

  • Functional job aspects — the practical and objective customer requirements.
  • Emotional job aspects — the subjective customer requirements related to feelings and perception.

Finally, emotional job aspects are further broken down into:

  • Personal dimension — how the customer feels about the solution.
  • Social dimension — how the customer believes he or she is perceived by others while using the solution.

Example:

One JTBD is to organize and manage music for personal use. An important functional aspect of this job is to listen to the music. A related emotional/personal job is to organize and manage music in a way that feels good; a related emotional/social job is to share songs with friends. Related jobs might be to download songs from the Internet, make playlists, discard unwanted songs, and pass the time.

3. Define competitors

You need to define few cases: for what job your product is hired for, why it got fired, and why your customer switched to other solution

If someone’s Job is to quickly satisfy their hunger on-the-go, they may consider a pizza…but also a sandwich, a burrito, sushi, Snickers, or even nothing — preferring to wait for another opportunity to eat.

Knowing what products are in a customer’s consideration set for a Job, gives insight into what products a customer considers as competition for their Job to be done.

That means that your product could compete with a bunch of different services from a different group of products.

4. Create Job Statements

Action + object + context

Source: “Giving Customers a Fair Hearing”, Anthony Ulwick; Lance Bettencourt, MIT SLOAN Management Review, Vol. 49, No.

Key components of a job statement are an action verb, the object of the action, and clarification of the context in which the job is performed.

5. Prioritize the JTBD Opportunities

There are hundreds of jobs that customers are trying to get done in every market. Which one of these offers the best opportunities for you?

You might try to use Likert Scale & ask customers how important the job is, and how satisfied they are with an existing solution or service.

Likert Scale

A Likert Scale can also work for assessing the level of satisfaction customers have with current solutions.

Chart

Under-served JTBD
A core growth innovation strategy (make the existing solution better).

Over-served JTBD
A disruptive innovation strategy (remake the solution so it becomes available to those who can’t afford the existing solution).

Served right JBTD
When your assessment shows opportunities in the middle that are served right, you should focus on related jobs to be done.

You can tell when a company thinks in term s of JTBDs because the result not only fulfills a need, but is often quite innovative. Consider the recent developments in self-cleaning glass for cars and high-rise buildings, or in car paint that heals itself and, thereby, removes the need to paint over scratches. While you could think of painting scratches as a JTBD, it really isn’t. Painting scratches is actually a solution for accomplishing the JTBD called maintain a blemish-free vehicle.

What criteria would the customer use to decide which solution to hire or use?

Think in terms of time, cost, potential errors, quality, dependability, availability, ease of use, maintainability, and any number of other satisfaction and dissatisfaction dimensions.

Outcome expectations are solution-neutral and reside at a higher level; they are JTBD-specific desires.

There are four types of outcome expectations:

  1. Desired outcomes customers want to achieve.
  2. Undesired outcomes customers want to avoid.
  3. Desired outcomes providers want to achieve.
  4. Undesired outcomes providers want to avoid.

For example, the job of safely transporting passengers from point A to point B has many associated outcome expectations, such as minimize the jerking motion a passenger feels while being transported, have a possibility to do his job while his traveling, and etc.

7. Create Outcome Statements

Improvement + measure + object of control

It is important to ensure that jobs-to-be-done and desired-outcome statements use consistent, unambiguous language so as to be easily understood and readily translated into technical specifications.

During data-gathering interactions, you can confirm desired-outcome statements with the customers themselves. After selecting the most relevant desired outcomes you can then conduct a quantitative survey to determine how important each desired outcome is and how satisfied customers are with their current product or service.

8. Jobs evolve much more slowly than we think

Let’s Remember Maslow’s Hierarchy of Needs

People buy products and services to get jobs done; and while products come and go, the underlying job-to-be-done does not go away. This notion is at the heart of jobs-to-be-done theory.

If you remember anything about jobs to be done, remember this: they are completely neutral of the solutions you create (your products and services). While a customer JTBD remains fairly stable over time, your products and services should change at strategic intervals as you strive to provide everincreasing value.

As Christenson says, “at a fundamental level, the things that people want to accomplish in their lives don’t change quickly.”

For more information check my blog gecis.co