Async Work and the Case for Being Slower on Purpose

Most remote teams didn't choose to work in real time. They just carried office reflexes into chat, and chat has no closing time.

Async is not slower. It's slower to respond and much faster to finish, because the work that produces anything of value requires uninterrupted stretches that a real-time culture never allows.

Set a response-time expectation out loud

The single highest-leverage sentence: "I check messages a few times a day, if it's urgent, call me." Say it once, put it in your status, then behave consistently. Almost nobody objects. The anxiety about it is nearly always worse than the reaction.

Write so nobody has to ask twice

Async only works if messages carry enough context to be actioned without a follow-up round. A good async message has: what's happening, what you need, from whom, and by when. Everything else is optional.

Bad: "Can we talk about the pricing thing?" Good: "Pricing page copy. I need a yes/no on the annual discount line by Thursday so it ships this sprint. Draft in the doc, comments welcome."

Protect two deep blocks a week

Two, not five. Five is a fantasy and you'll abandon the whole system when it fails. Two blocks of two hours, in your calendar, named after real work, with notifications off and chat closed. If someone books over them, move them, don't delete them.

Pace like the job lasts years

• Batch shallow work into one window rather than sprinkling it through the day.
• Plan to about 70% of capacity. The other 30% gets consumed by reality whether you allocate it or not.
• Do the hardest thing in your best hours, not your emptiest hours. For most people that's the first two hours of the day, which is exactly when they do email.
• Take breaks that involve moving. A walk in the middle of the day is not a break from productivity, it's the input that makes the afternoon work at all, plenty of people find a daily walk is the single change that holds the rest of the routine together.

The always-on trap

Constant availability feels like commitment and reads, over months, as burnout. If you're worried that being less instantly responsive will look bad, replace the signal: send one clear written update a week that shows what moved. Visible output beats a green dot, and it costs a fraction of the energy.