Retrospective Prompt Generator

Overview

A great retrospective lives or dies by the quality of its prompts. Ask "what went well?" for the fifteenth sprint running and you will get the same polite, surface-level answers. Ask something specific, surprising, or genuinely curious and the team starts to think differently about the work they have just completed.

This generator creates tailored prompts for nine popular retro formats, adapting the tone to match your team's current mood and the complexity of the period you are reflecting on. Each set includes a warm-up question, format-specific discussion prompts, facilitator instructions, a timing guide scaled to your team size, and a closing commitment prompt.

All prompts run entirely in your browser. Nothing is stored or sent to a server.

Generator

How It Works

The generator combines four inputs to produce a tailored set of retrospective prompts:

• Retro format determines the categories and structure. Each format has its own bank of prompts grouped by category, so a Sailboat retro produces Wind, Anchor, Rocks, and Island prompts while a 4Ls retro produces Liked, Learned, Lacked, and Longed for.
• Team mood adjusts the tone and framing. For a frustrated team, prompts lean towards acknowledgement and constructive forward-looking language. For a celebratory team, prompts encourage savouring wins and capturing what made them possible.
• Sprint/period focus is woven into prompts when provided, making them feel specific rather than generic. If you leave this blank the prompts remain universal.
• Team size drives the timing guide. Larger teams need more structured facilitation, breakout time, and report-back windows.

Each generation randomly selects from a pool of prompts per category, so hitting Regenerate gives you a fresh set every time.

Example Output

Best Practices

Running a retrospective well requires more than good prompts. Keep these principles in mind to get the most from every session.

• Rotate your format regularly. Using the same retro format every sprint leads to stale conversations. Alternate between two or three formats to keep the team thinking from different angles.
• Set the stage before diving in. Spend two to three minutes on a warm-up question. It lowers the barrier to speaking up and gives quieter team members an easy first contribution.
• Use silent writing before group discussion. Give everyone three to five minutes to write their thoughts individually before sharing. This prevents groupthink and ensures introverts have equal input.
• Timebox each section. Without timeboxes, teams spend 80% of the retro on what went wrong and rush through action items. Use the timing guide this tool provides and stick to it.
• Limit action items to three. A retrospective that produces ten action items will deliver on none of them. Pick the three most impactful changes and assign clear owners.
• Follow up on previous actions. Start each retro by reviewing the actions from last time. If the team keeps carrying the same items forward, discuss why they are stuck rather than adding new ones.
• Create psychological safety. Remind the team at the start that the retro is a blame-free zone. What matters is improving the system, not pointing fingers at individuals.
• Vary the facilitator. Rotating who runs the retro builds shared ownership of the team's improvement process and brings fresh facilitation styles into the room.

Common Mistakes

• Skipping the retro when things are going well. Good sprints are the best time to reflect because you can identify what to protect and repeat, not just what to fix.
• Letting one voice dominate. If the same person always speaks first or longest, use round-robin or written-first techniques to balance participation.
• Treating the retro as a venting session. Frustration is valid, but a retro that stays in problem space without moving to solution space leaves the team feeling worse. Allocate at least a third of the time to forward-looking actions.
• Never changing the format. Repeating the same format for months trains the team to give the same answers. Switch it up, even if the team says they are comfortable with the current one.
• Producing actions with no owner. "We should improve our testing" is a wish, not an action. Every item needs a named owner and a clear next step.
• Running retros that are too long. For most teams, 60 to 90 minutes is the sweet spot. Going beyond that leads to fatigue and diminishing returns on the quality of discussion.
• Ignoring remote participants. In hybrid retros, people on a video call are easily overlooked. Use digital boards so everyone contributes equally, and actively invite remote voices into the conversation.

Related Tools

Related Templates