A call is the most expensive communication tool you have. It demands everyone’s attention at the same moment, in the same time zone, with no record left behind. Reach for it last, not first.

Write it down instead

Most “quick calls” are actually a question that could’ve been a message, answered faster in writing because the other person doesn’t have to schedule anything to reply. Default to a written message. Escalate to a call only when you’ve gone back and forth in writing three times without resolving it, or the topic is emotionally sensitive.

Decision records, not meeting notes

When a real decision gets made, in a call, in a thread, wherever, write it down in one place everyone can find later:

• What was decided
• Why, in two or three sentences
• Who decided it
• What it would take to revisit it

This takes five minutes and saves the exact same conversation happening again in three months when someone new joins and asks why do we do it this way.

Daily written updates beat daily standups

A standup call at a fixed time forces one time zone to always be inconvenienced. A written update — what I did, what I’m doing next, what’s blocking me — posted whenever someone starts their day, gives the same visibility without the synchronous tax. Keep it to three lines. Nobody reads a ten-line standup post either.

The meetings worth keeping

Meeting	Keep sync?	Why
1:1s	Yes	Relationship, hard to fake in writing
Status updates	No	Written, always
Brainstorming	Sometimes	Real-time back-and-forth has value here
Decisions with real disagreement	Yes	Faster to resolve live than over ten Slack messages
Announcements	No	Written, with a place for questions

Set response-time expectations explicitly

Async fails when people assume instant replies anyway. State it plainly: “Non-urgent messages get a reply within a business day. Urgent means production is down, use the pager, not Slack.” Without this stated, someone always ends up checking Slack at 11pm out of quiet obligation.

What breaks async

• Decisions made verbally in a call and never written down. They evaporate the moment the meeting ends and get re-litigated later by someone who wasn’t there.
• Threads with no conclusion. If a Slack thread ends without someone stating the decision, it wasn’t actually resolved, it just stopped.
• Treating async as slower. Done right it’s faster on average, no calendar tax, no time zone tax, even though any single reply might take a few more hours.

The point isn’t fewer meetings for their own sake. It’s making sure the record of what happened, and why, lives somewhere durable instead of in someone’s memory of a call.

---