craigmcn

Slack and email were supposed to make workplace communication faster. Instead they gave us forty-message threads that a two-minute phone call would have resolved in the time it takes to say hello, followed by a scheduled follow-up meeting to clarify what the thread failed to settle. The promise was efficiency. What we got was a different kind of slowness, one that feels productive because it generates a paper trail, even when the actual problem sits unresolved somewhere around message thirty-one.

And yet I’m not convinced the answer is just “call more”. A well-written email, one that actually gives context and links to whatever it’s referencing, beats a call most of the time, because it lets me think before I respond instead of performing comprehension in real time on someone else’s clock. The problem was never asynchronous communication. The problem is low-effort communication, and both calls and emails can fail that test equally. A rushed call with no agenda wastes exactly as much time as a context-free email that assumes I already know what “following up on this” refers to.

That’s also why “quick call?” as a Slack message lands as a small ambush rather than an offer. It assumes the other person has nothing better to do than drop whatever they’re doing and switch modes instantly, on your timeline rather than theirs. Compare that to an email with a clear ask and the relevant link attached: it respects that the recipient might be in the middle of something else, and it lets them engage with the actual substance instead of scrambling to catch up verbally.

So the office didn’t kill the phone call so much as expose what it was never good at. Calls are for things sync actually helps, urgent alignment, a decision that needs back-and-forth, a tone that email keeps flattening into ambiguity. Everything else is better served by writing it down properly the first time. The real failure isn’t the medium. It’s how rarely either one gets used with any care.