As well as carrying out user research with users, it's also valuable to carry it out with internal stakeholders. This is how the GOV.UK Verify team conducted user research with its internal stakeholders.
We've been looking at how GOV.UK verify might be extended to local authorities. To help with this, we've been offering training, tools and support to get each of the local authority teams we're working with talking to their own users
It’s good practice to measure the performance of your site, and monitor this over time – often called benchmarking. On GOV.UK, we’ve just completed our fourth wave of benchmarking.
To get my confession out of the way up front - I’m not a user researcher. I’m a content designer who’s had the benefit of working with world-class user researchers. I’ve learnt a lot from my time in user research …
Discovery research as a team sport In the service manual team, our mission is to provide ‘better guidance for teams creating government services’.
I love walls. I love them so much I once gave a talk about them, using a wall. And I know you love them too.
In agile, we find that user research works best when we do research in every sprint.
On a recent project in HMRC’s Digital Delivery Centre in Newcastle, we wanted to encourage everyone on the design team to get involved in planning the user research.
We’ve made our design patterns publicly available in the Service Design Manual, where anyone can take GOV.UK elements and combine them to meet common user needs when creating public services.
A lot of teams aren't used to having a user researcher embedded full time.