Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Field app squad at Fieldnote, retro after the sprint that shipped the guided first-intervention flow, one week after the photo upload incident.
What the team took away
Three actions with owners: Friday merge freeze (Tom), Julien at review (Karim), one real technician in beta (Ana). Nothing else, on purpose.
How to run it
Preparation
The delivery team only. No manager unless they are part of the daily work.
Post last retro's three actions on the board before people arrive, with done or not done.
Three columns ready: Start, Stop, Continue. One sticky color per column, timer visible.
Agenda
5 min
Last actions Read the three actions from last time. Done or not. If not done twice, drop it and say so.
10 min
Silent writing Everyone writes stickies in the three columns, in silence. Minimum two per column. No reading others' notes yet.
15 min
Read and cluster Each person reads their stickies in one breath, no discussion. Cluster duplicates as you go.
5 min
Vote Three dots each. Vote only on Start and Stop. Continue is for morale, not for action.
20 min
Three actions Top three clusters become three actions. Each gets an owner and a check date before next retro. Write them in the team's channel now.
5 min
One word Close with one word per person on how the retro itself felt. Note anything that says 'useless' and change the format next time.
Pitfalls
Do not let a Continue sticky become an action. Actions come from Start and Stop; Continue is a thank-you.
Do not take five actions. Three with owners, or you will be reading five not-dones next time.
Do not let the loudest person read first. Start with whoever spoke least in the last sprint.
Afterwards
The three actions live in the team channel and open the next retro. If the same Stop appears three retros in a row, it is not a team problem: escalate it or run a Team Health Monitor.