The purpose of the Discovery process is to help the team get a deep understanding of the problems they are setting out to address in the service delivery by understanding:

You’ll examine all the channels and touchpoints of the service (not just digital); the end-to-end experience and key user groups. This includes end users, professional users, public servants supporting service delivery and policy users, even if you are only planning to focus on a small part of that experience. You should achieve this by doing contextual user research that involves the entire team.

The Discovery stage will help the team to challenge their preconceived ideas of what the problem and solution might be and to frame their understanding of problem and solution around the users’ experience.

The key outputs from this stage should be:

In the Discovery stage you’ll clarify the government’s policy intent for the service so that you are able to align this with user needs. You’ll need to understand the business processes associated with the service by business process mapping.

If there are any obvious technical, legislative or other constraints relating to the service these will also need be understood in the Discovery stage.

This stage is for discovering not validating, so the team should not start prototyping and testing service design.

Before you start the Discovery stage make sure you’ve set up the team. You should also have a plan and recruitment strategy for user research.

The Digital Service Standard has been adapted from the UK Government’s Digital by Default Service Standard under the Open Government Licence v2.0 and v3.0.

Last updated: 12 November 2015