A design project across time zones works when you treat the time difference as a schedule, not a problem. Keep one short overlap window for the conversations that need a conversation, put everything else in writing, send feedback in batches rather than as it occurs to you, and plan ahead for the few weeks a year when clocks change. Done that way, a team ten hours apart can move faster than one in the same building, because work continues while the other side sleeps.
This is the routine we run from India with teams in New York, London, Dubai and Sydney. None of it needs special software.
1. Find the real overlap, then protect it
Start by working out the hours you actually share. For a team in New York that is usually your morning and our evening. For London it is your morning and lunchtime. For Dubai it is nearly the whole day. Our time zone overlap tool shows the shared hours for any city in both local times.
Then protect that window. Use it for decisions, reviews and anything with real disagreement in it. Don’t spend it on status updates that could have been a message. A 30 minute call twice a week is enough for most brand and website projects once the founder sessions at the start are done.
2. Write decisions down where both sides can find them
When you can’t lean over a desk, the written record is the project. After every call, someone writes down what was decided, what is still open and who owns the next step, in the place the team already looks: a Slack thread, a Notion page or a comment on the Figma file.
This matters more than it sounds. Most delays on remote projects aren’t caused by the time difference. They come from two people remembering a call differently and finding out a day later.
3. Give feedback in batches
Feedback that arrives a line at a time across a whole day is hard to act on overnight, because the studio doesn’t know when you’re finished. Collect your comments, send them once, and say clearly when a round is complete.
Good feedback across time zones has three parts:
- What you’re reacting to. Pin comments to the exact frame or section in Figma rather than describing it.
- What the problem is, in terms of the goal rather than the fix. “A buyer won’t see the pricing link” is easier to solve well than “make the button blue”.
- Who decides. If three people on your side have opinions, name the one who settles them. Conflicting notes cost a full day each time.
A short screen recording often beats a long message. Talk through the page as you scroll; it takes two minutes and removes most of the back and forth.
4. Use the time difference as overnight turnaround
When you are behind the studio, as US and European teams are with us, the gap works in your favour. Send a round of feedback at the end of your day and the revised work is usually waiting in your morning. Plan reviews around that rhythm: you review in the afternoon, we work, you review again the next day.
When you are ahead, as Australian teams are, it runs the other way. Your afternoon is our morning, so calls sit late in your day and we keep working after you’ve logged off.
5. Plan around different weeks and clock changes
Two calendar quirks catch people out.
Different working weeks. Saudi Arabia works Sunday to Thursday. The UAE moved to a Monday to Friday week in 2022. India works Monday to Friday. With a team in Riyadh, that leaves Monday to Thursday for live calls and Sundays and Fridays for async work.
Daylight saving. India does not change its clocks, so every switch on your side moves your call. And the US and Europe don’t switch on the same day. In spring the US moves its clocks on the second Sunday of March and most of Europe on the last Sunday of March, so for two or three weeks the gap between New York and London is an hour shorter than usual. In autumn Europe switches on the last Sunday of October and the US on the first Sunday of November. Australia switches the opposite way round, in October and April. If a call involves people in more than one of these places, check it again in those weeks.
6. Keep the tools boring
You don’t need anything special. What matters is that both sides use the same few places and stop using the rest.
| Job | What we use |
|---|---|
| Design and comments | Figma |
| Day to day conversation | Slack, in a shared channel |
| Decisions and scope | One shared doc per project |
| Calls | Google Meet or Zoom, recorded when useful |
| Walkthroughs | Short screen recordings |
The one rule: if it was decided, it lives in the shared doc. If it was only said on a call, it wasn’t decided.
7. Set expectations on response times
Agree up front how fast each side replies during the working day, and what counts as urgent. For most projects a few hours during working time is fine, and nothing is urgent except a live site being down. Writing that down early stops either side reading silence as a problem.
What this looks like in a week
A typical week with a US team: founder or review call Monday and Thursday in your morning, feedback batches sent at the end of your Tuesday and Thursday, revised work waiting each following morning, and a written summary on Friday of what moved and what’s next. The calendar has two meetings on it. The work moves every day.
More on how we work with teams in specific places: the USA, the UK, Germany, the UAE, Saudi Arabia and Australia.
Quick recall
What is the overlap window for? Decisions, reviews and disagreement. Status goes in writing.
Where do decisions live? In one shared doc. If it was only said on a call, it wasn’t decided.
How should feedback be sent? In batches, pinned to the frame, with one named decider.
Why does the US to Europe gap change in March? The US moves its clocks two to three weeks before most of Europe does.
Which week does Saudi Arabia work? Sunday to Thursday, so live calls with India sit Monday to Thursday.
Written by 4080 Studio.
