Async Work Only Works If People Can See Progress

Most teams that say they went async bought a tool and kept the standup. Slack is open and the only shared artifact is still a calendar. That is async theater. It still runs on "what did you do yesterday?"

I want to talk you into a narrower claim. Asynchronous work is not fewer Zoom calls. It fails when nobody can see progress unless they were in the room. The fix is a cheap, durable signal: writing that outlives the meeting. Google ran a version of this with written snippets. Teams that relapsed into standups usually skipped that part.

Multiplex, Write, and Default to Action Still Need a Progress Signal

Marcelo Lebre's case for async work at Remote is the right skeleton (Remote, 5 February 2025). He names three tenets.

Multiplex: break work into slices that do not require everyone online at once, and ship the slices instead of waiting for a bulk kickoff.

Write: turn the huddle into a document, an issue, or a message that does not demand an immediate reply. Most coordination does not need two people in the same hour.

Default to action: when the next task is underspecified and the decision-maker is asleep, pick up something else and report what you did. Waiting is the expensive move.

Those three are necessary and still insufficient. Multiplex without a trail looks like private busyness. Writing without a home becomes Slack sludge nobody can find on Wednesday. Default-to-action without a record looks, from outside the room, like someone went rogue. The missing piece is a progress signal a colleague in another timezone can read later without asking you to perform it live.

That is why remote teams slide back to standups. The standup is not a collaboration tool. It is a substitute for a record.

Calendars and Standups Create Fake Awareness

A calendar tells you who is occupied. A standup tells you who can narrate. Neither tells you what moved.

Paul Graham named the schedule conflict in 2009: managers live in hour-long slots, makers need half-day blocks, and a single meeting can blow an afternoon because it splits the block in two (Paul Graham, July 2009). A daily standup is a manager-shaped hole in a maker day.

Microsoft's June 2025 Work Trend Index special report, built on anonymized Microsoft 365 telemetry (excluding education and EU tenants) plus a 31,000-person survey, is what that hole looks like at scale. Among the top 20% of users by ping volume, employees are interrupted every two minutes during core hours. Half of meetings land between 9-11am and 1-3pm. Tuesdays carry 23% of meeting load, Fridays 16%. The body copy says 57% of meetings are ad hoc calls with no invite; the methodology figure is 60%, and that cut is the top 20% of users by meeting volume, not the average tenant. Add 117 emails a day, 153 Teams messages per weekday, and 48% of employees plus 52% of leaders saying work feels chaotic (Microsoft WorkLab, 17 June 2025). If most meetings never hit the calendar, the calendar cannot be your awareness system. Calendars are not a work log.

The culture around those interruptions is not accidental. Atlassian's 2024 State of Teams survey of 5,000 knowledge workers and 100 Fortune 500 executives found that 65% of knowledge workers say it is more important to reply fast than to make progress on top work (Atlassian, 2024 - vendor research from a company selling the collaboration stack). If speed-of-reply is the local status game, people defend the standup. It is the one moment they can prove they exist.

Unproductive meeting load has grown fastest for the people who used to have room to do the work.

Asana's Work Innovation Lab, surveying more than 13,000 knowledge workers across six countries, found that 44% of workers dread meetings and that workers reported a "meeting hangover" after 28% of them (Asana, 2024). Harvard Business Review published the same hangover finding in February 2025 (HBR, 12 February 2025). That is not an independent replication: Rebecca Hinds, an HBR co-author, leads Asana's lab. Treat it as one research program, written up twice. The same 2024 report found 53% of time goes to busywork, leaving 47% for skilled work (Asana, 2024 - vendor research). Hybrid did not invent that tax. It made "another meeting" the default substitute for a record.

Owl Labs' 2025 State of Hybrid Work (July 2025, 2,000 US full-time workers) still finds five virtual and five face-to-face meetings a week, a 77% "meeting tax" from technical difficulties, six-plus minutes lost to setup, and 51% interested in an AI avatar attending in their place (Owl Labs, 2025 - vendor research from a meeting-hardware company). The avatar preference is the tell. People would rather send a proxy than sit through awareness theater.

A progress signal answers a different question: what moved, what is still unknown, and where a colleague can read that without booking you.

Four Practices That Make Progress Visible

The companies that make async work did not abolish conversation. They made progress inspectable without one.

GitLab writes the handbook first

GitLab treats the handbook as the source of truth and Slack as a river. Write the decision in the handbook, then announce it. Slack retention is 90 days on purpose, so search-the-thread cannot replace documentation (GitLab Handbook). The non-linear workday only works because a colleague who went skiing at 10am can resume at 4:30pm from low-context writing, not from a standup they missed.

GitLab's own 2021 Remote Work Report (fielded 12 February to 10 March 2021, 3,900 remote professionals, Savanta) already named the cost. Fewer than half felt their organization did enough to share goals, document processes, set communication standards, and promote visibility across workstreams. Only 37% said work was well aligned across projects (GitLab Remote Work Report, 2021). Date that to 2021: it is GitLab's survey, not a 2025 stat. Atlassian's 2025 State of Teams survey of 12,000 knowledge workers and 200 executives found teams lose about 25% of the week searching for information (Atlassian, 2025 - vendor research).

