Folta Studio works with clients across Europe and Asia. For a large part of the week, nobody on the team is awake at the same time. Async work is not a compromise we tolerate; it is a discipline we practice.
Write decisions, not updates
The single most useful habit: write down decisions, not status reports. A decision log answers “why is it built this way” months later. Status updates only answer “where are we”, which is stale by the time someone reads it.
Every important discussion ends with one sentence in the project log: what was decided and who owns it.
Review in a cadence, not in real time
Real-time review only works when everyone is online. We review in fixed windows: a pull request gets feedback within one working day, and the reviewer blocks time for it. Predictable latency beats fast but random latency.
Make handoffs self-contained
A handoff is ready when the next person can act without asking a question. That means a short summary, a link to the relevant files, and the one decision that needs their input. If a handoff needs a back-and-forth, it was not ready.
Timezone is a feature, not a bug
Eleven hours apart means one side always has a full working day before the other replies. Used well, that overlap turns review loops into overnight progress. The trick is to end each day with a clear, small next action the other side can start immediately.
The Folta rhythm
We keep a small set of written artifacts: a decision log, a short handoff note per task, and a fixed review window. It costs a few minutes per task and removes most meetings from the project.
Async work does not need perfect tooling. It needs the discipline to write things down well enough that the team does not need to be in the same room.