Three Things That Happened

We did more things than this


Highlight of the week was the mini design sprint for autocomplete suggestions. I mostly followed Google’s Design Sprint kit to plan the session but used some of our own workshops rather than theirs. We only had 3 hours to think about this feature so couldn’t spend ages explaining new workshop techniques.

We’re thinking of introducing autocomplete suggestions because it helps users get to a more relevant query or the results they’re looking for faster, reducing the interaction cost. For example, someone may search for ‘tax’, need a very specific piece of guidance about vehicle tax and is forced to refine their search until they hit the right results. This costs the user time (and patience), and we can reduce the interaction cost by suggesting queries or content to users before their query is submitted.

The team did an excellent job of researching how autocomplete is implemented on other sites’ search. Particularly surprising was IKEA, which suggests completed queries, actual products, site categories and additional content when you search for something like ‘light’. They’ve clearly thought about the different jobs-to-be-done and how the navigational journeys for those interplay, whereas most places will just complete your query or take you to a particular section of the site, leaving you as a user to figure the rest out.

The team scoped out some great hypotheses, affinity-mapped the useful aspects to each implementation, wrote some good user stories and had a think about which assumptions we needed to validate with our own implementation of such a feature. They used Crazy-8s to think about the different ways it could be designed on GOV.UK.

Jeremy, our interaction designer, is taking it all away to design a few prototypes which will help us validate our assumptions. We think that autocomplete should be contextual to where you are, as currently the site search bar works the same everywhere (except for searching inside manuals). We also think that query suggestions are useful but oftentimes a service or piece of guidance would be a better suggestion


Peter and Jared came in to chat about data access models and a designerly approach to exploring data-sharing methods. I set up the event several weeks ago and did have some big names attending, but they unfortunately had to drop out. That was fine because the people who did turn up – delivery teams – certainly found it more engaging.

I was really pleased that people from the innovation technology programme came along and provided some of their insight to update the map. It doesn’t include current paper-based methods of data-sharing and so departments might not see themselves on the map, but it’s good to point that out.


Spent about three hours filling in a skills assessment form, marking my performance and things I’ve done against the skill levels for product managers. Me and my line manager thought that I was operating above the required levels for a product manager for some skills, effectively as a senior product manager, but it’d be good to know how that would be assessed by our Head of Product and the Head of Product Community!

It’s worth saying that filling in that assessment and my monthly professional objectives would have been much, much harder had I not been writing weeknotes the whole time.