Website

Working With a Development Team Across Time Zones: Routines That Make Distance an Advantage

November 11, 2026 · 6 min read · Etzal Group Team

A company in California hires a development team in Jakarta, fourteen or fifteen hours ahead. In the first month, each question from the team waits overnight for an answer, each answer raises another question, and a feature that should take a week takes three. The client concludes that the distance is the problem. In month three, with different habits, the same team delivers work that the client reviews over morning coffee and that is corrected before the client wakes again. Nothing about the time zones changed. The routines did.

Know the arithmetic

Write down the working hours of both sides in one table, including daylight saving changes for places that have them.

  • Jakarta and Singapore: one hour apart. Nearly a full shared day.
  • Jakarta and Western Europe: five to six hours. A shared afternoon in Jakarta, morning in Europe.
  • Jakarta and the US East Coast: eleven to twelve hours. Overlap only at the edges of the day.
  • Jakarta and the US West Coast: fourteen to fifteen hours. Late afternoon in California meets early morning in Jakarta.

Indonesia itself has three time zones, and holidays differ by country. Share a calendar of public holidays at the start of each year.

Fix the overlap window

Agree on a window of shared time, and protect it.

  • Two to three hours, on agreed days.
  • Share the inconvenience. If one side always takes the early or late slot, resentment builds. Rotate, or split the difference.
  • Use the window for what needs conversation: unclear requirements, design discussions, demos, difficult decisions.
  • Do not use it for status. Status is written.

Outside the window, nobody is expected to be reachable, except for defined emergencies.

Write so that work continues without you

Asynchronous work lives or dies on the quality of what is written.

The brief

Each piece of work has a written description with:

  • The goal: what the user should be able to do, and why.
  • Acceptance criteria: how we will know it is done.
  • Constraints: what must not change, deadlines, dependencies.
  • Examples: screenshots, sample data, edge cases.
  • Who decides open questions.

Ten more minutes on the brief saves a day of waiting.

The question

A good asynchronous question can be answered in one reply.

  • Context: what I am working on.
  • The question, precisely.
  • Options considered, with a recommendation.
  • What I will do if I hear nothing: "I will proceed with option A unless told otherwise by tomorrow."

The daily handover

At the end of each working day, each side writes a short note.

  • Done today.
  • In progress.
  • Blocked, and by what.
  • Questions for the other side, numbered.
  • What happens next.

The other side starts its day by reading and answering. This single habit removes most lost days.

Decisions

Record every decision in one place: what was decided, why, by whom, when. Decisions buried in a call or a chat thread get relitigated.

Give people the right to decide

Waiting is the real cost of distance. Reduce the number of things that need to wait.

  • Define what the team may decide alone: technical implementation, naming, small interface details inside the design system.
  • Define what needs the client: scope, anything affecting cost or date, anything visible to customers in a new way.
  • Appoint one decision maker on the client side, with a stated response time.
  • Agree on the default: when blocked, proceed on a stated assumption or move to the next item, and flag it.

A team that must ask permission for everything will be slow at any distance.

A weekly rhythm

  • Planning, once a week, in the overlap window: priorities, what will be delivered, risks.
  • Demo, once a week or fortnight: working software, recorded for those who cannot attend.
  • Written daily handover, both directions.
  • One or two short calls in the window for discussion that writing cannot settle.
  • Retrospective, monthly: what slowed us down?

Record demos and important calls, with a short written summary. People in the other zone, or back from leave, can catch up without a meeting.

Tools, used with discipline

The tools matter less than the rules for using them.

  • One place for tasks, with status that is true.
  • One place for documents and decisions.
  • Chat for quick matters, with an agreement that chat is not a record. Anything that matters is moved to the task or the document.
  • Recorded screen walkthroughs for explaining a bug or a design. Five minutes of video replaces a meeting across twelve hours.
  • Access set up on day one: repositories, environments, test accounts. Waiting three days for a password is a classic distributed-team delay.

Turning distance into an advantage

  • Follow-the-sun review. The team builds during its day. The client reviews during theirs. Feedback is ready when the team returns. A full cycle every twenty-four hours.
  • Overnight fixes. A bug reported at the end of the client's day can be fixed by morning.
  • Longer support coverage without night shifts, if both sides share on-call sensibly.
  • Quiet time. Developers get long uninterrupted stretches, which is when the best work happens.

These gains appear only when handovers are clean.

People, not only process

  • Meet in person when you can, at the start and once or twice a year. Trust built face to face lasts.
  • Use video in the overlap window, at least some of the time.
  • Be explicit. Across cultures and languages, hints get lost. Say what you need and by when. Invite disagreement directly, because in many working cultures people hesitate to contradict a client.
  • Write simply. Short sentences, no idioms, dates written in full with the time zone.
  • Respect the off hours. A message sent at night is read in the morning. Do not expect otherwise.
  • Know the holidays and long leave periods on both sides.

Emergencies

Define them before one happens.

  • What counts: production down, data at risk, a security incident.
  • Who is called, in what order, on which channel.
  • Expected response time.
  • Who can decide to roll back or take a system offline.

Everything else waits for working hours.

Common mistakes

  • No fixed overlap window, so every call is negotiated.
  • One side always taking the bad hours.
  • Status meetings in the precious shared time.
  • Briefs of one line.
  • Questions with no context or recommendation.
  • No daily handover.
  • Decisions made in calls and never written.
  • A team with no authority to proceed.
  • Several people on the client side giving different answers.
  • Access and accounts set up late.
  • Dates written without a time zone.

We work with clients in Indonesia, Singapore and other time zones using these routines, as part of Enterprise Software. If you are considering a team in another time zone and want to see how the working week would run, contact us.

Summary

Distance costs time only when questions wait. Fix a shared window of two to three hours and use it for discussion, not status. Write briefs with goals and acceptance criteria, ask questions that carry a recommendation and a default, and exchange a written handover each day. Give the team clear rights to decide, name one decision maker, record decisions, keep a weekly rhythm of planning and demos, and define emergencies in advance.

Frequently asked questions

How many hours of overlap does a distributed team need?

Two to three hours of shared working time on most days is usually enough when the rest of the work is well documented. With less than one hour, every question costs a day and the team needs very strong written habits. More than four hours makes collaboration easy and is rarely necessary.

What is asynchronous work?

It is working without requiring the other person to be available at the same moment. Questions, decisions and progress are written down in a shared place, with enough context that someone can act on them hours later without a meeting. It depends on clear writing and on people being trusted to decide within agreed limits.

How do we avoid losing a day whenever the team has a question?

Give the team the context and authority to proceed: a written brief with the goal and constraints, a named person who answers within an agreed time, and a rule that when blocked they continue with a stated assumption or switch to the next task. End each day with a written handover listing open questions.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.