THE IDEA TO TAKE WITH YOU
An asynchronous retro needs more than an open board. Give each phase a clear deadline, allow every time zone a working-day opportunity and write down how the final decision will be made.
Separate writing from deciding
In an asynchronous retrospective, participants contribute at different times instead of doing everything in one call. This can suit teams whose normal working hours overlap poorly, but it still needs a facilitator and a defined finish.
Separate the stages of reflection, clarification and decision-making. If one person starts choosing actions while another is still writing their first note, the later participant has less opportunity to shape the conversation. A visible schedule makes the order clear.
Plan the contribution windows
Build the schedule around the team’s actual working days, including leave and local holidays. Use an explicit time zone for every deadline. The example below is a sequence to adapt, not a requirement to finish in a particular number of hours.
| Phase | Facilitator’s job | Participant’s job |
|---|---|---|
| Before opening | Share the scope, prompts, access rules and deadlines. | Check access and flag an unavailable working day. |
| Reflection window | Keep the prompts stable and answer access questions. | Write specific observations independently. |
| Clarification window | Reveal notes if needed and propose theme groupings. | Read all perspectives and clarify meanings. |
| Decision window | Present a small set of options and a decision method. | State a preference, concern or proposed adjustment. |
| Close and review | Record the action, owner and review date. | Confirm the next step and revisit the outcome. |
Give written notes enough context
A note needs to make sense to someone who reads it hours later. Use a short structure: what happened, what effect it had and what question you want to explore. “The release note arrived after the support handover, so we answered questions without it” is easier to discuss than “Bad communication.”
Avoid expecting readers to infer tone. Ask a clarifying question before treating a brief note as criticism. If the exchange becomes confusing or sensitive, arrange a smaller conversation with the people involved and bring back an agreed summary where appropriate.
Use Retro for the shared record
Share the board link and let teammates add reflections during the agreed window. A facilitator can use private reflection before revealing notes together. Shared notes retain authorship, and the participant link provides board access; neither feature is a confidential reporting channel.
Use groups to collect themes and votes to guide priorities after everyone has had a chance to read. Keep facilitation questions and deadline reminders in an agreed team communication channel if needed. The facilitator manages the schedule; this workflow does not rely on Retro automatically advancing asynchronous phases or sending reminders.
Where an overlap window exists, a short live discussion can help resolve a specific open question. Share the question in advance and leave a written summary for anyone who cannot join.
Close the loop in writing
State how the decision will be made before collecting preferences. For example, the team might agree on one experiment after checking for objections. Silence from someone whose working day has not started is not agreement.
Publish a concise outcome: the observation, the change to try, its owner and the review date. Record unresolved concerns rather than presenting the result as unanimous when it was not. Give the owner a chance to confirm their capacity.
Revisit the experiment at the next retrospective. Also review the asynchronous process: did everyone get a fair contribution window, and did the written discussion create enough shared understanding? Adjust the next schedule based on those answers.
Keep the conversation going. Explore Retro’s meeting tools or find a plan for your team.
