How to Run a Remote Retro in FigJam Without Losing the Room
Short answer: A FigJam retro works best in 45 minutes: 8 minutes silent writing, 10 minutes clustering, 15 minutes discussion on the top three clusters only, 7 minutes on actions with named owners, 5 minutes for the closing dot vote. Anything longer and attendance rots.
I have run this structure about 30 times with teams of five to nine. The first three attempts were bad, and the mistakes were consistent enough to write down.
How do you set up the board before anyone joins?
Build it once and reuse it. A retro board in FigJam needs less than you think: three columns, a parking lot section, an actions section with an owner field, and a dot-vote area.
Four setup decisions that save trouble:
- Turn off anonymous cursors for the writing phase. You want to see who is where, so quiet people are visible.
- One sticky colour per person. FigJam assigns a colour per author by default. Set it deliberately: it makes clustering honest, because you can see when one person wrote 14 of the 30 notes.
- Lock the template sections. Select a section and lock it so nobody drags the frame by accident. This happens in every second session.
- Put the timer on the canvas, not on your face. A FigJam timer widget is visible to everyone and stops the “are we still writing?” question.
Share the link before the meeting with one line: “Board is open, writing starts at the top of the hour.” People who pre-read write better notes.
What does the 45-minute agenda look like?
| Phase | Minutes | Facilitator move |
|---|---|---|
| Silent writing | 8 | Say nothing. Do not answer questions about wording. |
| Clustering | 10 | Two volunteers drag, everyone watches. AI grouping optional. |
| Discussion | 15 | Only the top 3 clusters by dot count. |
| Actions | 7 | Each action gets a name and a date. |
| Close | 5 | One sentence each, out loud. |
The clustering phase is where remote retros die. If everyone drags simultaneously the board becomes a fight. Nominate two people to move stickies and let the rest read. AI clustering can do a first pass — it is decent with homogeneous notes and merges things that share a word, so plan to correct three or four groups by hand.
Why do silent stickies produce better input?
Because writing in a shared doc while a call is happening is a performance, not a thought. The 8-minute silent phase removes the performance. Cameras can stay off; I have never seen quality drop because people turned cameras off during writing.
The failure case for silence is when the team is new to each other. Silence in a group that does not yet trust each other just means nobody writes. In that case cut it to 4 minutes and add a warm-up prompt with an easy answer — “one thing that worked this week” — before the harder columns.
How many clusters should you discuss?
Three, plus a parking lot. This is the single biggest improvement I made. With six clusters and eight people you get 45 seconds per topic and everyone leaves feeling unheard.
Dot voting before discussion decides which three. Give each person three dots, no stacking more than two on one cluster, and be explicit about the rule before voting starts. Then say out loud: “We are discussing three. Everything else goes to the parking lot and gets an owner review next week.”
That sentence prevents the most common retro ending, which is a list of 11 concerns and no decisions.
What makes actions stick?
Two fields. Owner, and date. A retro action without both is a wish.
In FigJam, put the actions in a table-shaped section with three columns: action, owner, date. When the session ends, screenshot that section and paste it into your tracker. The screenshot is not the record — the tracker is — but people trust the screenshot more because it is the one they watched get filled in.
Also worth doing: cap actions at three per retro. Teams that generate nine actions complete about two. Teams capped at three complete about two as well, and spend less time on the list.
What does FigJam charge for this?
FigJam is free for up to three files on Figma’s Starter plan, which is enough for a monthly retro if you reuse one file. Paid plans start at Professional, $16 per editor per month billed annually, and that is where AI features and unlimited files live.
For a facilitator running retros across several teams, one Professional seat for the facilitator and free view access for participants is the cheap configuration. Participants do not need edit seats to add stickies on a shared file in most setups, but check this before you plan a session with 12 people.
Who this structure fits
It fits teams of five to nine that meet every two weeks, where at least one person will hold the timer. It works with cameras off and distributed time zones, as long as everyone can be in one 45-minute window.
It does not fit a team of two or three — the overhead is bigger than the value, and a 15-minute call beats any board. It also does not fit a first retro after a serious incident; that needs an incident review with a written timeline, not sticky notes about feelings.
Quick Summary
- 45 minutes: 8 writing, 10 clustering, 15 on three clusters, 7 on actions, 5 to close.
- Nominate two people to move stickies; simultaneous dragging turns the board into a fight.
- Dot-vote with three dots first, then announce that only three clusters get discussed.
- Cap actions at three, each with an owner and a date, or nothing ships.
- FigJam Starter allows three files free; AI clustering needs Professional at $16/editor/month.
