When they plan user research, most user researchers start with an objective (eg test the usability of a new online transaction), and probably some more specific research questions.
We’ve been working on a project to build a user research panel for the GOV.UK user research team.
I expect you’ve already heard of High Speed Two (HS2). It will be the UK’s second high speed rail line, running North from London, initially to Birmingham. And the first main line railway to be built in the UK since …
Week-in and week-out user researchers communicate findings to teams and stakeholders. This is our stock-in-trade and we feel confident about it. But managing research over many months, or between teams rarely gets our focus.
Ben Carpenter and Ruben P. Huidobro work at GDS. Ruben is a user researcher, helping projects across government to do great user research and meet the Digital Service Standard. Ben looks at the guidance and requirements around assisted digital and digital take up. Ben and …
I’ve been working with GDS for several years now. I’ve researched, negotiated, procured and delivered several services for GDS, including a user research lab, an A/V library pilot and – currently in progress – a user research panel.
How can we include all kinds of users in our research, including those who may be harder to reach or reluctant to take part?
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.
Last year we ran a short workshop with the user researchers who assess government services against the digital by default service standard.
In The Old Man and the Sea, Ernest Hemingway tells this story. One day, Santiago goes out to sea, much further than other fisherman go. He engages in a herculean struggle to catch an enormous marlin. He thrashes all day …