I’m not going to write up everything I did this week, because it was filled with lots of little things and I was hoping it would be a week of deep things. But I did reflect on why I moved from GOV.UK and I’m feeling happy about it. And anyway, we changed our ways of working this week.
This week we tried out asynchronous communication to see whether it might become a feature of the new normal. Rather than everyone needing to be in the office at the same time, using meetings and emails as the main thoroughfare of information exchange, asynchronous communication uses the internet to facilitate distributed working.
In theory, it’s good for working parents who don’t have their regular access to childcare, and for people looking after vulnerable friends, partners and relatives. It’s also supposed to be ideal for anyone with an introverted sensibility that finds it hard to collaborate in face-to-face meetings. As a communication practice, it’s supposed to prevent managers and leaders from forcing their colleagues to pitch in on half-formed ideas, encouraging more background work and concise communication.
That’s the theory anyway. We tried it out for a week to see how it worked for us on GOV.UK Pay. Here’s my notes on what went well and what didn’t go well for me.
What went well
There was more time in the mornings to process emails and plan my goals for the week.
I felt more conscious of how instant messages might distract or overload people, so I spent a little longer writing out a message to make sure it was understandable and actionable.
When I hit a slump in concentration after a big tranche of meetings, I stopped working and went for a run. I carried on working after dinner with renewed energy. This is diffuse mode thinking.
What could have been better
On Monday I had 2 hours of meetings with people outside the team, which meant I didn’t get a chance to get my head down as much as I’d have liked. I doubt that’s avoidable.
Though we’re still using Slack for conversation, I did find it caused unhelpful context-switching and created a distraction when someone @-ed me. I had my head deep in a set of discovery questions for a new payment behaviour and felt compelled to switch into thinking about technical operational management.
I still had to send emails with my colleagues cc’ed, but these were email threads to people outside our team. Not ideal, but to be expected when you’re running a service.
Asynchronous sprint planning felt a little clunky. We had planned some activities to be completed by a certain time, but we cut it quite close to the wire. It’s probably because we’ve never done it before but also perhaps because we’re still gelling as a team.
Communication is always hard but it’s much easier to misread a message when you only have text to go by. We probably should have co-created some communication principles, such as assuming good intent or taking time to explain yourself.
By Wednesday, I felt like I was living out of my inbox more than usual.
What I’ll start doing
We work flexible hours, so I’ll start being more strict with caring for my concentration levels. For example, if I have a two-hour stretch of meetings, I’ll go do something else for a bit before returning to work some more.
Having my attention diverted by notifications on Slack is unhelpful, so I’ll start setting do-not-disturb periods when I’m trying to get my head down.
Pomodoro helps me break out of inbox- and Slack-surfing, so I’ll use that more next week.
I had a dead good birthday. Not as raucous as most years, relatively tame in comparison, but still indulged – as one should.
Birthday lunch at Forza Wine was decent, and I’d really missed Italian food and wine. The staff were PPE’d up sufficiently and the tables were distanced, which surprisingly didn’t affect the atmosphere too much. Having said that, I’m not sure it’s OK to put waiting staff through the possibility of contracting coronavirus, so that’s probably the last time I’ll eat out this year.
We walked the third section of the London Loop last week, which was just as nice as the second section. I hadn’t realised that Bromley (the borough) was so green and rural. Gorgeous. We also got to see the Wilberforce Oak which I’m sure many of you would like to visit too. This weekend we’re walking sections four and five, I’m HYPED.
After finishing Steal as much as you can by Nathalie Olah, I’ve started reading SPQR by Mary Beard. If you imagine she’s speaking it to you, it’s easier to read. Neat trick, that.
Started running again and my knee is holding out. So that plus continuing the prison workouts means weight loss is going well.
- Distributed Work’s Five Levels of Autonomy, 5 mins
- How do I know my team is productive when working from home?, 6 mins
- Keeping your team healthy and more productive using remote work, 6 mins
- TBM 30/53: Healthy Forcing Functions (and Paying Attention), 3 mins
- Remote is not a substitute, 3 mins
- Vittles 6.23 - The Lunch Break, 9 mins
- The top struggles of remote workers (part 1) — Collaboration & communication, 3 mins
- The top struggles of remote workers (part 2) — Loneliness, 3 mins
- The top struggles of remote workers (part 3) — Not being able to unplug, 3 mins
- The top struggles of remote workers (part 4) — Distractions at home, 3 mins
- Working-class people don’t need to “break into the elite”—we need to change it, 5 mins
- How ‘Sustainable’ Web Design Can Help Fight Climate Change, 4 mins
- Lawmakers, United in Their Ire, Lash Out at Big Tech’s Leaders, 6 mins
- Wolverhampton Wanderers: The one-year-old season that is far from over, 5 mins
I think it's time for people working on computers to look sideways (metaphorically) and help each other out in designing their future of work.
Open and honest conversations, building trust, purposeful retros and designing strategy. Belter of a week, to be fair.
It’s Q3 2020/21 and much of my week was spent kicking off our latest piece of work.