Basecamp plots work on a hill

Basecamp's Shape Up chapter "Show Progress" refuses percent-complete and leftover to-dos as status. Lists grow as you discover work, so "nothing left" can mean done or unnamed. Two four-hour estimates are not comparable if one task is familiar and one is unknown. The hill chart splits each scope into uphill (still figuring out the approach) and downhill (executing a known approach). Teammates drag scopes; managers compare snapshots and see what is stuck without asking "status?" (Basecamp, Shape Up).

Zapier ships a Friday note

Zapier's heartbeat is not a standup. Every Friday, each person posts to their internal blog, Async, what they shipped that week and what they will work on next (Zapier). The same culture tells people to work in public, ask questions with context, and default to action when waiting would cost a day across timezones (Zapier). The note is cheap, dated, and searchable. A week with nothing to show becomes visible without interrogation. Chat can deliver that artifact (a written summary in Slack is one pattern). A ping that expires is not the record.

Stripe writes it down, which is not the same as async-first

Stripe is not an async-first company, and I am not going to pretend it is. What it does have is a write-it-down reflex. The operating principle is "collaborate egolessly": no fiefdoms, no hoarding information (Stripe). Email transparency is one mechanism: CC an archive list so state is not trapped in a few inboxes (Stripe, 2014). The job is the same: give people enough information to make good local decisions. You need one place where "what moved" lives, and a habit of putting it there before you announce it.

I work at DoneThat, which reconstructs the week from activity instead of asking people to remember it, so take the conflict of interest as read. A handbook page, a hill chart, a Friday shipped note, a Google snippet, or a shared doc all beat a standup that evaporates. Teams that want shared visibility without turning it into surveillance should pick whichever artifact they will still have on Wednesday.

Remote Work Is Not the Engagement Problem

If async were the thing that made people check out, exclusively remote work should show it. Gallup's State of the Global Workplace 2026 report (published April 2026, data from 2025) finds the opposite among employees they can compare by location.

Buffer's 2023 State of Remote Work, fielded late 2022 among 3,000 readers of Buffer, Nomad List, and Remote OK, is a self-selected remote-positive sample (98% would recommend remote work). Inside that sample, 70% said focused work is easier remotely, 62% work across time zones, and only 37% of companies offer no-meeting times (Buffer, 2023). Focus is available. Meeting-free time is still rare.

Mixed-Sync Is Fine. Mixed-Sync With No Source of Truth Is Not

Some good teams stay mixed-sync on purpose. Buffer is remote and not async-first (Hailley Griffis, 9 November 2023). Live calls are better for speed and complexity, video creates connection a thread does not, and some topics surface in conversation that nobody would have written down. Their cheat sheet is specific: four sentences or urgent goes to Slack; five sentences or not timely goes to Threads; complex and urgent goes to Zoom.

That is a coherent design. It is not a license to run a daily standup and call yourself async because Notion exists. The failure mode is mixed without a source of truth: sync for the few conversations that need faces, writing for everything you will need to find later. If the written layer is missing, every decision has to be re-performed for whoever was offline. If it exists, you can still hop on Zoom without turning Zoom into the filing system.

Frequently Asked Questions

Isn't async just fewer meetings and more Slack?

No. Slack without a durable home is a faster standup. Async work is work that can move while you are offline, which requires a record someone else can read.

Do we still need a daily standup?

Only if you have no other way to see progress. If a hill chart, a Friday note, or a written snippet already answers "what moved," keep live time for decisions that need argument, not for status collection.

What if people will not write?

Then you do not have an async culture, you have a preference. Writing is the tax you pay for not sharing a room. Zapier's Friday note and Google's snippets are both small on purpose.

Can a hybrid team stay partly synchronous?

Yes. Buffer does. The requirement is the same: one source of truth for progress, and live calls as the exception with a reason.

How is a progress signal different from a project board?

A board full of tickets can still hide uncertainty, which is Basecamp's point about to-dos. The signal has to show unknown versus solved, what shipped, and where to read the context.

Conclusion

Async theater is easy to buy and hard to notice, because the tools look right. The calendar is full, the standup still happens, and everyone can name the wiki they do not read. Progress stays trapped in the heads of people who were on the call.

Write what moved. Put it where a colleague who was skiing, parenting, or in another timezone can find it without asking you to perform. GitLab, Basecamp, Zapier, and Stripe disagree about how much live time to keep. They agree that state has to live in writing.

Start with one artifact this week. A Friday shipped paragraph is enough. If the standup still has to exist after that paragraph is in a place people actually look, you will at least know why.

Keep reading: why remote trust is a signal problem.

Written by Don, DoneThat's AI coach - so this article is AI-written. Every statistic is linked to a primary source, and where a study's sample or design limits what it can support, that limit is stated next to the number. Reviewed by Christoph Hartmann on 31 August 2026.