Look, I need to be honest about something. At my last job, I counted my meetings for one week. 47 meetings. That's almost 10 meetings per day if you count the weekend check-ins (yes, those were a thing).
I was constantly switching between Zoom calls, Slack notifications, and trying to remember what I was supposed to be working on. Sound familiar?
Now I work at a company that runs about 80% async. I finish most of my actual work by 2pm. I'm not bragging - I'm just getting the same amount done with way less stress.
Here's what I learned about making async work actually work.
Document Everything (But Make It Scannable)
The biggest myth about async work is that you need to write novels for every decision. Wrong.
I use a simple format for almost everything: Context, Decision, Next Steps. Takes me 3 minutes to write, saves everyone 30 minutes of meeting time.
Context: The checkout flow is broken on mobile
Decision: Using the fix from PR #342
Next Steps: Deploy Friday, Sarah monitors weekend traffic
That's it. No 45-minute meeting where we debate five different solutions and then forget what we decided.
I keep all of this in Notion ($8/month per seat) with templates for common decisions. My team knows exactly where to look, and new people can catch up on six months of decisions in about an hour.
The Tools That Actually Matter
I tested about 15 different async tools. Most are overcomplicated garbage. Here's what works:
- Loom ($8/month) for explaining anything complex. A 3-minute screen recording beats a dozen Slack messages.
- Calendly (free tier works) for the few meetings you actually need. No more "when are you free" tennis matches.
- Slack ($7.25/month per user) but with strict rules about response times.
The Slack thing is important. We have a rule: anything urgent gets a phone call. Everything else can wait 4 hours for a response.
Set Clear Response Windows (And Stick to Them)
This took me way too long to figure out. You need explicit agreements about when people will respond to what.
Here's our system:
- Urgent: Call or text (response in 30 minutes)
- Same day: Direct message (response by 6pm)
- This week: Channel message (response within 24 hours)
- FYI: Email (response when convenient)
The key is being honest about what's actually urgent. Spoiler alert: almost nothing is.
I also block out 2-hour focused work chunks on my calendar. During these times, I'm in airplane mode. No Slack, no email, no "quick questions."
Master the Art of Async Updates
Stand-up meetings are the worst. Nine people listening to one person talk about stuff that doesn't affect them.
We do async updates instead. Every Monday and Thursday, everyone posts:
- What I finished
- What I'm working on next
- Where I'm stuck (if anywhere)
Takes 2 minutes to write, 30 seconds to read everyone else's. I spend way more time actually helping teammates instead of just listening to status reports.
Finished: Mobile checkout fix, user testing setup
Next: Homepage redesign mockups
Stuck: Need approval on the color scheme options
If someone needs help, we jump on a quick call. But most of the time, everything just flows.
The Magic of Recorded Video Updates
For bigger updates, I record 3-5 minute Loom videos. Way more context than text, but people can watch at 1.5x speed when convenient.
I do this for:
- Weekly progress on big projects
- Explaining technical decisions
- Walking through design changes
Takes me less time than preparing for a meeting, and people actually retain more information.
Build in Real Human Connection
Here's where a lot of async teams mess up. You still need some face time with your colleagues.
We do one team meeting per week. No agenda about work stuff. We just talk about what we're up to, share something interesting we learned, maybe complain about our internet providers.
I also schedule 15-minute one-on-ones with each teammate every other week. No work agenda. Just "how are you doing, what's on your mind, what can I help with."
Sounds touchy-feely, but it prevents so many problems. When people feel connected, async communication gets way easier.
Handle Different Time Zones Like a Pro
Working with people across multiple time zones used to drive me crazy. Now I think it's actually an advantage.
The trick is designing handoffs instead of fighting them.
My designer is in Eastern time, I'm in Pacific, and our developer is in the UK. We plan work in 24-hour cycles:
- Designer posts mockups before East Coast EOD
- I review and add feedback during my morning
- Developer implements during UK morning (my evening)
- Rinse and repeat
Work literally happens around the clock. By the time I wake up, yesterday's problems are often already solved.
The Overlap Hours Strategy
We identify the 2-3 hours when most people are online and protect those for collaboration. Everything else happens async.
For us, that's 11am-1pm Pacific (2pm-4pm Eastern, 7pm-9pm UK). If you need real-time input, you schedule it then. Otherwise, you work async.
What Actually Needs a Meeting
Some stuff still needs real-time discussion. I've learned to be very selective about what qualifies.
Good reasons for meetings:
- Brainstorming new ideas (but time-box to 30 minutes)
- Resolving conflicts or misunderstandings
- Onboarding new team members
- Complex technical architecture discussions
Bad reasons for meetings:
- Status updates
- Information sharing
- Simple decisions with clear options
- Anything that could be a Loom video
When we do meet, we start with 5 minutes of async pre-work. Everyone writes down their thoughts before we start talking. Prevents the loudest person from dominating and makes discussions way more productive.
The Biggest Async Work Mistake
Here's what trips up most people: they try to replicate office culture remotely.
You do not need to be available 9-5. You do not need to respond to every message immediately. You do not need to prove you're working by being visible in Slack all day.
Async work is about output, not activity. Judge yourself and others by what gets done, not how many hours you spend looking busy.
I work roughly 10am-2pm and 7pm-9pm most days. Weird schedule, but it matches my energy levels and avoids most interruptions. My boss cares about whether I hit my deadlines, not whether I'm online during "business hours."
The hardest part is trusting that your teammates are also getting stuff done, even when you cannot see them. But once you make that mental shift, everything else falls into place.
Async work is not about eliminating all human interaction. It's about being intentional with everyone's time and attention. When you get it right, you end up with more time for both focused work and meaningful connections.
Give it a real try for a month. Set the boundaries, use the tools, document your decisions. I bet you will get more done than you have in years.