How to run a sprint retrospective across time zones

The classic retrospective assumes everyone is in one room for an hour. A distributed team rarely has that hour. The fix is not a longer call at a worse time; it is to move the slow part, gathering input, off the clock entirely, and reserve live time only for the conversation that genuinely needs it.

Why the usual retro format breaks across time zones

A live, write-as-you-go retro spends most of its hour on silent note-writing and reading. That is fine when everyone is awake. Across a wide spread of zones it forces someone to dial in at midnight, and the tired person says less, which quietly erodes the honesty a retro depends on. This is not an edge case: in Buffer's 2021 State of Remote Work report, 74 percent of respondents said people on their immediate team are in multiple time zones. Two things make it work again: separate input from discussion, and protect the overlap for the part that needs voices.

What happens in each phase?

Splitting the retro into an async collection window and a short live discussion gives everyone an equal chance to contribute, regardless of where they sit.

Phase one: collect input asynchronously

Open a shared board (any retro tool, or a simple doc) with the usual columns, such as what went well, what did not, and what to try. Give it a real deadline, roughly 24 hours, so it spans every team member's working day at least once. Keep notes hidden or anonymous until the window closes. This matters: when people cannot see each other's notes first, you get independent thinking rather than an echo of whoever posted earliest.

• One board, clear columns. Fewer prompts get more honest answers than a long survey.
• A hard deadline in each person's local time. "By the start of your Thursday" beats a single UTC timestamp nobody can convert.
• Private until reveal. Hide notes during collection to protect independent input.

Phase two: a short live discussion in the overlap

Before the call, the facilitator groups the notes into a handful of themes and drops duplicates. Now the live session is only for discussion and decisions, so 30 to 45 minutes is plenty. Pick the slot that sits inside your team's shared waking hours and rotate it over time so the same region is not always meeting at the edge of their day. Record the call and post a written summary for anyone who could not attend.

Finding that overlap by hand is the fiddly bit, especially with half-hour offsets and daylight saving in play. Atlas shows each teammate's real local time on a map and highlights the window where everyone is comfortably awake, so you can pick a humane slot and write it straight to the calendar. The same overlap-finding approach scales up to a global all-hands across time zones when you need the whole company, not just the squad.

When there is no overlap at all

Some teams span a spread so wide that no waking hour is shared. Run the whole retro asynchronously. Keep the 24-hour collection board, then have the facilitator post a written summary of the themes, propose draft actions, and open a comment thread with a clear deadline for sign-off. A short recorded voice or video note from the facilitator adds warmth that plain text can lose. It is slower than a live call, but it keeps every voice equal and nobody loses sleep.

Protecting psychological safety

Distance and asynchrony can make people guard their words, so safety needs deliberate design. The retro exists to improve the system, not to grade people.

1. Anonymous or private input first. Reveal notes only after the window closes, so seniority and timing do not skew what gets said.
2. Discuss systems, not individuals. Set the norm openly, and have the facilitator reframe blame as a process gap whenever it surfaces.
3. Rotate the facilitator. It spreads ownership and stops one voice dominating every session.
4. Close the loop. Show last sprint's actions and what came of them. Nothing kills honesty faster than feedback that visibly goes nowhere.

Turning actions into something that sticks

End every retro, live or async, with a short, written list of actions: each with an owner and a due date. Post it where the team already works, not buried in the retro tool. Then open the next retro by reviewing it. That single habit, visibly acting on what people raise, does more for engagement than any clever format. For more on scheduling the wider rituals a distributed team runs, browse the Atlas blog.