Async Work: How to Thrive Without Meetings (2026)

Async Work: How to Thrive Without Meetings

By Sidra Salman · October 23, 2026

What if your team deleted every recurring meeting on your calendar tomorrow? Most of us feel two things at once: relief, because the calendar can finally breathe, and panic, because... how would anything get decided?

Async work — asynchronous work — is the answer to that tension. It means communicating and collaborating without everyone being present at the same time. You write it down, record it, or post it, and teammates read, watch, or respond on their own schedule.

And the data says we badly need it. Atlassian surveyed over 5,000 knowledge workers and found 68% believe at least half of their weekly meetings are unnecessary. The average professional attends about 17 meetings a week, yet only 11% of meetings get rated "highly productive." The price tag: roughly 31 hours a month — nearly four full workdays — lost to meetings people themselves call unproductive.

Meetings aren't evil. Some conversations genuinely need real-time back-and-forth. But when meetings are the default, they tax everything else. This guide is about flipping that default — the skills, a decision framework, and a daily routine you can copy.

What Async Work Actually Looks Like

Async doesn't mean "no communication." It means communication that respects everyone's time.

The synchronous way: a question pops up, someone schedules a call, five people join, three half-listen, the decision gets made verbally, and nobody writes it down. Two weeks later someone asks, "What did we decide?" and the whole thing repeats.

The async way: someone writes a short proposal — context, options, a recommendation, a feedback deadline. Stakeholders comment when they're free. The decision lands in writing, searchable forever. No meeting happened, and the outcome is often better, because writing forces clearer thinking.

Real companies run this way at scale. GitLab, an all-remote company with thousands of employees, operates "handbook-first": the default is to document a decision in writing the moment it's made, so a teammate eight time zones away can act without waiting for anyone to wake up. Doist (behind Todoist and Twist) runs on 24-hour response windows as part of its culture. Their guiding question is one I use all the time:

"How would I deliver this message or move this project forward right now if no one else on my team were awake?"

If you can answer that, you're thinking async.

The Meeting-or-Async Checklist

Not everything should be async. The real skill is knowing which things need a meeting. Run any proposed meeting through these four questions — if it fails all of them, it becomes a written update instead.

1. Does this need real-time back-and-forth?

Some things do: sensitive feedback, conflict resolution, rapid brainstorming where ideas build on each other faster than typing allows, and complex negotiations with real trade-offs. If a message could be read two ways and one of them causes damage, say it live.

2. Is there a written-record requirement?

If you need a record — a decision, an approval, a spec — go async first. A written proposal with a feedback deadline beats a verbal agreement every time, and it gives quieter teammates and non-native English speakers equal footing.

3. Could this be done in one message?

Status updates, FYIs, simple approvals, most reviews: async by default. Writing takes a few minutes; reading takes less. A 3-minute written update replaces a 30-minute call. That's math worth repeating.

4. Am I calling this meeting out of habit or anxiety?

Be honest. A lot of meetings exist because a manager wants the comfort of "alignment" or someone wants the safety of asking live instead of writing clearly. If the real reason is comfort, not necessity, skip it.

The rule of thumb: async is the default; sync is the exception that has to earn its slot.

The Communication Skills Async Work Demands

Async fails when people treat writing like casual chat. It succeeds with five specific skills:

Write self-contained messages

