Apr 5, 2022

Designing the temporary transport manager service

A case study on the design, build and launch of a new service for temporary transport managers.

An initial online workshop with stakeholders to capture ideas, concerns, risks, what information we should ask for in the new service, a potential user journey and how it could integrate into the VOL service.

Introduction

The UK-EU negotiations brought vehicles used by couriers and delivery services, including vans, under the scope of operator licensing.

This necessitated the creation of a new service to assist light goods vehicle (LGV) operators in applying to become temporary transport managers.

Transport managers are responsible for directing, coordinating, planning and overseeing tasks and operations within an organisation involving transportation activities. They are required to ensure the legal requirements for road haulage are met.

This case study outlines the design process for this service, covering the user research, discovery phase, service design, integration of existing components, development, and the launch of the service.

The task

As the primary service designer in the Vehicle Operator Licensing (VOL), I was in initial conversations with senior stakeholders at the Department for Transport (DFT) to help design a new service for LGV operators. LGV operators with good repute could use this service to apply to become temporary transport managers.

I was responsible for envisaging how the service could work and be as simple as possible for users, as well as leading on the design strategy of the service and it’s relationship with the current VOL service. I was also responsible for facilitating workshops and design reviews with key stakeholders from the Office of the Traffic Commissioner (OTC), Department for Transport (DFT) and the Driver and Vehicle Standards Agency (DVSA).

Discovery phase: unraveling the needs

During the discovery phase, extensive research was conducted to understand the needs of the new user group and gather insights from existing VOL license users. This research involved understanding the experiences of current VOL license users who were managing both light and heavy goods vehicles. Wth their feedback, we were able to make informed design decisions for the new service.

Stakeholder engagement was also crucial to identify the information required from users and establish the end-to-end journey, including application processing, appeals, and integration with the Vehicle Operator license application.

An initial online workshop with stakeholders to capture ideas, concerns, risks, what information we should ask for in the new service, a potential user journey and how it could integrate into the VOL service.
An initial online workshop with stakeholders to capture ideas, concerns, risks, what information we should ask for in the new service, a potential user journey and how it could integrate into the VOL service.

These sessions also enabled us to discuss:

  1. Information stakeholders wanted from users
  2. Needs of the users going through the application
  3. How these applications would be reviewed and by who
  4. What the options were for users with a refused application, such as hiring a transport manager or submitting an appeal against a refused application
  5. How to proceed with an approved application
  6. How an approved application could be used in the Vehicle Operator licence application process
  7. The end to end user journey, and what each organisation would be responsible for in this journey.

Once we were clear on the end to end journey, I created a user journey map that highlighted all possible outcomes and how the information would be shared between organisations.

A user journey map including the front and back end processing of the service, along with organisational handovers.
A user journey map including the front and back end processing of the service, along with organisational handovers.

Designing the service

Design priorities were established, with a focus on verifying credentials, ensuring road safety, and addressing potential gaps in user experience. A service blueprint was created, outlining the steps and interactions involved in the service.

My initial blueprint of the service, including the build up to using the service, the service itself and the application processing from the user and caseworkers point of view.
My initial blueprint of the service, including the build up to using the service, the service itself and the application processing from the user and caseworkers point of view.

The blueprint included:

  1. How users would find out about the service
  2. Initial steps the user could take before applying
  3. Creating an application
  4. The application verdict process from a users point of view
  5. How to review an application fom a caseworkers point of view
  6. The appeals process
  7. Using the application reference code in the VOL licence application

After multiple iterations, we had established our journey!

Creating an initial prototype

I took this blueprint away to create an initial design of the service using the GDS prototype kit. I worked closely with a content designer to create our journey, and established the key phases in our journey, these were:

  1. Find out if the user is using the right vehicle
  2. Find out if the user has the right experience
  3. Show the unhappy paths if steps 1 and 2 are not met
  4. If it is the correct vehicle and they have enough experience, ask for the users personal details
  5. Ask for users contact details
  6. Ask the user to record their work history for the last 10 years
  7. Ask the user to sign a declaration
  8. Show the user a confirmation page with a unique reference number and next steps

We created a design based on all the components and patterns in the GDS Design System to ensure we were creating a simple and easy to use service. It also gave us a good foundation for accessibility using well tested components.

An early screenshot from one of the initial user journey maps
An early screenshot from one of the initial user journey maps

Integrating a work history pattern from DFE

As we had limited research on this user group, I started gathering research on similar services from across the public sector. This led to conversations with designers at the Department for Education to learn how they designed the teacher training service. This service used the ‘record history’ design component, which helped users record their teacher training.

We used the ‘record history’ component from DFE in our new service when asking users to enter their work history. This ensured we were using a well-researched component in our service as it was used across many services at DFE.

Using the ‘record history’ component from DFE in our prototype to allow users to add their work history, and alert them with any gaps.
Using the ‘record history’ component from DFE in our prototype to allow users to add their work history, and alert them with any gaps.

Creating a design for the internal system

An internal system was designed to process the applications, taking into account the existing systems and processes used by VOL caseworkers. The goal was to provide a familiar environment to streamline processing and facilitate the addition of unique reference codes for successful temporary transport manager applications.

A later version of the internal portal user journey
A refined version of the internal portal user journey

Authorising the application in the VOL service

As part of the agile delivery team, I helped update VOL to accommodate the new light goods vehicle type and designed the process for successful temporary transport manager applications to add their unique reference code when applying for a license.

To streamline development, we adopted an MVP approach, adding functionality to the existing "adding a transport manager" journey. Users now have a choice when applying for a light goods vehicle license, between an approved application via the temporary transport manager service or the usual transport manager CPC qualification.

A prototyped journey of how users could add their approved temporary transport manager application reference code in the VOL service.
A prototyped journey of how users could add their approved temporary transport manager application reference code in the VOL service.

User Research and Testing

The prototype underwent several iterations based on feedback from potential users. Insights gained from user testing led to updates in content and guidance to improve clarity and provide additional support for users who faced challenges or did not meet the requirements.

A compiled log of the user research on the service, internal system, and VOL service updates.
A compiled log of the user research on the service, internal system, and VOL service updates.

Unhappy paths

Based on user feedback, I collaborated with the DVSA content design team to revamp the guidance on GOV.UK for transport managers. Our request to update the guidance with GDS led to a complete overhaul, allowing us to provide users with more helpful information by linking to it directly within the service.

An example of an ‘unhappy path’ on the service, where users would be given additional guidance on GOV.UK about transport managers.
An example of an ‘unhappy path’ on the service, where users would be given additional guidance on GOV.UK about transport managers.

Refining the prototype and mapping the full service

The prototype and the complete service journey were refined through continuous research and testing. A full service blueprint was created to illustrate the end-to-end process, including user flows, caseworker journeys, and the appeals process.

a picture of the full temporary transport manager service blueprint.
A picture of the full temporary transport manager service blueprint

Launching the service

Following a successful beta assessment, the service was launched. Ongoing monitoring and feedback will inform future improvements and enhancements to ensure the service continues to meet the needs of its users.