How to run a remote retrospective your team will actually follow through on
A retrospective is the meeting where a team looks back at the last stretch of work and decides what to change. Remote retros tend to go one of two ways: a quiet call where the same two people talk, or a lively one whose action items disappear by Wednesday.
The fix is less about the format and more about where the retro lives. Write before you talk, talk where the team already works, and leave the outcome in the channel.
The usual way
Most remote retros look something like this.
- A recurring video call. Everyone joins at the same time, cameras on, and someone shares a board.
- A separate board tool. Sticky notes go into an app nobody opens the rest of the sprint.
- Talking first, thinking later. The loudest takes set the agenda in the first five minutes.
- Action items in someone's notes. The facilitator types them up, sends them around, and they are never mentioned again.
The meeting itself is often fine. What goes missing is everything around it: the quiet people's input before the call and the follow-through after it.
A retro format that works remotely
A simple three-part structure holds up well across time zones and personalities.
1. Collect input in writing first
Open a thread in the team's channel a day or two before the retro with three prompts:
- What went well?
- What got in the way?
- What should we try next time?
People answer when they have a minute, in their own words. Teammates in other time zones get the same say as everyone else, and nobody has to think on the spot.
2. Talk it through, briefly
Spend twenty to thirty minutes on voice. Skip reading every answer aloud. Group the replies into a few themes, pick the two or three that matter most, and talk about those.
Keep cameras optional. A retro is a conversation, and audio is enough for it.
3. Leave with owners and days
Every change the team agrees to gets three things: what it is, who owns it, and when it will be checked. "Improve code review" is a wish. "Sam sets a two-reviewer rule on the main repo by Friday" is an action item.
Then post those items where the team will see them again, which is the channel the work happens in.
Retro prompts worth rotating
Asking the same three questions every time gets stale. A few alternatives:
- Start, stop, continue. What should we begin doing, quit doing, and keep doing?
- Most surprising thing. What happened that nobody planned for?
- One small change. If we could change one habit next sprint, what would it be?
- Last retro's items. Did the changes we agreed on last time happen, and did they help?
That last one is the most useful and the one teams skip most often. Opening each retro by checking the previous action items keeps them from piling up.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster, so a retro can live entirely inside the team's own channel.
The written round happens in a thread. Post the three prompts in the channel. Replies stay with the team's day-to-day messages, so anyone can read them before the call.
The talk happens in the channel's walk-in voice room. The room is already open beside the channel, so there is no link to send. People step in when the retro starts and step out when it ends.
Wren writes the notes. In a channel's walk-in voice room, Wren posts notes and action items back to that channel. The action items land in the same place as the written input, not in a separate doc.
Nix keeps the follow-up. Mention Nix in the thread where an owner promised something by a day, and the reminder arrives in that channel on the day. How to keep track of follow-ups in team chat covers the details.
Scout remembers last time. At the next retro, mention Scout and ask what the team agreed to change last sprint. Scout answers from what was actually said and links the message it came from.
If your team already uses a walk-in room for check-ins, Replace the status meeting with a walk-in room pairs well with this.
Try it at your next retro
Post the three prompts in your team's channel two days before the retro, and end the call by giving every action item an owner and a day.
Start free and run your next retro in the channel where the work already lives.