Every async message needs four things: context (what's going on), attachments (links, screenshots), the ask (the specific decision or action), and a deadline. "Thoughts?" on a document is a terrible async message. "I'm proposing option B for the pricing page — please flag risks by Thursday 5pm ET so we can finalize" is a great one.

Over-communicate context

Assume your reader has zero background. Spell out the "why" with the "what." In a live call, someone can ask what you meant. Async, ambiguity costs a full round trip across time zones.

Agree on response-time expectations

The habit teams skip, and the one that causes the most anxiety. Nothing should feel urgent unless it is. A workable standard: 4 hours for chat, 24 hours for email, 48 hours for documents. GitLab sets roughly 24 hours for non-urgent issues; Buffer runs a "no expectation" policy on evenings and weekends. Write it down, honor it — predictable response times are what let people mute notifications guilt-free.

Put durable things in documents, not chat

Chat scrolls away. A decision that lives only in a Slack thread is effectively lost within a week. Use chat for ephemeral coordination ("I'll be late to the overlap hour") and put decisions, specs, and processes in a document search can find. If you've explained the same thing twice in chat, it belongs in documentation.

Record when text would take paragraphs

A two-minute screen recording walking through a design or a bug report communicates more than a page of screenshots. Record the few meetings you do keep, with notes attached.

Tools That Make Async Work Click

Habits matter more than apps, but the wrong tools make good habits impossible:

• Async video (Loom, Zoom Clips): demos, bug reports, feedback with tone. Lowest learning curve of any async habit — record, link, done.
• Threaded chat (Slack with thread discipline, Twist): quick updates and discussions. Twist is built async-first; Slack works async if your team actually uses threads and respects Do Not Disturb.
• Documentation hub (Notion, Confluence): the single source of truth for decisions, processes, and specs.
• Task boards (Asana, Trello, Linear): visible ownership and progress — removes "where are we on this?" check-ins.
• Async standups: a daily written check-in — did, doing, blocked. Five minutes to write, two to read, and it kills the daily status call.

Pick a small stack, write down what each tool is for, and stick to it. A one-page "communication playbook" is worth more than any new app. And if managing your time at home is part of the challenge, protecting deep-work time is where async pays off fastest.

A Worked Example: An Async-First Daily Routine

Here's Maya, a remote project manager whose team spans the US, Portugal, and India. Total meetings for the day: one.

8:30am — async standup. Maya posts in the team channel: yesterday she finalized the launch checklist, today she's reviewing vendor quotes, blocked on legal's redlines. Teammates reply in-thread over the next few hours. No call needed.

9:00–11:30 — deep work. Notifications off. She's drafting a written proposal for the Q1 campaign budget — context, three options, her recommendation, a Friday feedback deadline. She posts it in Notion and drops the link in the channel.

11:30 — the one meeting. A 25-minute call with two colleagues to resolve a genuine disagreement about the campaign timeline — real-time trade-offs, exactly what meetings are for. Agenda and pre-read went out yesterday; the decision goes into the doc afterward.

1:00pm — async feedback. A designer recorded a 3-minute Loom of new homepage mockups. Maya watches it, leaves timestamped comments, and approves. The designer in Portugal reads them at her morning.

2:00–4:30 — execution. Quotes reviewed, proposal comments triaged, decisions logged. Anything she explained twice in chat, she adds to the team handbook.

4:30 — shutdown note. One line in the channel: done for the day, nothing urgent pending.

Notice what didn't happen: no status call, no "can you hop on a quick Zoom," no waiting on someone's calendar to move work forward.

Mistakes That Sink Async Teams

• Reactive chat culture: messages sent whenever, with an implicit "ASAP" expectation. That's not async — that's a meeting spread across your whole day. Fix it with written response-time norms.
• Meetings by habit: keeping the weekly status call "just in case." Harvard Business Review research found cutting meetings by 40% boosted employee productivity by up to 71% — the calls you're afraid to kill are usually the ones to kill.
• No documentation owner: docs nobody maintains are docs nobody trusts. Give each one an owner and a review rhythm.
• Skipping the social layer: async can get lonely. Build in lightweight connection — a watercooler channel, occasional video coffee chats, weekly wins. If remote work is feeling isolating, see our guide on how to stay motivated while working remotely.
• Expecting overnight change: shifting to async takes weeks of reinforcement. Start with one change — the meeting checklist, or async standups — and build from there.

Your First Async Week

You don't need the whole company on board to start. Try this five-step experiment:

1. Cancel one recurring meeting and replace it with a written update for two weeks.
2. Write your next "question" as a self-contained message with context, ask, and deadline.
3. Propose response-time norms — even an informal "I'm offline after 6" helps.
4. Document one decision that currently lives only in someone's head.
5. Block two meeting-free hours and defend them.

A solid workspace makes the structure easier — if yours needs work, our budget home office setup guide is a good starting point.

Frequently Asked Questions

What is async work, exactly?

Async (asynchronous) work means collaborating without everyone being present at the same time. Instead of calls and live meetings, it runs on written updates, recorded videos, shared documents, and task boards.

How do I start working asynchronously as a beginner?

Start with your own habits: write self-contained messages with context and deadlines, replace one recurring meeting with a written update, and agree on response-time expectations with your team. Email, shared docs, and chat threads are enough to begin.

Won't async work slow down decisions?

It can, if you skip feedback deadlines — the most common failure mode. But written proposals with a clear deadline often beat meetings, because nobody waits on a calendar slot. Reserve live meetings for genuinely time-sensitive or high-stakes calls.

How do async teams stay connected?

Deliberately. Successful async teams build a social layer: a casual channel, occasional video hangouts, async shout-outs for wins, sometimes one purposeful weekly meeting that's mostly about the people. Async protects focus time — schedule the connection on purpose instead of hoping meetings provide it.

About the Author

Sidra Salman is the founder of Remote Work Guide, where she writes practical, research-backed guides on remote work. Every guide is tested and written in plain English for a US audience.