Generate Icebreaker Questions for a Remote Retrospective
Produces 5 icebreaker questions calibrated for remote retros, ranging from light to reflective. Built for Scrum Masters starting virtual retros who want to warm up the team without wasting time.
When to use this prompt
Use this at the start of any remote retrospective when the team needs 3-5 minutes of warm-up before diving into the real work. You will need a rough sense of the team's current mood and the intensity of the upcoming retro content. The prompt produces 5 questions across a light-to-reflective scale so you can pick one that fits the room. Remote retros especially need icebreakers because there is no casual hallway chat beforehand; the team starts cold and stays cold without warm-up. Do not skip the icebreaker step to save time; the 3 minutes of warm-up are not wasted overhead, they are the price of psychological safety.
The Prompt
You are a Scrum Master generating icebreaker questions for a remote retrospective. Produce exactly 5 questions across a light-to-reflective scale. Team context: - Team size: {{team_size}} - Remote fatigue level: {{fatigue_level}} - Retro intensity coming up: {{retro_intensity}} - Team familiarity: {{familiarity}} For each question, produce: 1. QUESTION â The exact wording the facilitator will use. 2. LIGHTNESS SCALE â 1 (very light, funny, low vulnerability) to 5 (reflective, higher vulnerability, connects to work). 3. TIME ESTIMATE â How many minutes this question will take with this team size (assume ~30 seconds per person). 4. WHEN TO USE â Describe the team mood or situation where this question works best. Examples: "when the team is exhausted after a long launch" or "when the team is new and does not know each other yet." 5. FACILITATOR SCRIPT â 1-2 sentences the facilitator says to introduce the question, plus a follow-up prompt if people are stuck. Produce 1 question at level 1, 1 at level 2, 2 at level 3, and 1 at level 5. Skip level 4. Distribution rationale: - Level 1 for exhausted teams who need lightness. - Level 2 as a default for most retros. - Level 3 (two options) for teams ready to connect more deeply. - Level 5 for post-incident or post-launch retros where emotional context matters. Rules: - No icebreaker longer than 3 minutes total per question. - Avoid icebreakers that require physical presence ("pass the marker") since this is remote. - Avoid icebreakers that ask about weekend plans or hobbies; those can feel performative in a work retro. - Every icebreaker should connect loosely to work, team, or personal state â not trivia.
Example Output
1. LEVEL 1 (light) Question: "If this sprint was a weather forecast, what would it be?" Time: 2 minutes for 7 people. When to use: Exhausted team that needs a chuckle. Also good for first retro of a new team. Script: "We're going to start with something light. Think of this sprint as a weather forecast. Was it sunny? Stormy? Foggy? Your answer can be serious or silly. Let me start: mine was mostly partly cloudy with one tornado warning." 2. LEVEL 2 (default) Question: "What's one thing you're carrying into this retro that you want to name out loud?" Time: 3 minutes for 7 people. When to use: Most retros. A good default that gets people present without being too heavy. Script: "Before we dive in, I'd like to do a quick check-in. Share one thing you're bringing into this retro. It could be something from the sprint, something from outside work, or just your energy level today." 3. LEVEL 3 (connecting, option A) Question: "What's one thing you learned about yourself this sprint?" Time: 3 minutes for 7 people. When to use: Team that has been working together for a few months and is ready to reflect. Script: "We're going to start a little more reflective today. Take a moment and think about one thing you learned about yourself in the last 2 weeks â not the team, just you." 4. LEVEL 3 (connecting, option B) Question: "When did you feel most engaged at work this sprint?" Time: 2 minutes for 7 people. When to use: Mature team, good for identifying what supports team flow. Script: "Think of a specific moment this sprint when you felt most engaged or in the zone. Share the moment without explanation." 5. LEVEL 5 (reflective) Question: "This sprint was hard. What do you need from the team to process it?" Time: 3 minutes for 7 people. When to use: Post-incident or post-failure retro. Only with a team that has established psychological safety. Script: "We've been through something tough together. Before we look at what happened, I want to check in: what do you need from this team to process this sprint? It can be practical or emotional. Take your time."
Recommended Tools
Taskade supports the icebreaker step as part of a retro board with live participation. Notion projects lets you store a library of icebreakers for future retros. Monday works when your retros are embedded in sprint boards. For remote retros specifically, any of these tools work better than a plain video call because they give each participant a visual anchor when speaking.
Frequently Asked Questions
When should I use this prompt?
Use it before every remote retrospective where you need a warm-up icebreaker. Running it once and building a personal library of 10-15 icebreakers is usually enough; you can rotate through them for a year without repetition. Skip the prompt once you have that library. Also skip the icebreaker entirely for very short retros (under 30 minutes) where the 3-minute overhead is too much of the total time. But never skip it for full retros; the warm-up is the price of getting the team from cold to present.
What if the team rolls their eyes at icebreakers?
That is usually a sign that past icebreakers were performative ("share your favorite color") rather than connected to the team's work or state. The level 2 and level 3 icebreakers in this prompt deliberately ask about the team's actual experience rather than trivia, which tends to get genuine engagement even from skeptics. If the eye-rolling persists, name it: 'I hear the skepticism. Let's try this one and see if it helps us land together before the retro.' Sometimes naming the resistance dissolves it. If it doesn't, try a level 1 question that embraces the silliness rather than fighting it.