Hot Air Balloon Retrospective

Hot Air Balloon Retrospective

The Hot Air Balloon retrospective is a visual metaphor format that does something most retro formats don't: it makes the team look ahead as well as back. In a single 60-minute session, your team surfaces what's lifting them up, what's pulling them down, what risks are gathering on the horizon, and what clear skies lie ahead.

Think of it as the Sailboat's more weather-aware cousin. While Sailboat excels at processing where you've been, Hot Air Balloon combines that backward glance with explicit forward planning. Storm Clouds and Sunny Skies are equal citizens in this format — which is what makes it especially useful at mid-project moments, when understanding what's coming matters just as much as processing what's happened.

When to choose Hot Air Balloon

• Before a high-stakes sprint. When the next fortnight contains a release, a major stakeholder demo, or a technical migration, Storm Clouds gives the team a structured way to name risks before they become incidents.
• When morale is uneven. Some team members feel drained; others are energised. Hot Air makes room for both by separating what's working (Hot Air) from what isn't (Sandbags), rather than blending them into a single sentiment.
• When Sailboat has gone stale. Teams that have run Sailboat many times often find it becomes too backward-facing. Hot Air Balloon is a natural progression — familiar enough to set up quickly, different enough to generate fresh conversation.
• Mid-project rather than just end-of-sprint. At a project quarter-mark or after a major delivery, the Sunny Skies column gives the team space to recharge around what's coming, not just decompress about what's past.
• For distributed or hybrid teams. Anonymous brainstorming levels the playing field — quieter team members often surface the sharpest Storm Clouds observations when they can type freely without being put on the spot.

Warm up: Pre-flight weather check

Every balloon pilot files a weather report before takeoff. This is yours.

Before the session, open TeleRetro's AI Icebreaker Bot and grab a question to kick things off — or use one of these:

• "If last sprint was a weather forecast, what was it? ⛈️ Hailstorm? 🌤️ Partly cloudy?"
• "What's one thing you'd pack in the basket for the sprint ahead?"
• "Give the team a one-word forecast for the next two weeks."

Then, as the team joins:

1. Start the IceBreaker music — pick something upbeat and let it play as people arrive.
2. Switch on Brainstorming mode so everyone writes privately. No peeking.
3. Post the question — If last sprint was a weather forecast, what was it? — and ask everyone to add one card to 🌤️ Weather Report.
4. Reveal — once all cards are in, the facilitator switches off Brainstorming mode. Every answer appears at once.
5. React with an emoji on the card that most matches your own feeling. The more dramatic the better.

Leave the cards in Weather Report — they stay as a visible snapshot throughout the retro. The whole thing takes 5–7 minutes. Keep moving; the energy from the reveal is exactly what you want to carry into the main columns.

🌤️ Weather Report

If last sprint was a weather forecast, what was it?

Your one-card contribution before the balloon leaves the ground. Add it during the warm-up. Leave it there — it's a useful reminder of what the team was thinking at takeoff, and a good conversation starter if the retro mood drifts far from those opening answers.

🔥 Hot Air

What practices and dynamics are driving the team forward?

Hot Air is everything that's lifting the balloon: momentum, solid practices, helpful tooling, clear requirements, strong team dynamics, or a stakeholder who's making life easier. These are the forces that — if named and actively protected — keep the team climbing. Encourage specificity here. "Pair reviewing on the checkout feature" is more useful to the next sprint than "good communication."

🪨 Sandbags

What blockers or friction are slowing the team down?

Sandbags represent drag: slow processes, unresolved technical debt, unclear requirements, recurring blockers, or anything the team is working around rather than through. The goal isn't to assign blame — it's to identify what the team could drop, reduce, or hand off to fly higher. This column usually generates the most cards. That's a good sign; it means people are being honest.

⛈️ Storm Clouds

What risks or challenges are coming up this sprint?

Storm Clouds are what's gathering on the horizon. Upcoming deadlines, unclear dependencies, capacity concerns, changes in leadership, things the team is quietly worried about but hasn't said out loud yet. This column is what transforms the Hot Air Balloon retro from a purely reflective exercise into a forward-planning one. Every Storm Cloud identified here should, ideally, produce at least one concrete action item before the session ends.

☀️ Sunny Skies

What milestones or moments is the team looking forward?

Sunny Skies close the session on a lift. A new team member joining, a technical improvement nearly ready to ship, a feature the team is genuinely excited to build, a scheduled team lunch. This column is often undervalued — but naming what lies ahead in positive terms changes the energy in the room and makes action items feel achievable rather than burdensome.

---

Facilitating the discussion

After the brainstorm, resist spending all your time on Sandbags. A healthy time split is roughly:

• Hot Air — 10 minutes (celebrate briefly, then move on)
• Sandbags — 20 minutes (these generate the most debate)
• Storm Clouds — 20 minutes (highest-impact actions come from here)
• Sunny Skies — 10 minutes (save energy; use it to close on a high note)

