On this page (10 sections)
The hot air balloon retrospective pictures the team as a balloon. What lifts us up is the hot air that keeps you rising. What weighs us down is the sandbags: load you carry. Storms ahead are trouble you can see coming, and where we want to go is the destination. The format's real question is about load: what are we carrying that we could drop?
The four columns
| Column | What goes here | Example note |
|---|---|---|
| ๐ฅ What lifts us up | What gives the team energy and momentum, and needs to keep getting fuel | "Customer interviews every other Friday keep us excited about the roadmap." |
| ๐ What weighs us down | Load the team carries: commitments, work in progress, meetings, old promises | "We still support the v1 API for three customers." |
| โ๏ธ Storms ahead | Trouble you can see coming from outside the team | "The January budget review may cut our contractor." |
| ๐ฏ Where we want to go | The destination, and how you'll know you've arrived | "By the end of Q1, we own three services instead of seven." |
Sandbags are a choice. Balloonists climb by dropping ballast. Most of what weighs a team down was picked up on purpose once: a promise to one customer, a weekly report, a side project. Ask of each one: what if we dropped it?
Where it comes from. Nobody is credited with inventing it. It was already in use by January 2009, when Sarah Taraporewalla wrote about it as the best retrospective game she had seen, with fire lifting the balloon and sandbags slowing the team down. Later versions added the storms and the destination; nobody is credited with those either.
In Retro Rabbit
The Hot Air Balloon template in Retro Rabbit
Pick Hot Air Balloon from the format library when you create a Team Room (or later in its Settings) and the board starts with its four columns. Your team adds notes during the sprint, with or without their name shown, then votes on what to talk about.
Hot Air Balloon ยท Sprint #14
Example notes
What lifts us up
- Customer interviews every other Friday keep us excited about the roadmap2 votes
- Owning the partner API end to end, no handoffs to another team4 votes
What weighs us down
- Still supporting the v1 API for three customers5 votes
- Four status meetings a week, and most of them repeat standup3 votes
Storms ahead
- January budget review may cut our contractor3 votes
- Design team moves to a new tool next month, so specs may slip2 votes
Where we want to go
- By end of Q1 we own three services instead of seven1 vote
- Ship the partner API without anyone working weekends1 vote
- What lifts us up
- What weighs us down
- Storms ahead
- Where we want to go
14-day free trial ยท No credit card
When to use it (and when not to)
Use it when:
- the team feels heavy: too many things in progress, too many side commitments
- you're starting a new quarter and want to choose what not to carry into it
- energy is dropping and you want to know what still gives people a lift
Balloon, Sailboat or Speed Car? All three have forces for and against. Pick the balloon when the problem is load and energy. Pick Sailboat when you have a clear project goal and the risks on the way matter most. Pick Speed Car when the topic is delivery speed and you have 30 minutes.
Pick something else when:
- every sandbag is a mandate from above. The retro becomes a complaint session; run Mad Sad Glad to air it instead.
- the team has no shared destination yet. Agree one in planning first.
- you need behavior changes fast. Start Stop Continue gets there in 30 minutes.
How to run it live (45 minutes)
| Time | Step |
|---|---|
| 0โ4 min | Review last retro's action items |
| 4โ8 min | Agree on the destination |
| 8โ18 min | Silent writing: lift, weight and storms |
| 18โ22 min | Group and name |
| 22โ26 min | Dot vote: three votes each |
| 26โ40 min | Discuss the heaviest sandbags, then storms, then lift |
| 40โ45 min | Agree on what to drop, with owners |
- Check what you dropped last time. Open the Previous Retro tab in the Action Items panel. Did the sandbag actually go, or did it creep back? Old / Unresolved Items shows anything older still open.
- Agree on the destination. One note, written before anything else. If people can't agree, that's the first discussion.
- Write, group and vote. Set the shared timer for 10 minutes, then drag related notes together, vote and sort by Most Votes.
- Discuss sandbags first. For each top one: drop it, shrink it, or keep it on purpose. "Keep it on purpose" is a valid answer, as long as it's said out loud.
- Then storms, then lift. Storms get a "prepare or plan around" answer. Lift gets protected: name one thing to keep fueling.
How to run it async over a sprint
You feel a sandbag while you carry it, in a meeting you didn't need or a ticket for the old API. Post it then.
- Day 1: once someone clicks Start New Retro after the last retro, the facilitator writes the destination as the board's first note.
- During the sprint: people add sandbags as they feel them, and lift when something gives them energy, on the board or in Quick Notes.
- Mid-sprint: the facilitator counts tickets in progress and adds the number as a sandbag note. Numbers end arguments about load.
- Two days before the end: everyone adds storms they can see, then votes.
- The day before: the facilitator groups notes and reads the CarrotIQ Sprint Summary for the weight column.
- Retro day: a 20-minute call on the top sandbags, or fully async: the facilitator posts the top three with a proposed "drop, shrink or keep," and the team replies by end of day.
More in how to run an async retrospective.
12 example prompts
What lifts us up
- What gave you energy this sprint?
- When did the work feel easy, and why?
- What do we need to keep fueling, or it will fade?
What weighs us down 4. What are we carrying that nobody would miss? 5. Which promise are we still keeping that no longer matters? 6. How many things did we have in progress at once?
Storms ahead 7. What's changing outside the team that could knock us off course? 8. Which date on someone else's calendar affects us? 9. What would we do if the storm hit next week?
Where we want to go 10. Is this still where we want to go? 11. What would we drop today if we took the destination seriously? 12. How will we know we've arrived?
Facilitator tip and a common pitfall
Tip: ask "who would notice?" For every sandbag, ask who would notice if it vanished tomorrow. If "nobody" or "only us," drop it this sprint. If it's a customer or another team, the action is a conversation with them, not a quiet stop.
Pitfall: sandbags nobody on the team can drop. Company-wide processes pile into the weight column, the team can't change them, and the retro ends deflated. Before voting, mark the notes the team controls and vote only on those. Send the rest to their owners as one short list, with the cost of each.
How AI helps with this format
On Pro AI (and during the free trial), CarrotIQ takes care of the admin:
- Group names. Drag "v1 API support for three customers" onto "old CSV import still on call" and CarrotIQ names the group, for example "Legacy Support Load".
- Summaries. The Sprint Summary covers each column and the whole retro. Compare a few sprints' weight summaries to see whether dropped sandbags come back.
- Suggested action items. CarrotIQ Suggest drafts an action from the notes, weighting the most-voted ones. Turn it into a drop, shrink or keep decision, then assign it.
Example action items
Most actions here drop something, and check that it stayed dropped.
| Note | Action item |
|---|---|
| Weight: "v1 API support for three customers" | "Nadia emails the three v1 customers this week with a January 31 shutoff date. Done when all three have replied." |
| Weight: "Four status meetings a week" | "Cancel Tuesday and Thursday status. Omar posts a written update in the team channel instead. Next retro: did anyone miss them?" |
| Weight: "Twelve tickets in progress for five people" | "Set a limit of six tickets in progress for one sprint. Jonas tracks how often we hit it." |
| Storm: "January budget review may cut the contractor" | "By December 15, Theo lists what the contractor owns and who would take each piece, and shares it with our manager." |
| Lift: "Customer interviews keep us excited" | "Grace books the next three interview slots now, before the calendar fills up." |
At the next retro, check these in the Previous Retro tab. See retrospective action items that actually get done.
Use this template in Retro Rabbit
- Start a 14-day free trial. No card is needed.
- Pick Hot Air Balloon from the format library: choose "Browse all formats" when you create your Team Room, or later in the Team Room's Settings.
- Write the destination first, and ask people to post a sandbag the moment they feel one.
See pricing for plans.
Related formats
- Sailboat: a project goal and the risks on the way
- Speed Car: the same idea, focused on delivery speed
- Team energy check: energy on its own, without the metaphor
- Start Stop Continue: turn what you dropped into new habits
- More formats in Project retrospectives
- All retrospective templates
Frequently asked questions
What is a hot air balloon retrospective?
A visual retrospective where the team is a balloon. The team lists what lifts it up (the hot air), what weighs it down (the sandbags), the storms it can see ahead and where it wants to go. It looks back at the sprint and ahead at the next one.
How is the hot air balloon different from the sailboat retrospective?
They share a shape: forces for, forces against, risks and a goal. The balloon's weights are things the team carries and could choose to drop, like legacy commitments or recurring meetings, while sailboat anchors are whatever is slowing you down right now. Pick the balloon when the team feels overloaded; pick Sailboat when a project goal and its risks are the main topic.
What are the sandbags in a hot air balloon retrospective?
The load the team carries: work in progress, old promises, tools and meetings that cost more than they give. A balloonist climbs by dropping sandbags, so the useful question for each one is whether you can drop it.
What's the difference between storms and what weighs us down?
Sandbags are on board now, and the team can usually decide to drop them. Storms are ahead and outside the team: a reorg, a budget review, another team's deadline. You can't stop a storm, but you can prepare for it or plan around it.
How long does a hot air balloon retrospective take?
About 45 minutes for a two-week sprint. If people added notes during the sprint, most of that time goes to deciding what to drop.
Is the hot air balloon a retrospective or a futurespective?
Both. Lift and weight look back at the sprint you just finished, and storms and the destination look ahead. That mix makes it useful at the start of a new quarter or after a change in direction.
Run this retro in Retro Rabbit
Your team adds notes during the sprint, CarrotIQ groups and summarizes them and suggests action items, and unfinished items carry into the next retro.
14-day free trial ยท No credit card