Distributed Work, Unknotted

No. Use written communication for information and independent input, and use live conversation when dialogue helps resolve ambiguity, sensitive issues or interdependent decisions. See the meeting decision tree.

There is no universal minimum. Start with the work that genuinely needs simultaneous participation, test a limited overlap window, and review whose working day carries the burden. Do not assume that more overlap automatically produces better coordination.

Agree it by channel and type of request. Routine responses should account for local working periods, leave and public holidays. Urgent incidents need a separate, explicit coverage process. Put the expectation in a working agreement rather than leaving people to infer it.

Summarize the decision in the agreed project record with its owner, rationale, current status and next action. Link to that record from the original chat. Our async writing guide explains how to keep that summary readable.

Treat ownership as pending, keep the status visible and use the agreed backup arrangement. Do not assume a notification means the recipient accepted the task. The handoff checklist includes an explicit acknowledgment step.

No blanket requirement is necessary for good collaboration. Consider accessibility, bandwidth, privacy and the purpose of the conversation, and provide other ways to participate. A visible face is not proof of understanding or engagement.

Agree on outcomes, make commitments explicit and welcome early blocker signals. Review usable work and support needs rather than online indicators, keystrokes or message volume. Address specific missed agreements directly instead of introducing surveillance for everyone.

Local offsets can change on different dates or not change at all. Recheck recurring meetings, coverage and handoff deadlines using current time-zone information. A named zone such as Europe/Berlin is usually more informative for recurring events than a fixed offset alone.

Use plain language, define abbreviations, share preparation in advance and allow written input. Do not treat speed or fluency in live discussion as a measure of expertise. Ask colleagues what would make participation easier instead of guessing from their background.

Pick one recurring point where work waits. Add the missing owner, source, acceptance criteria or response agreement, then ask the receiving colleague whether the change helped. Keep the experiment small enough to evaluate without creating another reporting burden.