The Mountain Expedition: A retrospective for reaching new heights
Published on Oct 27, 2026
Published on Oct 27, 2026
Pro

Did you enjoy the last Speedboat retrospective you organized with your team? After that experience by the sea, why not try the mountains? The Mountain Expedition retrospective provides an environment conducive to collective reflection. Much like a team of climbers making their way up a mountainside, you will identify what is helping or hindering your progress toward the summit.
A retrospective is an essential discussion opportunity for any Agile team. Held at the end of each sprint, it helps participants analyze their work processes, identify effective practices, and pinpoint areas for improvement. Scrum Masters and project managers foster team engagement and keep the session interesting by regularly varying retrospective formats, which facilitates the implementation of sustainable improvements.
Klaxoon’s Mountain Expedition template is a structured whiteboard that allows you to evaluate your sprint preparation, identify obstacles, assess the quality of your collaboration and dependencies, and recognize your victories and successes at the end of the sprint.


Every contribution type and each key area on the whiteboard is instantly recognizable.
Now let’s see how your team can use this visual retrospective to build on its strengths and move forward with all your projects.
The Mountain Expedition retrospective is an end-of-sprint workshop that frames the team’s reflections as a mountain climbing. Participants are invited to recount their sprint as if they were a rope team climbing a peak, step by step.
Their journey is divided into four stages:
Why this mountain metaphor? Simply because it helps bring to life the idea of a team moving toward a common goal, where everyone depends on one another to get there. The team thus analyzes its performance with perspective, without losing sight of what led it to the summit.
While Scrum Masters and Agile teams are the primary users of the Mountain Expedition retrospective, any team that completes a work cycle and wants to step back to reflect on its achievements can also use it.
For project managers, product teams, or marketing teams, it’s a simple and visual method for analyzing a completed phase, even outside a strict Scrum framework. The mountain metaphor resonates with everyone, making it easier for participants unfamiliar with Agile terminology to engage.
Some specific contexts fit particularly well to this format, for example:
Furthermore, this format works equally well in-person and in a hybrid setting: the shared Klaxoon whiteboard brings everyone together in the same space and remains accessible to participants even after the workshop.
This method is particularly well-suited for teams of up to 10 people. With a larger group, the session may take longer, especially because of the time required to identify and clarify all dependencies.
The Mountain Expedition retrospective’s primary strength lies in the engagement it fosters. Its visual and narrative format captures attention more effectively than a standard discussion format. It allows everyone, including those who are typically more introverted, to imagine themselves on the expedition and find it easier to speak up.
Its visual structure also brings greater clarity to the discussion. The four sections clearly distinguish between what set the team up for success, what held it back, how it collaborated, and what it managed to achieve. Feedback doesn’t get mixed up, and the discussion remains clear and traceable from start to finish, even after the workshop ends.
Another distinctive feature of the Mountain Expedition Retro is its ability to balance positive and negative aspects, which is not always the case with other formats. For instance, the Summit Reach section provides as much visibility to successes as the Loose Rocks section does to challenges. The team can acknowledge its victories while considering friction points, thereby improving preparation for the next sprint.
Additionally, this method places a huge emphasis on collaboration. The Climb Team Communication section provides a dedicated space for interpersonal dynamics, which is often missing from formats focused solely on tasks. Here, the team can evaluate how well they communicate and adjust their work processes.
Finally, the Mountain Expedition has a structure that helps the team transition from ideas to actions. Each zone provides the participants with concrete lessons that they can use to improve the next sprint. Thus, the retrospective is not just an isolated discussion, and results in collective, concrete decision-making that is carried out over time.
If you’ve ever facilitated a Speedboat retrospective, the logic behind the Mountain Expedition one will seem familiar. Speedboat is based on the metaphor of a boat sailing toward an island. The anchors represent what holds the team back, the wind represents what propels it forward, and the rocks represent the risks that threaten it, while the island stands as the goal to be achieved.
Whether on the sea or in the mountains, Speedboat and the Mountain Expedition retrospectives both share the same fundamental objective: to help visualize teamwork through a metaphorical image. However, Speedboat focuses primarily on looking ahead, identifying what holds the team back and what propels it toward its goal. On the other hand, the Mountain Expedition addresses two additional dimensions: team preparation with the Basecamp Effort, and the quality of collaboration through the Climb Team Communication area.
Speedboat retrospective | Mountain Expedition retrospective |
A metaphor for a boat sailing toward an island | A metaphor for a climbing team scaling a peak |
Focused on obstacles and drivers | Covers preparation, challenges, collaboration, and successes |
Goal-oriented | A comprehensive review of the completed cycle |
Ideal for assessing progress toward a final goal involving multiple sprints | Ideal for a detailed end-of-sprint review |
To illustrate how this method is applied, here are three examples of typical situations where the Mountain Expedition retrospective can yield good results:


At the end of the retrospective, the team lists the best practices to adopt in the “Action Plan” section located below the four key areas.
This Board template provides a structured, mountain-climbing-themed whiteboard. Your goal is to transform the lessons learned during the climb, the risks identified, and the successes achieved at the summit into concrete actions, assigning each to a designated person. Plan for 30 to 60 minutes, depending on your team’s size.
When your Board is ready, click the Share button to generate its unique link and send it to the participants. On the day of the retro, follow these steps:
The Mountain Expedition retrospective gives your team a comprehensive overview of their sprint, from preparation to summit victories, including obstacles and the quality of collaboration. It complements other formats, such as Speedboat, and allows you to change your perspective from one sprint to the next, ensuring that the ritual remains engaging and dynamic.
With this Klaxoon template, facilitating this retrospective has never been easier, whether in person or remotely. Your team will walk away with clear, well-defined actions, ready to aim for the next summit. A must-try for your next retrospective!
A sprint review focuses on the delivered product and often brings together all stakeholders. A retrospective, including the Mountain Expedition format, focuses on how the team functions and on ways to improve its processes.
Plan for 30 to 60 minutes. Smaller teams tend to fall closer to the lower end of the range, while larger groups or busy sprints tend to fall closer to the higher end.
Yes. The Klaxoon shared whiteboard brings all participants together in the same virtual space, whether they are working on-site or remotely. Moreover, participants can contribute either synchronously, during the meeting, or asynchronously by submitting their ideas before the group discussion.
Switch to Anonymous mode during the brainstorming session. This allows participants to post their ideas in the Board areas without fear of judgment, helping to identify points that might otherwise go unmentioned.
At the end of your retrospective, assign someone to be responsible for each action identified for the next sprint. Do not end the workshop until at least three clear next steps have been defined. You can also use Klaxoon’s native integration with Wrike to convert your ideas into structured tasks that are tracked in Wrike.




