Retrospective actions that don't get lost

A retrospective is only worth the time if something changes afterwards. The usual problem is not the discussion: it is what happens in the following days. The actions are written on a board, retyped into a task tool by someone who remembers, and a few of them quietly disappear before the next sprint.

Why actions get lost

• They live in the wrong place. A whiteboard is great during the meeting and useless a week later.
• Retyping is a chore, so it is skipped. The person who has to copy the actions somewhere else is the one with the least time.
• Nobody owns them. "We should improve code reviews" is a wish; "Ana will propose a review window by Friday" is an action.

A board with three zones

Keep the structure simple: Went well, To improve and Action items. Everyone adds sticky notes during the sprint, not only in the meeting, so the important points are written down when they happen and nothing is forgotten when the retro arrives.

Two habits make the discussion better:

• Keep other people's notes hidden until you reveal them. When notes stay private, each person writes what they really think instead of reacting to what is already on the wall.
• Connect each improvement to its action. Drawing an arrow from the problem to the action keeps the "why" attached to the "what".

Write the action once

When the retro ends, every note in Action items becomes a tracked item for the whole team: you give it a status (open, in progress or done), an owner and a due date. It stays in one place, next to the retro it came from, with a count of what is still open and what is overdue.

There is nothing to copy into another tool, which removes the step where actions usually get lost.

Start the next retro with the last one

Before collecting new notes, spend two minutes on the actions from last time. Which are done? Which are stuck, and why? Teams that do this notice something quickly: fewer, smaller, more specific actions get finished, and the retros stop repeating themselves.

One action with an owner and a date beats five good intentions.

Quick checklist

• Add notes during the sprint, not only in the meeting.
• Reveal the notes together, then discuss.
• Turn each improvement into one concrete action.
• Give every action an owner and a date.
• Open the next retro with the status of the last one.