Business
Retrospective Prompt Generator
The retrospective prompt generator produces discussion questions from a pool of ten, sampling without replacement. The count input (3–14) controls how many you receive per run. The prompts span went well, slowed us down, what to start and stop, surprises, communication, learnings, risks, and pride — giving a team concrete things to respond to rather than an open "how did the sprint go?" Agile teams use them to run start/stop/continue and went-well/slowed-us-down retrospectives without the same three questions every fortnight. Managers running project post-mortems use them to structure reflection across a delivery. Generate a set, work through four to six with the team, and close with one or two specific actions you will actually do next sprint.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many prompts you want.
- Click Generate to produce retrospective prompts.
- Work through a few as a team.
- Capture one or two concrete action items.
Use Cases
- •Running an agile sprint retrospective
- •A project post-mortem or wrap-up
- •Getting past awkward retro silences
- •Structuring a team improvement session
- •Turning reflection into concrete action items
Tips
- →Make it safe to be honest — no blame.
- →End with specific actions, not a long wishlist.
- →Rotate who facilitates to keep it fresh.
- →Revisit last retro's actions before starting.
FAQ
What is a retrospective and when should you run one?
A retrospective is a team meeting where you reflect on how recent work went and decide what to improve. In agile, it follows each sprint; for projects, it happens at key milestones or at the end of a delivery. The focus is on the team's process, not individual performance.
What prompts are in the pool?
The ten prompts cover: what went well, what slowed the team down, what to start and stop, surprises, communication breakdown points, learnings to share, what to change if the sprint ran again, what the team is proud of, and risks carried into the next sprint. A count of 6 samples six distinct prompts from this set.
How do I run a retro that ends with real actions?
Work through the prompts, capture every answer without judgment, then vote or discuss to identify one or two recurring themes. Convert each theme into a concrete, owned action item — not a vague aspiration. Revisit last sprint's actions at the start of the next retro to close the loop.
How is this different from a SWOT analysis?
A retrospective looks backward at a specific sprint or project — what happened, what to improve. A SWOT looks at the business or product from a strategic angle across internal and external factors. Retro prompts are team-process focused; SWOT prompts are business-position focused.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.