Beta This is new guidance. Complete our quick 5-question survey to help us improve it.
Using data to improve your service: an introduction
Collecting data about your service allows you to measure its performance. You can use data to make sure:
- the service is meeting user needs
- the service allows users to easily complete the task it provides
- there are enough people using the service to make it cost-efficient
- people know about the service and are choosing to use it
Meeting the Digital Service Standard
You must continuously measure and report on how your service is performing to meet the following points:
- point 15 (collect performance data)
- point 16 (identify performance indicators)
- point 17 (report performance data)
You’ll have to demonstrate how your service meets these points to pass your service assessments.
What to measure
You must collect data that shows how your service is performing against these 4 metrics:
- cost per transaction - how much it costs the government each time someone completes the task your service provides
- user satisfaction - what percentage of users are satisfied with their experience of using your service
- completion rate - what percentage of transactions users successfully complete
- digital take-up - what percentage of users choose your digital service to complete their task over non-digital channels
These metrics are called the 4 key performance indicators (KPIs).
You’ll also need to choose other KPIs to measure. These will vary depending on your service. Use the work you’ve done to set performance metrics for your service as the basis for any decisions you make to measure service performance.
Metrics and measurements
Metrics are measurements that tell you how well something is performing. Typically they’re expressed as a percentage.
For example, if 2000 people tried to complete your service, that’s a ‘measurement’ of total attempts. If 1000 of them successfully completed your service, that’s a ‘measurement’ of completions. Combine the two and you get a ‘metric’ for how often people using the service manage to complete it. In this example the completion rate is 50%.
Measuring from the start
You must consider how you’ll measure your service from the start of your project.
In discovery and early alpha, you need to:
- have an analyst as part of your team (or available to your team) so that you can start asking the right questions about how you’re going to measure service performance
- start to set performance metrics for your service - outline your service’s objectives and explain what data your team should gather to meet them
- estimate the number of people you expect to use the service - be aware that large numbers may mean you need powerful analytics tools
- find out the analytics tools your organisation already has and whether they’re suitable for the type and volume of data you’re expecting
- find out where all your existing data is kept and how you’re going to access it, aggregate it and make it usable so that you can measure your service’s KPIs
- start thinking about the different ways users will interact with your service so you can plan how you’ll gather data
- start talking to the Performance Platform team so that you’re ready to start sharing data with them in beta
Share your data
How to use your data
It’s important to use the data you’ve collected to find ways to improve your service and prioritise them.
For example, your completion rate data can help you identify the stages in your user journeys when users are dropping out. Work with your user researcher and plan a round of user research to try to understand why.
You can also segment your user data based on the characteristics of groups of users. For example, you could check if users who are a certain age find the service harder to complete than other users.
If this is the case, you could then work with your user researcher to plan a round of user research with those users.
You may also find these guides useful:
- Published by:
- Performance analysis community
- Last update:
Guidance first published