Remote & async collaboration

Every remote practice follows from one fact: with four or more hours of timezone offset, a question and its answer cost a day. That makes round trips the currency. Ask with full context and a proposed answer. Write documents that can be reviewed without a meeting. Give reviewers a deadline. Prefer an over-communicated message that pre-answers the follow-up.

Default to writing, and write in the open. Decisions in DMs or calls don't exist for anyone who wasn't there and can't be searched next quarter. A decision log, an ADR, a comment on the ticket — the format matters less than that it's findable. This is also how work becomes visible: in an office, presence signals contribution; remotely, only the written record does, and engineers who are quiet in writing get under-credited regardless of output.

Spend synchronous time on what needs it: disagreement, ambiguity, design exploration, feedback with emotional weight, onboarding, and relationship-building. Status is not one of those things — a written update replaces a standup and is more useful than one. Where overlap hours exist, protect them for the things above rather than filling them with recurring meetings.

Handoffs are the async superpower: someone in another timezone continues where you stopped if you leave the state behind. That means the branch pushed, the PR description updated with what's done and what's next, and blockers named. Done well, an offset team gets nearly two working days per calendar day; done badly, it gets half of one.

The failure modes worth naming: isolation, which is real and needs deliberate structure rather than optimism; always-on drift, where async is misread as instant and people stay in chat all day, which destroys the focus that made remote worthwhile; and timezone inequity, where the same people always take the 10pm call. Rotate it.

Most of the target companies in PRD.md §1.1 are remote-first, and they interview explicitly for async working: written communication, self-direction, and comfort making decisions without a meeting. Your PR descriptions, take-home README, and email replies are all read as direct evidence of it.

• Timezone offset makes round trips expensive; ask questions with context and a proposed answer.
• Write decisions down in a findable place — DMs and calls leave no record.
• Visibility remotely comes from the written record, not from presence.
• Reserve synchronous time for disagreement, design, feedback, and onboarding; never for status.
• Leave clean handoffs — pushed branch, updated description, named blockers — so work continues without you.
• Async does not mean instant; protect focus time or remote work loses its main advantage.
• Rotate inconvenient meeting times so the cost of overlap is shared.
• Remote-first companies read your written artifacts as direct evidence of how you'd work.
• The difference between a distributed team that ships and one that doesn't is where its overlap hours go.