Mountain Climber Retrospective
Trail metaphors for gear, obstacles, weather, and the summit—great for big goals.
Base camp
Foundations that supported the climb—basics that worked.
Boulders
Big obstacles that slowed or redirected the team.
Weather
Mood and morale—stormy, foggy, or clear skies.
Summit
The goal line—alignment on what "done" means for the team.
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 Mountain Climber Retrospective?
The Mountain Climber Retrospective uses the metaphor of a mountain expedition to frame team reflection. Each element of the climb represents a different aspect of the team experience: the base camp represents foundations, boulders represent obstacles, weather represents morale and conditions, and the summit represents the ultimate goal. The format was developed by agile facilitators seeking a metaphor that emphasizes long-term effort, incremental progress, and the relationship between preparation and achievement.
The climbing metaphor is particularly apt for software teams because it captures the non-linear nature of complex projects. Mountain climbing involves careful preparation, unexpected obstacles, changing conditions, and the need to sometimes retreat and try a different route. These dynamics mirror the reality of iterative development far better than linear metaphors like road trips or assembly lines.
What makes this format unique among metaphor-based retros is the emphasis on altitude and progress. The base camp represents where the team started, and the summit represents where they are going. This vertical dimension creates a natural conversation about progress: "How far up the mountain are we? Are we ascending, plateauing, or have we lost altitude?" This progress-oriented framing motivates teams working on long initiatives where daily progress is hard to perceive.
When to use the Mountain Climber Retrospective
The Mountain Climber format excels during multi-sprint initiatives where the team needs to maintain motivation and strategic alignment over an extended period. Use it at mid-project checkpoints, quarterly reviews, or after completing a significant milestone that represents reaching a new altitude. It is especially valuable when the team is climbing toward a big, ambitious goal and needs to stay oriented toward the summit.
Teams of four to ten people benefit most, and the format works well in 60-minute sessions. It is particularly effective for teams that are starting to feel the fatigue of a long project—the climbing metaphor normalizes the difficulty of sustained effort and creates space to acknowledge exhaustion without framing it as failure. "The weather has been rough" is easier to say than "I am burning out."
Avoid this format for short sprints or projects with no clear long-term goal. The summit metaphor requires a meaningful destination to be effective. Also avoid it when the team needs to process immediate tactical issues—the strategic, long-view nature of the climbing metaphor may feel disconnected from day-to-day sprint concerns.
How to facilitate the Mountain Climber Retrospective
Draw a mountain on the board with clearly labeled zones: base camp at the bottom, boulders on the slopes, weather icons in the sky, and the summit at the peak. Mark the current team position on the mountain based on project progress—this visual anchor grounds the entire discussion. Ask the team: "Where do you think we are on this climb?" and discuss any disagreement about altitude.
Give the team seven minutes to write cards for all four columns. Process Base Camp first: "What foundations supported us?" This acknowledges the preparation and groundwork that enabled progress. Then Boulders: "What obstacles did we encounter?" For each boulder, discuss whether it was avoidable, what the team learned from navigating it, and whether similar boulders lie ahead.
Move to Weather for a morale and conditions check: "What has the atmosphere been like?" This column surfaces emotional and cultural factors. Finally, discuss the Summit: "Are we still aligned on what reaching the top looks like? Has the goal shifted?" Close by identifying one boulder to clear, one weather condition to address, and one practice from base camp to maintain as the team continues climbing.
Tips for getting the most out of the Mountain Climber Retrospective
The "Weather" column is the most nuanced and deserves careful facilitation. Weather is not just mood—it includes the conditions that affect morale. "Stormy" might mean interpersonal conflict, but it might also mean external pressure from stakeholders, or uncertainty about the project direction. Ask clarifying questions to understand what kind of weather people are experiencing and what is causing it.
Use the altitude marker as a tracking device across retros. Each time you run this format, mark where the team was and where they are now. Seeing visual progress up the mountain over months is motivating. If the team notices they have been at the same altitude for three retros, it opens a valuable conversation about what is preventing ascent.
The Boulder column benefits from distinguishing between boulders you can move, boulders you must climb over, and boulders you need to route around. This categorization leads to different action types: removal (fix the root cause), adaptation (change your approach), or avoidance (change direction). Teams that try to move every boulder waste energy on immovable obstacles.
Variations and adaptations
For remote teams, use a rich digital illustration of a mountain with interactive elements. Place team member avatars at their perceived altitude and discuss the spread—if some people feel higher on the mountain than others, that divergence is a valuable data point about team alignment. Remote teams also benefit from a shared "climbing journal" document where key insights from each retro are recorded, creating a narrative of the journey.
For async teams, the Mountain Climber format works well as a reflection exercise posted at the end of each sprint. Each team member briefly notes their altitude, the biggest boulder they encountered, and the weather they experienced. These individual reflections accumulate into a rich data set that the synchronous quarterly retro can analyze for patterns—recurring boulders, persistent weather patterns, and altitude trends.
A popular variation adds "Gear" as a fifth column—the tools, skills, and resources the team brought to the climb. This is useful for capability-focused discussions: "Do we have the right gear for the next phase of the climb? What gear do we need to acquire?" Another adaptation for teams nearing project completion adds a "Descent" column—planning for what happens after the summit. In software, the descent is often neglected: documentation, knowledge transfer, maintenance planning, and team reassignment all need attention before the climb is truly complete.
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.