Skip main navigation

Jobs to be done

Learn about jobs to be done, a new concept for understanding how users choose different products and services.

Jobs-to-be-done, or JTBD, is a theory developed by American academic and business consultant Clayton Christensen in 2006. It helps understand why users choose one product or service over another.

Simply put, it is about identifying what ‘job’ the product or service is being ‘hired’ to do. In this step, we will learn about how this works in the private sector and then explore how it can help us to understand government services.

JTBD in the private sector

Christensen put his theory into practice when hired by McDonald’s, the fast food restaurant, to help them sell more milkshakes.

In an attempt to increase sales of their milkshakes, McDonald’s had conducted market research with their customers so that they could determine what customers might want from their products. They implemented various changes from this research – improved and more varied flavours, different sizes, different mixtures and recipes – but found that sales did not increase.

Christensen conducted a different sort of research.

He observed customers throughout the day and realised that they mainly bought milkshakes in the morning on their commute to work. He then asked them what ‘job’ the milkshake was being ‘hired’ to do – or, in other words, what need it was fulfilling during the morning commute.

He discovered customers simply wanted something to keep them full and alert during their morning commute. Milkshakes are sugary, which provides an energy boost, and customers could drink them with one hand while driving. Most surprisingly, they did not really care about different ingredients or flavours – the most important thing was convenience. This meant that McDonald’s was not competing against different fast food chains in terms of the quality of their products, but against different things that people might have for breakfast.

Rather than trying to improve the product itself, McDonald’s listened to Christensen, and changed the layout of their restaurant and the process of purchasing milkshakes to make it easier, faster, and more convenient for customers. As a result, sales increased.

This is the principle behind JTBD – understanding the fundamental reason behind user decisions. If customers wanted gourmet milkshakes made from hand-crafted gelato, they would make the effort to go to a different restaurant to purchase that product and experience. On their morning commute, they simply wanted something quick and easy to keep them going.

JTBD in government services

JTBD works well for businesses when sales and profit are the goal, but what does this mean for government services?

In government, we are not trying to turn a profit or hit a quota for sales. What matters to us is that whenever someone needs to do something, there is a service there that enables them to do so.

This is how we can use JTBD in government. The job that users need to get done when they interact with a government service should be as easy and efficient as possible. This means services should be simple, intuitive (easy to understand and use), and work for everyone.

All the optional extras that you might get at a gelateria that serves gourmet ice-cream sundaes are not what customers are looking for when they just need a sugar fix in the morning. In the same way, users of government services do not need anything other than a service that works in the way they need it to when they need it to.

Let’s think about vehicle tax again.

‘Tax your vehicle’ is a service that meets the need of having to pay vehicle tax. It is simple and gets the job done – there are no add-ons or optional extras. This is because the user need of paying vehicle tax was clearly identified, and the service was built to meet that need and no more.

However, what if the teams had tried to add on a whole bunch of extra features? What if while paying your vehicle tax, you were also offered insurance deals or MOT services? As a user, you would probably feel totally overwhelmed and frustrated by the fact that the service appeared to be trying to do everything except the job you need it to get done, which is pay your vehicle tax.

When services try to do too much, they risk failing at the one job users actually need them to do.

This is how JTBD can be used to understand user needs in government services. It is about finding the fundamental user need behind someone needing to complete a task, and building a service that meets that need and no more.

This article is from the free online

User Research in Government: Developing Further

Created by
FutureLearn - Learning For Life