The retro ends at 11:47am. Someone says "I'll post a summary to the channel." By 1pm, three stand-up threads and a deploy notification have pushed it off the screen. The summary never arrives. The action items exist only in the heads of the eight people who were in the room.
That's the real follow-through problem - not the retro format, not the tool, not team buy-in. It's the 12-minute window between "meeting ends" and "channel has moved on."
Why the Slack post matters more than the retro tool
The summary message isn't a nicety. It's the accountability mechanism. When an action item lives only in Miro, FigJam, or a retro board, its audience is capped at attendees. When it lands in #eng or #product with a person's name on it, the whole team becomes a passive witness - and that social pressure is measurable.
Across hundreds of thousands of action items tracked in TeamRetro, about 73% were eventually completed. About half are done within three months, and about a quarter before the team's next retro. The factor that moves the number most is assignment: an action with a named owner and a due date completes about 90% of the time.
The gap between 67% (unowned) and 90% (owned-and-dated) is enormous for something that costs nothing to fix. But here's the catch: only about 40% of actions get an owner at all. The Slack post is where that assignment either happens publicly or gets quietly dropped.
What actually goes wrong in the 12-minute window
Most retrospectives don't fail during the session itself; they falter in the days and weeks afterward. According to a poll in PMI's community, nearly two-thirds of respondents implemented fewer than 25% of the ideas from their retros - none reported implementing more than 75%.
The structural failure is almost always the same:
- The retro tool (Parabol, TeamRetro, FigJam sticky notes) has the outcomes, but the team's operating channel does not.
- The person nominated to "write it up" is already in the next meeting.
- The summary, when it finally appears hours later, is a wall of text with no owners, no due dates, and no threading - so it reads like a status update instead of a commitment.
Even well-written action items disappear when there's no system for tracking them. They live in meeting notes that nobody opens, or on a whiteboard that gets erased.
The fix is not a new process. It's doing the existing step faster and in a structured format.
The four-line Slack summary format that actually works
A good retro summary in Slack does four specific things and nothing else:
- States the sprint (Sprint 42, or the date range) so the message is searchable later.
- Lists only the committed actions - not everything discussed, just what was decided.
- Tags one owner per item with a target date. Not "the team." One person.
- Links back to the full retro board for anyone who wants context.
That's it. Four elements. The whole message is under ten lines. Anything longer and people stop reading at item three.
Here's the shape: