Working with a distributed team across time zones

I've built with people scattered across time zones — collaborators I've sometimes never met in person. The naive approach is trying to sync constantly, and it fails by exhausting everyone. What works is treating async as the design, not the fallback.

The principles

Writing is the backbone. Decisions live in documents, not in chats that scroll away. If a decision isn't written where the team can find it, it wasn't made — it was murmured.

Over-communicate context, under-communicate urgency. Every message carries why it matters, because the reader might see it twelve hours later with zero of my morning's context. Urgency is rare and explicit; context is constant and assumed.

The handoff is the artifact. My day's last act is leaving work a collaborator can pick up cold: what I did, what's blocked, what needs their eyes. Done well, the time difference becomes a relay — work advances while the other half of the world sleeps.

Meet rarely, and only to decide. Live calls are for decisions that writing can't settle. Everything else is text, because text has a memory and a timezone of its own: none.

Async done right isn't lonelier. It's calmer — and calmer ships.