Time zones and async: working well when nobody's online together

Distributed teams run on asynchronous work — collaboration that doesn't require being online at the same time. Done well, it's a superpower: the project advances around the clock. Done badly, every question loses a day. The difference is technique.

Write messages that don't need a reply to your reply

The core async skill is anticipating the follow-up question and answering it in advance. Compare:

"Can we change the deadline?" — this costs a full round trip.

"Can we move the deadline from Thursday to Monday? The supplier confirmed delivery slipped to Friday. If Monday works, I'll update the plan and notify the client; if not, I can deliver a partial version Thursday — here's what it would include."

The second message can be answered with one word, from any time zone, and work continues either way.

Default to visible progress

• Work in shared documents and trackers, not private files, so progress is observable without asking.
• Post a brief daily or end-of-block update: done, next, blocked. Three lines is plenty.
• When you're blocked, say so immediately and switch to the next task — don't wait in silence for an answer that's eight hours away.

Respect the overlap window

Most distributed teams have a few shared hours. Guard them for the things async does badly: decisions with many stakeholders, sensitive feedback, brainstorming, and anything emotionally loaded. Everything else — status, reviews, questions with clear context — belongs in writing.

Make your hours legible

Keep your working hours on your calendar and your profile. Say when you'll deliver, in the other person's time zone ("by 9am your Tuesday"). Small courtesies like this are how strangers across twelve time zones come to feel like a team.

Async work rewards the considerate. Every clear message you write is a gift to a colleague who wakes up after you've gone to bed — and the teams that internalize this ship faster than any office ever did.