The one-day rule

With a big offset, every unclear message costs a full day: you ask at your 10:00, they answer at their 10:00, and if the answer is "what do you mean?" — that's 48 hours for one clarification. Async across time zones is therefore mostly about writing messages that don't need a follow-up question:

  • Include the context — link the ticket, paste the error, screenshot the screen. Assume they can't ask.
  • Make the ask explicit: "I need a yes/no on X" beats "thoughts?"
  • Offer a default: "Unless you object by your EOD, I'll ship option A." Blocked becomes unblocked-by-default.

The end-of-day handoff

The highest-leverage async habit: a short written update at the end of each region's day — what moved, what's blocked, what you need from whom. It's waiting at the other region's morning coffee, turning the timezone gap into a relay instead of a wall. Teams that run this well (GitLab and other all-remote companies wrote the book on it) effectively work a 24-hour development day.

Decisions live in documents, not calls

When a decision spans regions, a shared doc with a deadline beats a meeting nobody can attend:

  1. One page: context, options, recommendation, deadline ("comments until Thursday, then we decide").
  2. Everyone comments in their own working hours.
  3. The owner decides, records the outcome in the same doc, and posts the link.

The doc is the meeting — with a permanent record for whoever joins the team next year.

Record instead of present

Demos, walkthroughs, onboarding, sprint reviews: record a 5-minute screen capture instead of scheduling a call. Viewers watch at 1.5× in their own morning and leave timestamped comments. Save live calls for what genuinely needs back-and-forth in the moment: sensitive feedback, incident response, negotiation, and relationship-building — those are worth an odd hour, occasionally and rotated fairly.

Respect the clock you can't see

Async fails socially when messages arrive as 2am phone buzzes. Norms that keep it humane:

  • Use scheduled send — write in your afternoon, deliver in their morning.
  • Check before you ping. A glance at a menu bar world clock with availability statuses — like GlobalTimeZones — tells you the red dot means "asleep" before you hit send. Renaming cities after teammates makes it effortless.
  • Agree that nobody is expected to reply outside their hours — and have leads model it.

What good looks like

A healthy async team across time zones: mornings start by reading handoffs, decisions have documents and deadlines, demos are recordings, the few live meetings land inside real overlap windows, and nobody's phone buzzes at 2am. The offset stops being friction and becomes what it actually is — a 24-hour workday your competitors don't have.