How to run a remote retrospective on an online whiteboard

The worst remote retrospectives sound like a status meeting. Someone shares a slide, asks "so, how did the sprint go?", and waits. The two most confident people answer. Everyone else nods into their camera. Forty minutes later there's a list of complaints in a doc and nobody's name next to any of them.

A shared whiteboard fixes part of this, because everyone can write at the same time. It doesn't fix the rest. Structure does that, and the structure is simple enough to run every sprint. Give each step a timebox, have people write before anyone talks, and leave with action items that each carry a name.

Here's the format we use, built on the four columns of our retrospective template. It fits in under an hour for a team of five to eight.

Prep the board the day before

Fifteen minutes of prep saves the first ten minutes of the meeting.

Open the retrospective template. It gives you four frames named Went well, To improve, Ideas and Action items, each with a few example stickies. Delete the examples, or keep one per column so people see the expected size of a note. If you'd rather start from a sentence, type something like "retro for a six-person web team after a sprint where staging broke twice" into the AI whiteboard and edit what it drafts.

Then add a fifth frame to the side called "Last time" and paste in the action items from your previous retro. That's your first agenda item, and it's the one most teams skip.

Send the share link a day early with the edit role. On Prompt Board, people who join through an edit link sign in, while viewers need no account at all. Sending it early means nobody spends the opening minutes creating a password.

One honest note on tooling. Prompt Board doesn't have a built-in timer or voting yet. For timing, use the timer on your phone and say the time out loud when you start each step. For voting, you'll use dots drawn by hand, which I'll explain below. Both work fine. Miro's paid plans and Mural have them built in, if you want a tool that enforces the clock for you.

The agenda

Here's how the hour breaks down:

1. Check in and review last time's actions, 5 minutes
2. Silent writing, 10 minutes
3. Read out and group, 15 minutes
4. Dot voting, 5 minutes
5. Action items with owners, 15 minutes
6. Close, 5 minutes

That adds up to 55 minutes, which leaves a few spare for the conversation that always runs long.

Start with what you promised last time

Go through the "Last time" frame item by item. Was it done? If not, why not? Keep it short and blame-free. A team that never checks its action items learns quickly that retros are theatre.

If an item failed twice, drop it or make it smaller. Carrying the same sticky from sprint to sprint helps nobody.

Silent writing comes before discussion

The first person to speak anchors the room. If the tech lead opens with "I think deploys were the big problem", half the board will be about deploys. So start a ten-minute timer and ask everyone to write in silence, straight onto the board.

Rules for the stickies:

• One thought per note.
• Facts beat verdicts. "Staging was down two days" is something the team can act on. "Infra is bad" isn't.
• Went well, To improve and Ideas are all fair game. Leave Action items empty for now.

Keeping Ideas separate from To improve matters more than it looks. A complaint and a proposal are different things, and mixing them makes the grouping step harder.

Live cursors show who's writing, so you can tell if someone hasn't started. A private nudge in chat works better than calling them out.

Read out, then group

Go round the team. Each person reads their stickies aloud in a minute or so. Only clarifying questions are allowed at this stage. Debate comes later.

Then group. Drag duplicates and near-duplicates together until each cluster is one topic. With twenty stickies this takes a couple of minutes by hand. With fifty it's tedious, and that's where AI clustering earns its keep. Select the stickies in To improve, ask the AI whiteboard to cluster them, and it sorts them into themed frames. Treat the result as a draft. Rename frames that are too vague, and move any sticky that landed in the wrong place. The team should agree on the groups, not the model.

Vote with dots you draw yourself

Give everyone three votes. Each person puts a dot on the clusters they most want to fix, either drawn with the pen tool or as a tiny sticky in their colour. Stacking two dots on one cluster is allowed.

This is low-tech and it works. It isn't anonymous, though. Everyone can see who voted where, and in some teams that nudges people toward the senior person's choice. If that's a problem for your team, have everyone place their dots at the same moment when you say "go", so nobody waits to see where the lead voted.

Count the dots and take the top two clusters. Three at most. A team that commits to six fixes usually finishes none.

Turn the top clusters into action items

This is the part that decides whether the retro was worth an hour. Every action item needs a named owner, a date, and a size you can finish before the next retro.

Compare these:

• Weak: "Improve communication."
• Better: "Tom: add an acceptance-criteria checklist to the ticket template by Thursday."

The template's examples follow the same pattern, such as "Mia: fix staging alerts by Tue". "Team" is acceptable as an owner only for experiments everyone runs together, like trying an async standup for two weeks.

Write each action item as a sticky in the Action items frame while the team watches. If nobody volunteers to own something, that tells you it isn't a priority, and it shouldn't go on the board.

Close the meeting and follow up

Spend the last few minutes on a quick round. One word on how the sprint felt is enough.

After the call, select the stickies in Action items and use the AI summarise action to turn them into a single sticky you can paste into Slack. You can also export the board as PNG and attach it to the sprint ticket. If someone needs to follow up on a point asynchronously, pin a comment thread next to the sticky and resolve it when it's done.

Before the next retro, duplicate this board from your dashboard, clear the four columns and move the action items into "Last time". That way every retro opens with the promises from the last one.

When the format gets stale

Running the same four columns every two weeks gets dull after a few months. Change the prompts now and then. Try "What slowed you down?" instead of "To improve", or run a start, stop, continue retro for one sprint. Our guide to retrospective formats compares six options and when each one fits. The AI can draft the variant from one sentence, and the parts that matter stay the same. People still write in silence first, and every action item still leaves with an owner.

A remote retro rarely fails because of the software. It fails when people talk before they write and leave without owners. Get those two right and a phone timer and some hand-drawn dots will carry the rest. Start with the retrospective template and run it at the end of your next sprint.