Async Client Communication Works Better Than Anyone Admits

I used to run weekly status calls on every project by default, because that's just what consultants do. At some point I started asking what each call was actually for, and the honest answer was usually: giving a verbal version of an update I could have written down more precisely in ten minutes.

I switched one project to a structured written update instead — same cadence, same content, delivered as a short doc instead of a call. The client initially asked for the call back out of habit. Three weeks later they told me they preferred the written version, because they could forward it to stakeholders who weren't on the original call without a game of telephone.

What actually got better

• Decisions got faster, because a written question with a clear deadline for response beats waiting for the next scheduled call to even ask it
• Nothing got lost to someone's bad memory of what was said verbally — there was a document to point back to
• Stakeholders who weren't in the original relationship could read the update directly instead of relying on a secondhand summary
• I stopped losing an hour of actual work time per week per client to call scheduling friction and the inevitable fifteen minutes of small talk before getting to substance

A status call is usually a verbal performance of an update that would be clearer, faster, and more useful written down.

Where calls still genuinely win

This isn't a case against ever talking to clients — a real scoping conversation, a disagreement that needs real-time back-and-forth, or a kickoff where rapport actually matters all benefit from a live call. The shift was specifically about recurring status updates, which almost never need to be live and almost always get worse when forced into a scheduled synchronous slot. Reserve the calls for the conversations that actually need two people talking at the same time, and default everything else to writing.