The problem
Sprint retros are supposed to generate change. They rarely do. The board fills up with sticky notes — What went well, What didn't, Try next — and then the Scrum Master takes a photo on their phone. That photo lives in Slack for a week and then vanishes. Nobody can read the handwriting in column three. The action items that were supposed to ship in the next sprint never get assigned.
Digital tools like FigJam and Miro fix the photo problem but create a different one: remote participants type faster than in-person participants think, the board becomes a wall of text, and you still have to manually scrape the output into a ticket or a doc. Someone has to do that work. Nobody wants to.
The real cost isn't the meeting. It's the twenty minutes of cleanup after the meeting — and the compounding cost of action items that never made it out of the retro board into the sprint backlog.