You can find more information about user research on the dedicated User research in government blog.
We’ve already written about how we’ve worked to identify user needs for GOV.UK, so now I’d like to explain a bit more about what happens next - how does a need become published content or a tool on the site?
We’re doing a lot of user testing over the summer, and Sarah Prag has a quick update on a couple of things we’ve already changed based on what we’ve learnt so far.
We said we’d be iterative, so here’s a list of all the changes we’ve made since the release last night. Most of these things went live at 3pm today - largely based on your feedback - so keep it coming!
As a Product Analyst in the GDS Delivery team acquiring data is critical for telling us if our products are meeting user needs and how improvements must be made to content and services. Our team analyses not only search data …
My name is Joshua Marshall, and I'm a front-end developer and the Accessibility Lead for the team working on the beta of GOV.UK. Most of my focus has been on making sure that both the public facing website and the …
As mentioned in other blogs, one of the first and primary tasks for the Alphagov project was to build a site that provided the information and services users need. So where were we going for the evidence? Within the timescale …
Read GDS’s recent blog post for an update on our one login for government programme, including live beta, onboarding and feature development.
If you’re interested in joining us, check out all open opportunities on the GDS careers site.