Retros that spend the time on what matters

Ask how the sprint felt, what went well and what to change. Collect answers before the meeting and start the retro with all of it.

Collect answers before the meeting, anonymously if you like.

The team ranks the actions, and the order settles on screen.

Answers in before the meeting

The team retrospective asks how the sprint felt, what went well and what to change. Everyone answers in their own time, and the meeting starts with the full picture.

  • A rating plus open questions
  • Answers before the meeting
  • Show them on screen together
The Team retrospective template asking how the sprint felt

Honest because it’s anonymous

Leave out names and keep respondent names private. A browser session check is enough for a friendly team, or use unique codes when it needs to be strict.

  • No names asked
  • One answer per person
  • Private results and comments

Commit to what the team ranks first

After the discussion, everyone ranks the proposed actions. The shared order shows what to do next, and nobody argues about whose idea it was.

  • Rank the action items
  • A shared order everyone sees
  • Repeat every sprint

Good to know

Better retrospectives with async input

Why collecting answers before the meeting changes the retro, which questions to ask, how to keep it honest and how to reuse it every sprint.

2 min read

Why async input works

In a classic retro, half the meeting goes to writing sticky notes, and the first idea shared shapes everything after it. When everyone answers a day ahead, in their own time, you start the meeting with the full picture. Quiet team members get the same weight as the confident ones, and the hour is spent on what to change.

Questions that lead somewhere

  • A Rating: “How did this sprint feel?” Track it over time.
  • What went well that we should keep doing?
  • What got in the way that we should change?
  • One idea to try next sprint.

With conditional logic, ask “What would have helped?” only after a low rating. Happy weeks stay short.

Keep it honest

Leave out names and keep Show respondent names private. Browser session is enough for a team that trusts each other; use unique codes when it needs to be strict. Set Access to results to Only you if you want to read first and present a summary.

Run the meeting

  1. 1 Close the poll an hour before the retro.
  2. 2 Walk through the answers in present mode.
  3. 3 Group similar points and discuss the biggest themes.
  4. 4 Collect proposed actions, then let everyone rank them.
  5. 5 Commit to the top two, with an owner each.

Every sprint, without the setup

Choose Save as template, and next sprint the retro is under Templates when you start a new poll. Or keep one poll, export the answers as a CSV and reset it. Connect Slack to see responses in your team channel as they come in.

Questions people ask

Team retrospectives

Next retro, start with the answers

Send the retrospective today and walk into the meeting knowing what to fix.

Team retrospective 3 questions · ~2 min