You don't need another meeting. You need themes that survive the weekend and tickets that close. Here's what RetroSync gives an EM — and how a Friday actually plays out.
We talked to forty EMs running 2-week sprints. The list always comes back to the same four needs. The product is shaped around them; everything else is downstream.
What the retro actually looks like, beat by beat, with what the EM does (or doesn't do) at each step.
A scheduled MCP call pulls Sprint 24's incidents, merged PRs, and Sentry alerts. Eight notes land on the board with sources attached. Nobody is in the room yet.
Eight people, fifteen minutes. Notes are anonymous-by-phase. The board ends with twenty-two notes total — eight from Claude, fourteen from humans.
Five votes each. Three minutes. Top six notes get four votes or more; they cluster naturally into three themes.
The EM facilitates discussion at the theme level. The board displays each theme's contributing notes side-by-side; authorship is now attributed.
For each of the three themes, the Retro Coach drafts an action item with a suggested owner and due-by. The EM nudges two of them, accepts the third as-is.
One click. Three tickets created in the team's Linear project; cycle = next sprint; assignees notified. Retro closes; board archives.
Tuesday morning, the assignees pick up the work. Friction-to-PR time: 4 calendar days, including the weekend. (Sprint 23 average: 11 days.)
We resisted the temptation to ship twenty charts. The three below cover 90% of what an EM needs to know on a Friday afternoon.
I used to spend Sunday catching up on what Friday meant. Now Friday produces tickets, and Sunday is mine again.
Full catalogue is in § 5. These three carry 80% of what EMs end up running.
Start free, set up your team in five minutes, run your first retro this week.