Retrospective Meeting Facilitator
Facilitate effective team retrospectives that surface real issues, celebrate wins, and produce concrete action items — with multiple format options beyond the basic 'what went well / what didn't' template.
Prompt Template
You are an experienced agile coach and team facilitator. Help me plan and run an effective retrospective meeting. Team context: - Team size: [number of participants] - Team type: [engineering / product / cross-functional / marketing / operations] - Sprint/cycle length: [1 week / 2 weeks / monthly / quarterly] - What happened this cycle: [brief summary — shipped a feature, missed a deadline, had a production incident, onboarded new members, etc.] - Team mood/energy: [high / neutral / low / tense / mixed] - Retrospective maturity: [first retro ever / team does retros but they feel stale / experienced with retros] - Recurring issues: [any themes that keep coming up — e.g., unclear requirements, deployment problems, communication gaps] - Meeting length: [30 / 45 / 60 / 90 minutes] - Format: [in-person / remote / hybrid] Please create: 1. **Retro Format Recommendation** — Suggest the best retrospective format for this team's current situation. Choose from or adapt: - Start/Stop/Continue - 4Ls (Liked, Learned, Lacked, Longed For) - Sailboat (wind = what propels us, anchor = what holds us back, rocks = risks) - Mad/Sad/Glad - Timeline retro (walk through the sprint chronologically) - Explain why this format fits the current context 2. **Detailed Facilitation Guide** — Minute-by-minute agenda: - Opening: Icebreaker or check-in activity (2-3 min) - Data gathering: How to collect input (silent writing, digital board, round-robin) - Grouping & voting: Cluster themes and prioritize - Discussion: Deep-dive into top 2-3 themes - Action items: Convert insights into specific, owned, time-bound commitments - Closing: End on an energizing note 3. **Facilitation Tips** — Specific techniques for: - Getting quiet team members to participate - Preventing one person from dominating - Handling blame or finger-pointing - Keeping the conversation constructive when morale is low - Following up on action items from previous retros 4. **Action Item Template** — A structured format for capturing commitments: - What specifically will change - Who owns it - By when - How we'll know it worked 5. **Anti-Patterns to Avoid** — Common retrospective mistakes that make teams dread retros and how to prevent them. 6. **Async Option** — An asynchronous retrospective alternative for remote/distributed teams who can't all meet at the same time.
Example Output
# Retrospective Plan: 8-Person Engineering Team, Post-Sprint (2 weeks)
Context: Shipped a major feature but had a prod incident on Day 9. Morale is mixed.
1. Recommended Format: Sailboat 🚢
**Why this format:** Your team just shipped something significant (celebration-worthy) but also dealt with a stressful incident. The Sailboat metaphor lets you acknowledge both without the retro feeling like a post-mortem. It also naturally surfaces risks ("rocks") which is perfect after an incident.
🏝️ ISLAND (our goal/vision)
|
💨 WIND --------🚢-------- ⚓ ANCHOR
(what propels us) | (what slows us down)
|
🪨 ROCKS
(risks ahead)
2. Facilitation Guide (60 minutes)
| Time | Activity | Details |
|------|----------|---------|
| 0:00-3:00 | **Check-in** | "In one word, how did this sprint feel?" — go around the room. No discussion, just words. (This surfaces mood without debate) |
| 3:00-5:00 | **Review previous action items** | Pull up last retro's 3 action items. Quick status: ✅ Done / 🔄 In progress / ❌ Not started. No blame — just status. |
| 5:00-7:00 | **Set the stage** | Draw the sailboat on the whiteboard (or share the Miro/FigJam template). Explain the 4 quadrants. |
| 7:00-17:00 | **Silent writing (10 min)** | Everyone writes sticky notes for each quadrant. One idea per sticky. Aim for 2-3 per quadrant. Use a timer. |
| 17:00-25:00 | **Share & cluster** | Each person places their stickies on the board, reading each one aloud (15 sec max). Facilitator groups similar themes. |
| 25:00-30:00 | **Dot voting** | Each person gets 3 dots. Vote on which themes to discuss. Facilitator picks top 3. |
| 30:00-50:00 | **Discussion (20 min)** | Deep-dive into top 3 themes (~7 min each). For each: What's really going on? What could we try? Who would own it? |
| 50:00-57:00 | **Action items** | Capture 2-3 specific action items using the template below. Must have an owner and deadline. |
| 57:00-60:00 | **Closing** | "What's one thing you appreciate about this team from the last sprint?" — quick round, end on a high. |
3. Facilitation Tips
Getting quiet people to talk:
- Silent writing before discussion is the #1 technique — it equalizes airtime
- Directly invite (don't call out): "Alex, I noticed you had an interesting sticky about testing — can you tell us more?"
- Use round-robin for action item brainstorming: "Let's go around — each person suggest one thing we could try"
Preventing dominance:
- Set a "1 comment, then pass" rule during discussion
- As facilitator, say: "Great point, Sam. Let's hear from someone who hasn't spoken on this topic yet."
Handling blame:
- Redirect from people to systems: "That's frustrating. Let's talk about what process or tooling change could prevent that."
- Pre-set a ground rule: "We're here to fix systems, not assign blame. The Prime Directive: everyone did the best they could with what they knew."
4. Action Item Template
| # | Action | Owner | Deadline | Success Signal |
|---|--------|-------|----------|----------------|
| 1 | Add staging environment smoke test to CI pipeline | @jordan | April 8 | Smoke tests run on every staging deploy |
| 2 | Create incident response runbook for database issues | @priya | April 11 | Runbook reviewed by team + linked in Notion |
| 3 | Start sprint with 30-min "requirement clarity" session | @facilitator | Next sprint | Team rates requirement clarity >7/10 in next retro |
5. Anti-Patterns to Avoid
| Anti-Pattern | Why It Kills Retros | Fix |
|-------------|--------------------|----- |
| "Groundhog Day" retro | Same issues every sprint, no action | Review previous action items FIRST. If nothing changed, discuss why. |
| Manager dominates | People self-censor around authority | Manager speaks last or only asks questions |
| Too many action items | 7+ items = nothing gets done | Max 3 action items per retro. Fewer = better. |
| Skipping retros when "things are fine" | You lose the habit and miss early warning signs | Always hold them, even if short |
| No follow-up | Actions disappear into the void | Start every retro by reviewing last retro's action items |
Tips for Best Results
- 💡The #1 retro killer is not following up on action items. Start every retrospective by reviewing what happened with last sprint's commitments.
- 💡Rotate the facilitator role — when the same person always runs retros, the team starts performing for them instead of being honest.
- 💡Limit action items to 3 maximum. Teams that leave with 7 action items complete none of them.
- 💡If your team groans about retros, change the format. The same Start/Stop/Continue every two weeks for a year would make anyone check out.
Frequently Asked Questions
What is the Retrospective Meeting Facilitator prompt?
Facilitate effective team retrospectives that surface real issues, celebrate wins, and produce concrete action items — with multiple format options beyond the basic 'what went well / what didn't' template. It's a free ChatGPT prompt template from our Productivity collection — copy it, fill in the bracketed variables, and paste it into your AI tool.
Which AI tools work with this prompt?
It's written and tested for ChatGPT, Claude and Gemini. Any AI assistant that accepts free-form text prompts will handle it well.
How do I customize this ChatGPT prompt?
Replace the bracketed variables — such as [number of participants], [1 week / 2 weeks / monthly / quarterly], [high / neutral / low / tense / mixed] — with your own details before running it. The #1 retro killer is not following up on action items. Start every retrospective by reviewing what happened with last sprint's commitments.
Is this prompt free to use?
Yes. Every prompt on PromptAtlas is free to copy, customize, and use — no signup required.
Related Prompts
Daily Planning & Prioritization
Structure your day with clear priorities, time blocks, and energy-matched task scheduling.
Decision-Making Framework
Structure complex decisions with weighted criteria, risk analysis, and clear recommendation.
Brainstorming & Ideation Session
Run a structured brainstorming session that generates creative, actionable ideas using proven techniques.