I started to feel like I couldn’t finish the work I needed to do because meetings were getting in the way. So I declined all my meetings for a week and went async.
When doing all-remote, async communication is key.
We have to think about typically synchronous things (like meetings) in a different way.
At GitLab, all most meetings are optional and have an agenda ready ahead-of-time that anyone can edit.
You can attend meetings asynchronously and work on your own schedule.
Turning the usual way of thinking about meetings on its head puts people back on a level playing field.
“The beauty of asynchronous is that team members can contribute to meetings that occur while they sleep.” — GitLab’s All-Remote handbook
Having an active agenda ahead of time allows people to contribute to the meeting asynchronously. This has been great for me as it allows me to contribute to meetings that occur outside my working hours. It allows me to hire and manage folks in APAC (Asia-Pacific) timezones, which I’m currently doing. It also allows me to focus on getting things done, without the usual meeting interruptions. That is exactly what I did last week. We call it an async week, and they’re fantastic.
I’d still “attend” meetings by adding my points to the agenda and watching the discussions on the recording. I just don’t have to be there at the exact time they were happening. Recording meetings felt weird at first, but you get used to it. Being able to watch them at 2x speed and skip the points that don’t apply to you are absolute game-changers.
A crucial step with async week is to let people know you’re doing it. You’ll likely have a few meetings where you’ll be missed if you don’t show up. It also prevents people from scheduling meetings with you for that week. Let people know, and over-communicate your intentions. I did this with a cross-posted slack message and brought it up in my usual meetings the week before.
Next, it’s the cathartic process of declining all your meetings. Clear, calendar, bliss. You can then plan your workload with ease and revel in all the free time you’ve given yourself.
I used this week to burn though my backlog, but it also gave me a new outlook on the meetings I do have. I couldn’t do an async week every week, but there’s a few meetings I don’t need to attend as often, or at all. These meetings can pile up. My next step; get brutal with my regularly scheduled calendar events. But that’s a topic for another day.
This wouldn’t work without our company-wide stance of async-first communication. Huge props to Darren, Jessica, and our remote team for helping foster a culture that allows us to take weeks like this. Check out our all-remote handbook for tips on how to do this.
Side note: I made a desktop wallpaper to remind me that, “all meetings are optional”. Check it out
Comments
(Powered by webmentions)love the lil’ “btw I’m hiring” mention 😆
Haha, just incase anyone missed it: boards.greenhouse.io/gitlab/jobs/56…
"I started to feel like I couldn't finish the work I needed to do because meetings were getting in the way. So I declined all my meetings for a week and went async." Did that a while ago, and it felt refreshing. #async #remotework
Cc @timothep
Saw this tweet thanks to @dnsmichi 👏 Greatly appreciate the link to our Async Week page (below) Kudos to @jessicareeder for putting this idea in motion 😎 about.gitlab.com/handbook/marke…
Remote + Async work = productivity and fulfilment 👑
I'll put this on my list of 'Personal Experiments' to try-out.
@spences10
Great article Sam! I should definitely try an async week soon.
It's like "make you daily optional" on steroids. Love it! aerokhin.com/posts/how-to-i…