# Async Retro in a Shared Doc: Format, Deadline, Follow-Through

> A practical guide to running async retrospectives in a shared document: format, deadline, and follow-through rules for teams that want improvement without more meetings.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-28
- Updated: 2026-10-28
- Source: https://aiadvisoryboard.me/blog/async-retro-shared-doc-format-deadline-follow-through

After watching 30+ founders try to fix team alignment, my conclusion is this: the retrospective that never happens is worse than no retrospective at all.

## TL;DR
- Run the async retro in one shared doc with three sections: what worked, what didn't, and what we change next week.
- Set a hard deadline: comments close Friday at 3 PM local time.
- Assign one owner per action item with a due date; otherwise the retro is theater.

### Definition: Async retrospective
A team reflection held asynchronously in a shared document instead of a live meeting. Participants add comments over a set window, then the team converts insights into owned action items.

### Definition: Follow-through
The practice of assigning every retro insight to a specific person with a deadline, and checking status in the next cycle. Without it, the doc becomes a graveyard of good intentions.

## Why async retros fit companies of 30-500
At this size, pulling everyone into a room for an hour kills productive time. Time zones, deep-work blocks, and client calls make sync retros hard to schedule. A shared doc lets people contribute when they can think clearly, not when the calendar forces them.

But async has a failure mode: people write comments, nobody converts them into work, and the next retro repeats the same complaints. The fix is structure, not more meetings.

## What to include in the shared doc
Use one document per retro cycle. Keep it to three sections so the format never bloats.

1. **What worked** — wins, smooth handoffs, things to keep doing.
2. **What didn't work** — blockers, missed deadlines, friction points.
3. **What we change** — specific experiments for the next cycle, each with an owner and due date.

Add a fourth section only if you need it: **Open questions** for decisions that require leadership input. Do not use this section for general venting.

### Copy/paste template
```markdown
# Team Retro — Week of [Date]

## What worked
- 

## What didn't work
- 

## What we change next week
| Item | Owner | Due |
|------|-------|-----|
|      |       |     |

## Open questions (needs leadership)
- 
```

## Setting the deadline that actually works
A deadline is not a suggestion. It is the forcing function that turns a document into a decision.

For most teams, a Friday 3 PM local deadline works best. It captures the week while it is fresh, but gives people Thursday to finish deep work. Comments close at the deadline. No late entries. If someone misses it, their input goes into the next cycle.

The retro lead reads all comments by end of day Friday, clusters duplicates, and assigns action items by Monday morning.

## Follow-through: from comment to action
This is where most async retros die. A comment with ten upvotes is not an action item. An action item has three fields:

- **What** — the specific change or experiment.
- **Who** — one named owner, not "the team."
- **When** — a date, not "soon."

Review open action items at the start of the next retro. If an item carried over twice without progress, either re-scope it or kill it. Do not let zombie items accumulate.

## Manager scan (2-minute digest example)
- Retro doc opened Monday, comments due Friday 3 PM.
- 12 comments clustered into 4 themes.
- 3 action items assigned, each with an owner and due date.
- 2 items from last retro carried over; 1 killed after no progress.

> **Tool tip (AiAdvisoryBoard.me):** A shared doc works best when leadership can see the gap between what the team planned to improve and what actually changed. That is the Plan → Fact → Gap rhythm: plan the retro actions, check the fact of completion, and close the gap before the next cycle. See how the 7-day diagnostic surfaces that visibility for your company.

## Micro-case (what changes after 7-14 days)
A 90-person professional services team ran their first async retro in a shared doc. In week one, comments were vague and no owners were assigned. By week two, the retro lead enforced the three-field rule: what, who, when. The founder stopped hearing the same complaints about client handoffs because one action item had a named owner and a due date. Visibility into team friction improved without adding a single meeting to the calendar.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30-500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ
**How long should the comment window stay open?**
Three to four business days. Any longer and momentum dies; any shorter and people in other time zones miss it.

**Who owns the doc?**
One rotating retro lead, usually a team lead or ops person. They set the deadline, cluster comments, and assign action items.

**What if nobody comments?**
That is a signal, not a success. Either the team does not feel safe being honest, or they do not believe anything will change. Address the culture before you fix the format.

**Can we use this for a remote-first team?**
Yes. Async retros are ideal for distributed teams because they remove the time-zone penalty of live meetings.

**How is this different from a daily standup?**
A standup tracks today's work. A retro looks back at a cycle and decides what to change next time. They serve different purposes.

Done well, an async retro in a shared doc becomes the team's operating rhythm for improvement. The format is simple. The deadline is non-negotiable. The follow-through is what makes it real.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.
https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/async-retro-shared-doc-format-deadline-follow-through. More articles: https://aiadvisoryboard.me/blog