Working Across Time Zones With African Talent: A Schedule That Actually Works

Founders often assume remote talent in Africa means a big time zone gap. For most European teams the gap is zero to three hours, and for the US East Coast it is a comfortable morning overlap. The difference is not the problem. The absence of a plan is. Here is a working week that teams in London, Berlin and New York use with developers, designers and assistants in Accra, Lagos and Nairobi.

Start with the actual numbers

Accra runs on UTC, the same as London in winter and one hour behind it in summer. Lagos is UTC+1, so it matches central Europe and sits one hour ahead of London. Nairobi is UTC+3. None of these countries change their clocks, which means your overlap shifts by an hour twice a year when yours do.

• London team: Accra and Lagos share almost the entire working day; Nairobi shares about six hours.
• Berlin, Paris or Amsterdam team: Lagos matches exactly; Accra is one hour behind; Nairobi is one or two ahead.
• New York team: Lagos and Accra share about four hours, from 9am to 1pm New York time; Nairobi shares about three.
• San Francisco team: one to two hours of overlap in the morning, so written handoffs carry the work.

Agree an overlap window, not a workday

The mistake that burns people out is asking a talent in Nairobi to work New York hours. It works for a month and then quietly stops working. Instead, agree a fixed overlap window of two to four hours when both sides are online for meetings, pairing and quick questions. Outside that window, the talent works their own normal day.

Write the window into the contract with both time zones spelled out, for example 2pm to 5pm Lagos, 9am to 12pm New York. Put it in the calendar as a recurring block so nobody schedules over it.

Move decisions into writing

With a short overlap, every decision that lives only in someone's head costs a day. The fix is a single written home for decisions: a project tool, a shared document, a pinned channel. When a question comes up outside the overlap, it goes there with enough context that the other side can answer it on their morning without a call.

This also fixes a problem you did not know you had. Written decisions are searchable. Verbal ones evaporate.

End the day with a handoff

The most effective habit in a time shifted team is a short written summary at the end of each person's day. Three lines: what shipped, what is blocked, what is next. The other side wakes up to a clear picture instead of silence, and a blocker raised at 5pm in Lagos is unblocked by 9am in New York, before the Lagos day has even ended.

Use the gap instead of fighting it

A time shift is an advantage once the handoffs are working. A designer in Accra can finish the mockups while the London founder sleeps, and the founder reviews them over coffee. A developer in Nairobi ships a fix at their 4pm, and the US team tests it at their 9am. Work moves around the clock without anyone working around the clock.

The teams that struggle are the ones that insist on live meetings for everything. The teams that thrive treat the overlap window as precious and use it for the conversations that genuinely need two people at once.

Keep meetings few and inside the window

A weekly planning call and a short mid week check in are usually enough for a small team. Both go inside the overlap, both have a written agenda, and both end with decisions recorded in the written home. Anything that can be a message should be a message.

The overlap is for conversations that need two people at once. Everything else is a well written message.

Hire for the window you actually have

When you browse profiles on DevDey, each talent's time zone is shown alongside their location, so you can see the overlap before you message anyone. Start with developers, designers or virtual assistants, agree the overlap window in your first conversation, and read Async Communication: How Remote Teams Get More Done for the written habits that make the rest of the day productive.