Asynchronous Communication and Peace of Mind

You know the feeling. When the "typing..." indicator shows up, suddenly you are waiting too, and once the two blue ticks appear, there's a clock running. You take forty minutes to reply to a message about dinner plans and open with "sorry, just saw this," as if you owe someone an explanation.

I think there is a better way, and it is an old one: asynchronous communication.

We made everything real-time

Somewhere along the way, we agreed that every conversation has to happen right now. Slack shows a green dot when you're online, WhatsApp tells the sender exactly when you read their message, and email, which was designed to sit in an inbox and wait, has turned into chat with a subject line.

I am not only on the receiving end of this either. As a CTO, I am the one sending a lot of those "quick question" pings, and each one feels tiny when I hit send. On the other side, someone drops whatever they were deep in, because the notification looks exactly the same whether it is a production outage or me asking where a doc lives.

Most of these conversations do not need to be real-time. The quick question can wait an hour, and the group chat planning next week's dinner can certainly wait an hour, yet we treat every ping like a fire alarm.

What async actually means

The idea is simple. Since you send a message when it suits you and the other person replies when it suits them, nobody gets pulled out of a half-finished thought. It is how email was supposed to work before we ruined it.

The interesting part is what happens when you actually try it. On the days I manage it, deep work gets properly deep, because I am not surfacing every ten minutes to check a green dot, and evenings go back to being evenings. The thing everyone is afraid of, that something will fall apart because you didn't reply within four minutes, mostly does not happen. Work still ships, and people still like you.

Doing it without being a jerk

Going async does not mean ghosting people or ignoring the messages that matter. It means telling people what to expect, so that your silence does not read as rudeness.

Start by saying when you check messages. A status like "checking messages at 10 and 4" does a surprising amount of work. Give people a real channel for real emergencies, like a phone call, and then keep your word: if you said you would reply within a day, reply within a day. Async only works when people can trust the delay.

If you lead a team, this part is more on you than on anyone else, because people copy what you do rather than what the handbook says. If the manager is replying to threads at 11 PM, the whole team has just learned that 11 PM is a working hour, whatever the policy doc claims.

The peace dividend

Productivity is the easy pitch, but I think the bigger benefit is peace of mind. When you are not constantly available, you get time to think, whether that means staying with a hard problem long enough to solve it or eating dinner without your phone buzzing on the table.

It is the same reason I keep coming back to a notebook and a pen: some of the best tools for thinking are the ones that cannot interrupt you.

So try it for a week. Turn off instant notifications for anything that isn't a real emergency, and check messages on your schedule instead of everyone else's. My guess is that very little of it will turn out to be urgent.

And the next time you see "typing...", let them type. You can read it when you are ready.

P.S. If you checked your phone twice while reading this, it can wait. Probably.