Use anonymous voting to let the team decide what matters most without the loudest voice in the room setting the agenda. Group similar Storm Clouds before voting — teams are often surprised how often the same risk has been noticed from different angles.

Variations

Three-column version. Drop Sunny Skies if the team is in crisis mode and forward optimism feels forced. Hot Air + Sandbags + Storm Clouds is tighter, more action-focused, and better suited for teams under delivery pressure.

Team energy check-in. Before opening the board, ask everyone to rate their current energy on a scale of 1–5. If the average is below 3, schedule extra time for Sunny Skies at the end. This turns the retro into a light team health check without adding a separate ceremony.

Quarterly Hot Air Balloon. Run a longer version every quarter with a 90-minute timebox. Use Pulse Survey data from the previous three months to pre-populate Storm Clouds with evidence — it saves brainstorm time and grounds the conversation in real signals rather than recent memory.

Related formats

• Sailboat retrospective — The closest sibling. More backward-facing, stronger for long-term goal-setting. Good to alternate with Hot Air Balloon across sprints.
• DAKI retrospective — When your team wants direct action language (Drop, Add, Keep, Improve) rather than a metaphorical frame.
• Starfish retrospective — When you want five explicitly action-oriented dimensions and the team is ready to go without metaphor.
• KALM retrospective — A four-column practice-focused format for teams that want the forward-backward balance without the imagery.

All formats are available on every TeleRetro plan. See pricing for details.

Start a Hot Air Balloon Retro View all retro templates

---

Frequently Asked Questions

What is the Hot Air Balloon retrospective template?

The Hot Air Balloon retrospective is a four-column agile format that uses the metaphor of a balloon flight to structure team reflection. Hot Air captures what's propelling the team forward, Sandbags identifies what's slowing you down, Storm Clouds surfaces upcoming risks, and Sunny Skies highlights what the team is looking forward to. Unlike purely backward-looking formats, Hot Air Balloon blends retrospective and forward planning into a single session.

When should you use the Hot Air Balloon retrospective?

Use the Hot Air Balloon retrospective when your team needs to look both backward and forward in the same session — particularly before a significant milestone, when risks are looming, or when morale needs a lift from focusing on what's ahead. It works especially well mid-project, when a team has grown familiar with Sailboat and wants a natural step forward, or when upcoming change (a new team member, a tech migration, a hard deadline) makes it important to name both risks and opportunities explicitly.

How do you run a Hot Air Balloon retrospective meeting effectively?

To run an effective Hot Air Balloon retrospective, follow these steps:

• Set the stage - Use a mood check-in to gauge how the team is feeling, then walk through the balloon metaphor. The goal is to surface what's lifting the team, what's weighing it down, and what weather is ahead
• Brainstorm - Give 10 minutes for silent individual brainstorming with icebreaker music. Team members add cards to all four columns anonymously. Encourage specificity — "slow CI pipeline" is more useful than "tech issues"
• Group and sort - Group and sort similar cards together. Storm Clouds often surfaces clusters that surprise people
• Discuss and vote - Vote to prioritise. Spend the most time on Sandbags (to reduce weight) and Storm Clouds (to mitigate risk before it lands)
• Create action items - Assign owners and deadlines to the top-voted items. Every Storm Cloud should produce at least one action — risk without a plan is just worry
• Share summary - Export and share the retro summary with the team

Sessions typically run 60 minutes. Allow extra time on Storm Clouds if the team is heading into a complex sprint.

How is the Hot Air Balloon retrospective different from the Sailboat retrospective?

Both formats use visual metaphors, but they have a different centre of gravity. Sailboat is primarily backward-looking — Wind pushed you, Anchors held you back, Rocks are risks, and the Island is your long-term goal. Hot Air Balloon is more forward-balanced: Storm Clouds and Sunny Skies push the conversation toward what's coming next, not just what happened last sprint. Sailboat also invites strategic goal-setting through its Island column; Hot Air Balloon replaces that with Sunny Skies, which shifts energy toward immediate motivation rather than long-horizon planning. Use Sailboat when you want strategic clarity; use Hot Air Balloon when you need risk awareness and team morale in the same session.

What are some alternatives to the Hot Air Balloon retrospective?

If you're looking for different retrospective formats, consider these alternatives:

• Sailboat retrospective — When you want a visual metaphor focused more on long-term goals and strategic direction than on upcoming risk
• Starfish retrospective — When you want five explicitly action-oriented dimensions and the team has moved past needing a metaphor to engage
• DAKI retrospective — When your team prefers direct action verbs (Drop, Add, Keep, Improve) over metaphorical framing
• KALM retrospective — A four-column practice-focused format (Keep, Add, Less, More) for teams that want the forward-backward balance without the metaphor

Hot Air Balloon remains the strongest choice when teams want retrospective reflection and risk planning in a single, visually engaging session.