Support/Project Process/Working across timezones
Project Process

WORKING ACROSS TIMEZONES

2,900 views
remotecommunication

Asynchronous by default, with a small number of scheduled overlaps.

Default: asynchronous

Written updates, attached files, decisions in the thread. This works in every timezone and leaves a record.

Scheduled overlap

Where a project needs live discussion, we agree fixed slots at the start rather than negotiating each week. Two half-hour slots per project phase is usually plenty.

Handoff notes

Every phase ends with a written handoff note: what is done, what is pending on us, what is pending on you. If you read one message per week, read that one.

What breaks

Projects where every decision needs a call. If your organisation cannot approve anything in writing, tell us at scope stage — it changes the timeline, not the possibility.

Was this helpful?

Tell us honestly. It is read by the people who write these pages.

If this didn't answer your question, ask Xylo.

Back to Project Process