Hot Air Balloon Retrospective
Lift, weight, storms, and fire visualize help, drag, uncertainty, and energy.
Hot air
What lifts the team—motivation, clarity, support, wins.
Sandbags
Weights slowing ascent: debt, handoffs, unclear scope, or bottlenecks.
Storms
External risks or volatility you need to navigate.
Fire
Fuel and heat—energy sources and passion worth stoking.
This board is for demo purposes only. Your responses are not saved. Close or refresh the page to clear all cards. Do not add any sensitive information.
What is the Hot Air Balloon Retrospective?
The Hot Air Balloon Retrospective is a visual metaphor-based format that frames the team journey as a balloon flight. Like the sailboat format, it uses physical forces as analogies for team dynamics, but the vertical dimension—rising versus falling—creates a different emotional resonance. The format emerged from the agile coaching community in the early 2010s as facilitators looked for fresh metaphors to re-engage teams experiencing retrospective fatigue.
Four elements define the balloon journey. "Hot Air" represents the forces lifting the team—motivation, good practices, supportive leadership, and clear goals. "Sandbags" are the weights dragging the team down—technical debt, unclear priorities, excessive meetings, or skill gaps. "Storms" represent external threats and turbulence—market shifts, organizational changes, or unexpected dependencies. "Fire" is the energy source—the passion, curiosity, and drive that fuels the team.
The distinction between hot air and fire is subtle but important. Hot air is about conditions that lift the team (external support, good tools), while fire is about internal energy and passion. Teams that have good conditions but low fire are coasting; teams with intense fire but heavy sandbags are burning out. This two-dimensional view of positive forces creates more nuanced discussions about team health.
When to use the Hot Air Balloon Retrospective
The Hot Air Balloon format is particularly effective when a team needs to discuss both external pressures and internal motivation simultaneously. Use it after a turbulent period—organizational restructuring, major pivots, or extended crunch—when the team needs to process what happened and assess their readiness to move forward. The storms column explicitly creates space for external factors that other formats often ignore.
This format suits teams of four to ten people and works best in a 50 to 60 minute session. It is especially useful for teams that feel stuck or are losing altitude (morale dropping, velocity declining) because it helps diagnose whether the problem is too many sandbags, insufficient fire, or approaching storms. The visual language makes it easier to discuss these dynamics without making anyone feel personally responsible for the team state.
Avoid this format when the team needs to focus on specific tactical improvements. The metaphorical nature of the format can sometimes lead to abstract discussions that are rich in imagery but thin on concrete action items. Pair it with a brief action-planning session at the end to convert insights into experiments.
How to facilitate the Hot Air Balloon Retrospective
Start by drawing a hot air balloon on the board with clearly labeled zones: flames below the basket for fire, rising arrows for hot air, bags hanging from the basket for sandbags, and storm clouds nearby. Spend a moment on the metaphor—ask the team: "If our team were a hot air balloon right now, how high would we be flying?" This opening question calibrates shared perception before diving into details.
Give the team seven minutes for silent card writing across all four categories. Process "Fire" first—what energizes the team? This starts the conversation with passion and purpose. Then move to "Hot Air"—what external conditions are lifting you? Next, tackle "Sandbags"—what weights could you cut to rise higher? Finally, address "Storms"—what external threats are approaching?
After processing all quadrants, facilitate a synthesis conversation: "Given our current fire and hot air, which sandbags should we cut first? Which storms do we need to prepare for?" This prioritization question naturally leads to action items. Aim for one sandbag to cut, one fire to stoke, and one storm preparation plan. Close by asking: "After this discussion, how high will we be flying in two weeks?"
Tips for getting the most out of the Hot Air Balloon Retrospective
The "Fire" column is often underutilized. Teams focus heavily on sandbags and storms (problems and threats) while giving fire a cursory treatment. Invest real facilitation time here. Ask: "What made you excited to come to work this sprint? What problem were you most engaged in solving?" Understanding what fuels the team is just as important as understanding what drags it down. Teams that lose touch with their fire eventually lose their best people.
Be careful with the "Storms" column. It is tempting to fill it with things the team cannot control—company politics, market conditions, regulatory changes. While naming these is valuable, ensure the discussion moves to "what can we do about it" rather than spiraling into helplessness. For each storm, ask: "Can we avoid it, weather it, or leverage it?" Some storms create opportunities for well-prepared teams.
Track the team altitude over time. At the start of each retro using this format, ask the team to rate their current altitude on a scale of one to ten. Plot these over months to visualize team health trends. This simple metric creates a longitudinal view that individual retros miss.
Variations and adaptations
For remote teams, use a digital whiteboard with a colorful balloon illustration. Consider adding altitude markers (ground level, cruising altitude, stratosphere) and ask each participant to place a dot at the altitude they feel the team is at. This anonymous altitude check creates a powerful visual that immediately shows alignment or divergence in team perception.
For async retros, share the balloon board with the instruction: "Place your cards where you feel them most strongly. If a sandbag feels particularly heavy, make the text bold or add a weight emoji." These visual intensity cues help the synchronous facilitator prioritize discussion without extensive voting. Async participants can also comment on each other cards to build context before the live session.
A powerful variation adds a fifth element: "Compass" or "Navigation" representing the team direction and decision-making. This is useful when the team feels they are flying but unsure where they are heading. Another adaptation for quarterly planning adds "Fuel Reserves"—resources, goodwill, and buffer that the team has banked and can draw upon. This variation helps teams assess not just current state but their resilience and capacity for the challenges ahead.
Run Retrospectives in CodeKudu
CodeKudu includes dozens of retrospective board templates, anonymous feedback, AI summaries, and action items that sync to GitHub Issues, Jira, and Linear.
