Survey · Marketing
Retrospective survey template
Filled in privately before the meeting, so quieter people get heard and the discussion starts from real answers. It compares this period with the last one, asks for one concrete thing to try, and anyone who didn't feel safe raising problems gets a gentle follow-up question.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
Retro time. Answer on your own before we meet, so we can spend the meeting on what matters.
Which sprint, project or period is this for?
How did this stretch of work feel for you?
Did we deliver what we set out to do?
What went well that we should keep doing?
What slowed you down? Pick all that apply.
Pick the biggest thing that got in the way. What happened?
Compared with last time, how did we do on these?
What's one thing we should try next time?
How comfortable did you feel raising problems during this period?
What would make it easier to speak up? You can keep this general.
Anyone you'd like to thank for something specific?
Ends with
Thanks, see you at the retro 👋
The flow
Where each answer leads. Every route here is editable once the form is yours.
Short text
Opinion scale
Single select
Long text
Multi select
Long text
Matrix
Long text
Opinion scale
Long text
Long text
What this template uses
- Short text
- Opinion scale
- Single select
- Long text
- Multi select
- Matrix
- 2 branches
Questions to consider
- Will answers be anonymous? For a small team, say plainly who will read them and whether names are shown.
- Do you want to compare with last time? Keep the grid rows the same every retro so the trend means something.
- How long before the meeting should people answer, so the facilitator has time to group the replies?
- Did the team agree on actions last time? Consider adding a question about whether they happened.
How to use the responses
Before the meeting, group the slowed-down answers and the try-next ideas into themes, and bring the top two or three into the room rather than reading every reply. Use the comparison grid to show whether last retro's actions made a difference. If several people score low on speaking up, raise it carefully as a team topic, not an individual one, and agree on no more than two actions with a named owner each.
How to customize and share it
- 1Edit the slowed-down options to match the problems your team really runs into.
- 2Put the sprint or project name in the link as a hidden field, so the first question fills itself.
- 3Share the link a day before the retro and read the answers in the dashboard while you prepare.
Frequently asked questions
What questions should I ask in a retrospective?
What went well, what slowed you down, and what to try next are the core three. Comparing with the previous period and asking about psychological safety add useful depth.
Why run a retrospective survey before the meeting?
People answer more honestly on their own, and quieter team members get the same voice as the loudest. The meeting then starts with real input instead of a blank board.
Should retrospective feedback be anonymous?
It often helps, especially in teams where people are new or there's tension. Don't add a name question unless the team agrees to it.
Can I use this for project retrospectives, not just sprints?
Yes. The first question names the period, so it works for a sprint, a launch, a quarter or a whole project.