Sprint retrospective poll for Slack

Keep it to three or four questions. The classic set works because each one asks for a different thing:

• How did the sprint go? A 1 to 5 rating. It gives you a number you can compare sprint to sprint.
• What went well? Free text. Name the sprint so answers stay specific.
• What didn't? Free text. Ask about the work, not about people.
• What should we try next sprint? Free text, optional. Not everyone has an idea every time, and a required box gets filler.

Make the whole retro anonymous. A retro is feedback, and named feedback on a bad sprint gets polite answers.

Post it the morning of the last sprint day and close after 1 day or close after 2 days (Premium), so it closes before the retro meeting. Closing it matters: answers settle, and nobody adds a late comment while you are presenting.

If the team is spread across time zones, add remind 2 hours before closing (Premium) so the late half of the team sees it again.

Read every answer, group them into a handful of themes, and count them. Bring the themes to the meeting, with one or two answers quoted word for word. Don't try to work out who wrote what. If people suspect you do, the next retro will be empty.

End with a decision. Take the top three suggestions and run a ranked vote so the team picks one change to try. One change that sticks beats five that don't.

Collecting the same feedback every sprint and never acting on it. If "too many meetings" tops the list three sprints running, the retro has stopped working. Open the next poll's description with what you changed since the last one.