Async Standups for Teams Across Africa's Time Zones
A team split between Lagos, Kigali and Nairobi isn't far apart on a map, but the clocks differ by up to two hours, and that's before someone loses power or a connection drops mid-call. A daily video standup can be a real cost for a team like that. A written one usually works better.
The time zone reality
Africa spans several zones, and no single "African time" exists. Roughly:
- West: Ghana and Senegal keep UTC+0; Nigeria, Cameroon and others sit on West Africa Time (WAT, UTC+1).
- North: Morocco, Algeria and Tunisia are around UTC+1; Egypt and Libya are on UTC+2. A few countries shift their clocks for daylight saving or Ramadan.
- Central and Southern: Central Africa Time and South Africa Standard Time (CAT/SAST) are UTC+2 — South Africa, Zambia, Zimbabwe, Rwanda and others.
- East: Kenya, Uganda, Tanzania and Ethiopia are on East Africa Time (EAT, UTC+3).
Between Accra and Nairobi that's already a three-hour gap, and much more once you add a contractor in Europe or North America. Since a few countries change their clocks, check the current offset before you fix a recurring meeting time.
Even inside one zone, "everyone online at 9:00" is optimistic. Commutes, load-shedding and unreliable connections mean a live call routinely starts with three people missing.
What a standup is actually for
Strip away the ritual and a standup answers three questions: what did you finish, what are you doing next, and what's blocking you. None of these needs a live conversation. They need a place to write down the answers and a way for teammates to react.
A written standup format
Each person posts once per working day, at the start of their own day, in a single agreed place:
- Done: what I finished since my last update.
- Next: what I'm working on today.
- Blocked: anything I need, and from whom — tagged by name.
Keep each update to a few lines. The point is speed, not a status report nobody reads.
Let the board do most of the talking
If tickets are up to date, half the standup already exists. Someone opening the board can see what's In progress, who owns it and what's stuck. That's why the written update should point at tickets rather than restate them: "Done: the homepage banner. Next: checkout copy. Blocked on the logo files from Amina."
In Alignr you can mention a teammate by name in a ticket comment, and they're notified, which makes "blocked on" a concrete request instead of a vague hope. Checklists inside a ticket keep bigger tasks visible without splitting them into a dozen cards.
Find the overlap, and protect it
Async doesn't mean never talking. Work out the hours when most of the team is online — often a two- or three-hour window mid-morning — and use it for the conversations that are better live: tricky decisions, kickoffs, retros that need discussion. Everything else goes in writing.
Meet when you need a conversation. Write when you only need to inform.
Design for bad connections
- Prefer short text updates over long calls or large video files.
- Assume replies can take a few hours. Don't make anything urgent depend on an instant answer.
- Put decisions on the ticket, so a person who was offline sees the outcome, not just chat fragments.
- Try any tool on your team's real connections during the trial, not just office Wi-Fi.
Once a cycle, look back
Daily updates keep the work moving; a retro at the end of each sprint keeps the process improving. We cover a low-effort version in how to run a retro when everything lives on WhatsApp. And if your team is still deciding how to set up sprints, start with the small-team sprint guide. Working across Asia's time zones instead? Read the Asia version of this guide.
Boards and sprints work on Alignr's free plan (up to two users); a larger team needs the Team plan at $2 per user per month, billed in USD. Start free to see whether the written routine suits you.