The Fallow Period
A short week at work, being only Christmas Eve and one day of The Gooch – the bit between Christmas and New Year that’s a bit empty but definitely has purpose. Spent most of it either wrapping up the quarter or walking in the West Midlands and Wales (1, 2).
Two Things That Happened
We did more things than this (though it was only a 2-day week)
As there will be a new associate product manager replacing me on Platform Health, I spent a few hours packaging up a project I’d made a start on but can’t continue. Translations on GOV.UK give departments the ability to share information in languages other than English, which due to the platform’s organic growth isn’t a function that’s handled consistently by the various publishing applications. Since we have a few issues with translations to be solved, it’s worthwhile looking at how we can make it better everywhere rather than fixing bit-part problems.
It’ll be a good first project for them to sink their teeth into, a meaty technical problem – allowing them to explore the stack and the idiosyncracies of applications – which can be fixed by focusing on delivering value to users. Starting with user needs will mean they can check on whether we’ve delivered enough for users already, as this hasn’t been looked at holistically before.
I wrote up what we’d managed to achieve this quarter and it’s quite a bit. There had been a few headline metrics such as making content appear 10x sooner for users, reducing the publishing queues by 45 per cent and improving publishing latency by 25 per cent. But after digging into our metrics a little more, the improvements haven’t been wholly consistent and there’s still a few fluctuations to take account of.
This doesn’t mean that the team hasn’t been successful. Though we set ourselves the task of improving the publishing pipeline, we don’t own it and the actions of other teams have influence on it. We’ve been successful in finding root causes and addressing those through code, but it’s time to take a look at some principles.
I regret not having been able to set service level objectives (SLOs) for the user experience on GOV.UK. It was my main aim at the beginning of the quarter but holiday and urgent EU Exit projects got in the way. It started off with a prioritisation of Jobs-to-be-Done on GOV.UK and setting SLOs for scheduling publications, but the body of work needs to be completed.
What I Learned
You can’t get precious about the effect of your code on shared infrastructure. It’s better to be precious about the principles you set for everyone who shares it. One to run past Alex when we next have coffee.
What I Could Do Better
It was a 2-day week, it’s hard to improve on answering emails and writing up organisation knowledge.
- How Much of the Internet Is Fake? Turns Out, a Lot of It, Actually
- Why the PDF Is Secretly the World’s Most Important File Format (Spoiler: it’s not, it’s just pushed heavily.)
- The Many Meanings of Open
- How can we break the Brexit deadlock? Ask ancient Athens
- This Health Startup Won Big Government Deals—But Inside, Doctors Flagged Problems
- Fathom Analytics on Heroku
If you’d like to receive articles like this in your inbox every week, sign up to my mailing list.