How to run a remote retro with online sticky notes (the free way)

Most retro tools want a per-seat subscription before your team has even agreed what "retro" means. You don't need it. A free online sticky-notes board, a 30-minute calendar block, and a half-decent facilitator is the entire stack. Here's the exact playbook.

Why bother with a "tool" at all?

Retros fail in two ways: nobody talks, or one person dominates. The cure for both is the same — make people write before they talk. Sticky notes do this because everyone's brain warms up while their hand is moving, and the notes are visible to the room without anyone having to "go first" out loud.

You can do this with physical post-its on a wall. Or with Miro and 14 days of free trial anxiety. Or with a free online sticky-notes board that opens in any browser and saves to its URL. We're going to use the last one.

The 4-step retro that fits in 30 minutes

1. Pre-load the board (2 minutes, the facilitator alone)

Open the retrospective sticky-notes board, click Templates, and pick "Retrospective." You'll get three header notes — KEEP, CHANGE, START — already laid out as columns. (Use any three-column framework you like: Liked/Learned/Lacked, Mad/Sad/Glad, Stop/Start/Continue. The shapes are interchangeable.)

Copy the share link. Drop it in the meeting invite or the call's chat.

2. Silent dump (8 minutes, everyone at once)

Set a visible timer. This is the most important part of the retro. Everyone — including the facilitator — adds one note per thought, anywhere on the board, color-coded by category (the default eight colors are plenty). No talking, no reactions, no clarifying questions. Just put it down.

Common facilitator mistakes here:

• Talking. Don't. Even encouraging people to "really go for it" steals their thinking time. Read your phone if you need to.
• Letting it run long. Eight minutes is enough. People will write the obvious things in the first four minutes and the real things in the next four. After eight, you're forcing depth that wasn't there.
• Combining notes during the dump. Save it for step 3.

3. Cluster & share (10 minutes, everyone)

Now talk. Each person reads their notes out loud and drags them into the right column. If two notes are clearly the same idea, drag them together and recolor them the same color. Don't merge — recolor. Future-you wants to see who agreed on what.

The facilitator's job is to keep this moving. If a discussion starts to bleed into solutioning, defer it: "That's a great thread — let's note it for step 4."

4. Pick one thing & commit (10 minutes, the team)

Look at the START column. Pick exactly one thing to try next sprint. Not three. Not "a few quick wins." One. Add a fresh note next to it with a name attached: @maria will draft the new PR template by Friday.

This is the bit that fails 90% of retros: people leave with a vibe of consensus and no one owns the change. Owning means name + date, written on the board, exported to the artifact.

The artifact: what you walk away with

Click Export → PNG. You now have a board snapshot you can drop into Confluence / Notion / your team wiki / the retro folder in Drive. Two reasons to do this every time:

1. Memory. The next retro starts by reviewing the last one's action item. Without an artifact, "we said we'd do that" turns into "did we?"
2. Pattern recognition. Three retros in a row with the same "CHANGE" item is a signal. You won't see the signal without the artifacts.

For paying customers, the board also lives in version history — 50 snapshots, restorable with one click — so you can diff sprint 14's retro against sprint 13's without leaving the tool.

What's actually wrong with Miro / FigJam for this

Nothing — they're excellent tools. The problem is they're designed for the 2-hour facilitated workshop. A retro is a 30-minute meeting. The setup overhead (creating boards, inviting members, learning where things live, hitting feature paywalls) costs more than the meeting itself. For sprint retros, a zero-onboarding tool wins every time.

Where the big tools earn their fee: design jams, customer-journey workshops, anything that's going to be revisited and grown over weeks. For those, pay them. For your weekly retro, don't.

One more thing: async retros

If your team is distributed across time zones, the live retro doesn't work anyway. Share the board link a day before the "meeting," let people dump their notes whenever they're awake, and reserve the synchronous time for steps 3 and 4 only. The dump-then-discuss pattern works just as well async; you just buy back the dump time.

Open the retrospective sticky-notes board →

Related tools

• Online sticky notes board — the canonical tool, with all templates available
• Brainstorming board — wider canvas, more colors
• Daily standup board — three-column standup template
• Quick Notes for meeting notes — markdown-based, for capturing decisions instead of cards
• Pomodoro timer — runs the 8-minute silent dump for you

← Back to all posts