Async Communication: The Practices That Survive Contact With a Deadline

Every team that adopts async communication discovers the same thing in their first deadline week: some of it holds and some of it evaporates. The useful response is not to recommit to the practices that evaporated. It is to notice that a practice which cannot survive pressure was never a practice, it was a preference, and to build the team on the ones that held.

"We say we're async and then book a call."

The crunch week is the only honest test

In a calm week, async looks like it works everywhere. People write thoughtful updates, meetings get declined, and documents get read. None of that is evidence, because in a calm week nothing is contested and nothing is late.

Then a deadline arrives. Within two days the team is on a call, the written updates have stopped, and someone is messaging three people directly because they need an answer now. That week is the real measurement. What people do when they are under pressure is what the system actually is; what they do otherwise is what they would like it to be.

What survives

• Decisions written down, with an owner and a date. Survives because it saves time immediately. Under pressure, a team relitigating a settled question feels the cost instantly, so the record earns its keep in the same week it is written.
• Work specified well enough to continue unattended. Survives because the alternative is a blocked person, and blocked people are visible during crunch in a way they are not otherwise.
• A place to look before asking a person. Survives only if looking is faster than asking. If it is slower by even thirty seconds, it disappears in week one.

The pattern is consistent. Practices that pay back inside the same day survive a deadline. Practices whose payoff is next month do not, regardless of how sincerely the team agreed to them.

What does not, and why that is fine

Long-form written culture goes first. Writing a considered document takes forty minutes and a call takes ten, and under pressure people choose the ten. Hard no-meetings rules go second, usually with visible relief. And any practice with delayed payoff goes third: the retro template, the weekly written update, the documentation rota.

This is not a discipline failure and treating it as one produces a team that feels guilty and does the same thing next quarter. It is a signal that those practices were paid for in the moment and rewarded later, which is an exchange no one makes when the deadline is Friday.

Some of it is also correct behaviour. When a deadline is contested and tempers are short, a call is genuinely the right instrument. The mistake is not the call; it is concluding from the call that async does not work here. Both belong, and a two-question test helps sort which is which.

The single point of failure

Strip away the practices and one failure mode explains almost all of it. Async breaks when a question sits unanswered. Everything else is downstream: the call gets booked because someone needs an answer, the direct messages start because the channel was too slow, the written update stops because the conversation moved to a call.

This is where StandIn fits. Each person spends ninety seconds at the end of their day confirming a brief, mostly drafted from the work they already did. While they are off, their StandIn answers questions from it in their words, with a source under every answer, and never guesses: when the answer is not there, it says so and names who to ask. The unanswered question, which is the thing that breaks async under pressure, stops being unanswered. See how StandIn works.

Rebuilding around what held

After a crunch week, run a fifteen-minute review with one question: which of our async practices did we abandon, and what did we do instead? Do not moralise about it. Write two columns.

Abandoned	What to do about it
Weekly written update	Shorten it until it survives, or drop it
No-meeting Wednesdays	Keep, but fix what people needed the meeting for
Decision log	Usually survived; make it the spine
Long written proposals	Reserve for genuinely irreversible decisions

Then keep three practices and delete the rest. A small async system that holds under pressure beats a comprehensive one that is suspended whenever it matters.

Common Questions

Is async communication realistic for a team with tight deadlines?

Yes, for the parts that are information transfer, which is most of the volume. Under a tight deadline the right shape is a short daily live slot for decisions plus everything else in writing. Teams that fail usually attempted the reverse: all-written decisions and no live time at all.

Why do async practices keep dying at our company?

Almost always because the practice costs effort now and pays off later, so the first busy week removes it. Look for the version that pays back the same day. A ninety-second brief that stops three interruptions tomorrow survives; a forty-minute document that helps next quarter does not.

Should we ban meetings to force async?

No. Banning meetings without removing the need for them pushes the same conversations into direct messages, which is worse, because it is unrecorded and it interrupts individuals rather than a scheduled group. Remove the reason for the meeting first.

How do we know if async is working?

Measure how long a typical question waits for an answer, and how often work stops while waiting. Those two numbers tell you more than any count of meetings. If both fall, async is working, whatever your calendar looks like.