Skip main navigation

Journey maps

An introduction to journey maps and how they are used.

A journey map, also known as a user journey map, tracks each step a user takes as they go through a service.

Journey mapping helps teams understand how users interact with a service as they go through the process of completing their task. By visualising the whole user journey through the service, a journey map makes it easy to determine where the service works well as well as where users encounter difficulties and become frustrated or confused.

Users interact with services in many different ways and encounter different barriers.

Some users have time to research exactly what they need to do to complete their task and then interact with services in a careful and methodical way to ensure that they do not make mistakes. Other users need to interact with services when they have little time or something urgent comes up that they need to do immediately, which can cause them to rush or miss important information and create further stress.

Some users do not speak English well; some are less confident using digital services or struggle to use the internet; and some people have disabilities or impairments that create barriers for them when using online services.

All users can miss important information or steps in a process if a service is not well-designed and therefore not easy for them to use. Some users may not even be able to start the process due to certain barriers. These barriers could be low digital literacy, a lack of access to the internet, a disability or impairment, or sometimes simply not knowing that a certain service actually exists!

We will learn more about barriers in Week 3.

Journey maps help teams identify these problems. Identifying points in the process that cause confusion or create barriers for the user make it possible to solve these problems and make the service more accessible and easier to use for everyone.

Building a journey map

A journey map breaks down the whole user journey through your service into distinct steps.

It is important to remember that the user journey begins before they interact with the service and ends after they have finished using it. This means that your journey map should include what happens before someone starts using the service and what they do after their task is completed, not just the steps they take while using the service.

For example, users may receive a letter notifying them of something they need to do. After receiving the letter, the user would then begin their interaction with an online service, but the letter is still a vital part of their user journey that should be included in the journey map.

In a comprehensive journey map, each step in the user journey should also include information about:

  • what the user is trying to do
  • what they are thinking or feeling
  • where they face issues
  • what is working well
  • what could be improved

Different user groups have different needs and skills and will interact with services in different ways. They will encounter different problems at different times in the process. Focusing on only one user group might cause you to miss problems experienced by others.

At the same time, you should avoid trying to add too much detail – too much information makes the journey map hard to read and use. For example, not every single action that a user does will count as a separate step in the journey.

As you gain experience working in design teams and working with journey maps, you will learn how to use them effectively.

This article is from the free online

User Research in Government: Developing Further

Created by
FutureLearn - Learning For Life