At GDS we realise how important it is to build government services by understanding the needs of the people who use them. One of the most useful ways of doing this is by testing products with end users, and remote user testing is one method we use to do this at scale.
As detailed in other blog posts remote user testing is conducted by asking users to complete a number of tasks online, with their actions being recorded by a bespoke piece of software. This gives us task success rates, time to complete task, and common paths that people take through the site.
The latest round of remote testing involved 400 online participants completing five tasks on the latest release of Inside Government. The tasks that they were asked to complete were similar to those asked in the previous round, and included finding policy information, consultation information, department information, ministerial information, and contact information.
What did we find?
From this latest round of testing we found several improvements;
- task completion is a minute faster than the previous testing in April 2012
- average task completion is similar to previous round in April 2012 (64% vs. 60%), but…
Some tasks were achieved with greater success, namely
- policy information was found more easily (77% vs 64%)
- ministerial information was found more easily (54% vs 33%)
- agency or department contact details were found more easily (83% vs 69%)
- information on the homepage was easy to digest, and links to other content widely used
Users did, however, struggle to find consultations on the site. Users didn’t understand where to start looking, or under what navigation heading it would be listed. This issue was also picked up in the face-to-face lab testing, so it was quickly addressed by the product team and a solution is now undergoing further testing.
Remote usability testing has proved to be really useful at GDS. We can test products quickly, easily, and cheaply with a large number of potential users, and findings can be given to the product teams quickly.
Using this method of testing on Inside Government alongside agile working methods has really helped us understand how the product has improved – while also indicating where further work is needed to make it better for users.