We started Q2 2020–21 this week, so I was mostly doing kick-off things and writing OKRs.
Now that we’ve reformed our teams using Team Topologies, I’m product manager for Payments on GOV.UK Pay. I’m looking after the experience for paying users, considering payment types and payment channels we offer, PMing the microservices which run those, and other stuff that ensures you can pay government online. It’s bloody exciting work.
We released our open roadmap on Tuesday and it has already garnered some interest from service teams. That means it’s working, which is great! As mentioned in last week’s post, I had been looking into open collaborative roadmaps and the value they provide, so I’ve written up a blog post.
On Wednesday I spent time crafting our objective and key results for the quarter, based on some operational goals we’ve been set and the need to help GOV.UK Pay scale. You may have seen that the number of payments GOV.UK Pay takes each week has doubled in recent weeks, and since we’re scaling fast we’ll need to reduce bottlenecks and improve the experience for paying users. We’ve got two decent service level objectives as a guide but we’re at liberty to choose how we do it. It’s properly empowering to be working like this, it’s what I’ve always wanted!
Alongside the operational improvements and reducing errors, I’ll be doing some groundwork on UX for paying users, specifically on our Welsh language features and web performance (to reduce page weight and load times for people with low data allowances). There’s also accessibility improvements to keep ticking along.
And besides that, we’re also looking into Open Banking, more on Direct Debit, and how we might take recurring payments. That strategy work is mostly desk research and meeting with stakeholders, though there may be opportunity to build some prototypes.
I started using the Bets & Learning board to keep track of new features and opportunities, giving me a place to record learning over time. It’s provided a useful, actionable framework so far. Each feature or opportunity has a doc to record what we know, what we need to find out and next steps, so that we can keep a chronology of learning and evidence-building. I’ve already added snippets of emails to it, and I’ll invite people to comment on the doc next week. Asynchronous communication and creating alignment!
London is a bit shit maybe? It’s a shock being back, of course, but there’s f’ all physical distancing going on and everything just seems normal. Having said that, I keep checking this 7-day hotspots map that someone called Russ built, and case rates in Lewisham and surrounding boroughs are low. Think it’s just all the ambient noise that’s bothering me.
Anyway, on a positive note, I had a mix for the first time in ages and it gave me a right rush. SPINE-TINGLING! Splashed out on some back-in-the-day beats on Bandcamp, subby-dubby numbers, and it took me back to 2007 when I got my first pair of decks. Will be doing more of this over the next few months. Check out my collection on Bandcamp, if that’s your sort of thing.
The exercise regime is going well and having a noticeable impact on my waistline – phew! There’s lots of people about at lunchtime and in the evenings, so I’m running in the mornings and doing HIIT at home. Means it’s all out of the way at the start of the day, and if I fancy a walk in the evening, I can have one.
Surprise of the week: non-alcholic beer is low calorie, who knew.
- Launching the Digital, Data and Technology Functional Standard, 3 mins
- Creating alignment during product discovery, 3 mins
- Making product decisions requires us to take risks, 3 mins
- TBM 27/53: The Lure of New Features and Products, 4 mins
- Facebook Fails to Appease Organizers of Ad Boycott, 6 mins
- Reality bites: how the pandemic changed the way we eat, 16 mins