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.
User research may be a team sport, but it’s not uncommon to be the only user researcher in your team.
We have a well-loved mantra: research is a team sport. It’s not just about embedding a user researcher in the team to report back on what the user said, it’s about the team participating and collaborating with the researcher.