A really good week. I missed working on the Search team over the past few weeks, it’s such an interesting problem space. You get the almost continual gratification of seeing changes in metrics from tests too, validating or invalidating your hypotheses.
Tempted to try another style of writing weeknotes, these feel a bit dry now.
Five Things That Happened
We did more things than this
Much of the week was spent getting my head back into the Search team’s work and the whole problem space. By the end of the week, I was able to write this in the GOV.UK internal weeknote.
Search have brought back highlighted search terms to site search. They added it to finders and prototyped and built spelling suggestions ready for release soon. They also drafted a build-and-release plan for the improved mobile search UI, stopped last week’s A/B test and started another – they’re inches close to switching to ES6 entirely! The team continued refactoring Finder Frontend and rewrote some of its queries to perform 50x faster, as well as adding support for mixing quoted and unquoted query fragments, upgrading Golang apps and improving sitemaps so that Google crawls us more often.
So that’s what the team did. But what did I do?! Mostly I spent the week thinking about our objectives, milestones in the strategy, how we measure success/know when we’re done, and the different activities the team go through to reach those goals. It’s important to be thinking about this because, as a programme, GOV.UK is moving away from how quarterly planning has become established in GDS to something else.
The problem with quarterly planning is that it made everyone think in terms of quarters and it caused some people to be shifted around every three months. That’s process over people, the antithesis of agile development, and isn’t helpful. I’ve always told the Search team not to think in terms of quarters – the work is only ever done when value is delivered to users. So in our case, the work will probably never be done because site search can always be improved.
Lean methods feel more comfortable to me, and I also find thinking in terms of OKRs helpful, so I’ve always tried to frame the team’s work using vision, objectives, key results and milestones. Sprints have goals which play into these, but we don’t have a traditional roadmap of things to deliver, it’s all about outcomes.
Having checked on everything we’re doing and the way we’re doing it, I feel comfortable that the framework is laid down. There’s more work to be done on helping the team find its ideal Build, Measure, Learn process and tools, however.
Since we’d like to introduce site search suggestions to GOV.UK’s site search, I planned out a design sprint for the team. This starts with some fun (well, hopefully it’s fun) homework to collect up examples of search and autocomplete suggestions in other products. We’ll then pick apart
- what we’re looking for (search intent) when entering a query,
- what results are returned,
- how it looks,
- the onwards journey, and
- the problems this style of search suggestions solves
to see how the features work in different products. It’s entirely probable that the best ideas already exist so we should look at comparable problems, but also this background thinking will help the team think about what’s different in the user’s context when visiting GOV.UK to look through our content set.
The rest of the sprint will very much follow sections 3–6 of Google’s Design Sprint kit.
I started drafting a mini-discovery for searching inside manuals, e.g. the Highway Code and the content design manual, because the experience and results returned have changed since the migration to Finder Frontend. A couple of months back I emailed a heap of manuals publishers, asking if they had direct contact with their users so that we can perform some research. Having checked through user-submitted feedback for all manuals, there’s nothing to go on, so we’ll need to do some research.
We had a retro for last week’s remote sprint. I’ll share the team’s thinking once Nicole’s written a blog post on it. I’ve been eager to have an entirely remote sprint with a team for a while but unfortunately only caught two days of this one. Still learned some things though.
- Working remotely helps me focus and prevents me getting distracted by other people’s demands.
- Since I already block out two days for focussed work, working out of the office on those two days doesn’t disrupt meetings and face-to-face time.
- Team meetings can be hard when run remotely. Collecting opinion or asking the team for their thoughts is tough because it’s hard to stop people talking over each other.
I’ve taken on a mentee, which is the first time I’ve ever mentored anyone. They want help in reaching their performance objectives, someone to bounce thoughts off who isn’t their line manager, which is good as I’ll be offering ways of thinking rather than my own solutions when I’ve experienced those same problems.
- Using hypothesis driven design and user research to validate design decisions, 7 mins
- Idea Validation - Much More Than A/B Experiments, 13 mins
- Why you should stop using product roadmaps and try GIST Planning, 5 mins
- How Much Is Your Privacy Really Worth?, 14 mins
- Why should we care about data ethics?, 3 mins
- Data About Us, 3 mins
- Behavioural Innovation: embracing behavioural science for lasting impact, 3 mins
- Margaret Atwood’s Dystopia, and Ours, 8 mins
- The ‘Political Anarchist’ Behind Britain’s Chaos, 6 mins
- Being a user researcher for a day, 4 mins
- Not another directory of services!, 4 mins