Design a retrospective that is not a formality
Builds questions grounded in what actually happened this period, plus an order that gets quiet people talking.
| Category | Office work › Meetings |
|---|---|
| Tags | Question generationAnalyzingOffice worker |
Design a retrospective session. Produce: 1. Six questions derived from what actually happened. Each must reference a specific event, not a general theme. 2. Run order, with a time box per question and a note on which ones need silent writing first so the loudest voice does not set the frame. 3. For each question, the follow-up to use if the room goes quiet. 4. Two questions that surface things people avoid saying in front of a manager, and how to ask them safely. 5. A closing step that produces commitments rather than observations. Rules: - *No leading questions.* "Why did the deployment go badly" presumes the answer; "what happened around the deployment" does not. - Ban "what went well / what went badly" as a frame. It produces the same answers every time. - Work only from the events I gave you. If they are too thin for six questions, say how many you can support and what else to collect first.
After pasting, fill in the fields at the bottom (Period · Participants · What happened)
What this prompt does
Retros go flat because the questions are generic. This derives them from the period’s actual events and sequences the session so discussion does not concentrate on the loudest people. Leading questions are banned so the facilitator does not pre-decide the outcome.
More in this category
| Brief someone who missed the meeting | |
| Write the follow-up email after a meeting | |
| Turn minutes into a chat message | |
| Split a meeting outcome by recipient | |
| Créer une Carte Mentale pour Séance d'Idéation |