Retrospective templates
Retrospective templates Updated

Mountain Climberretrospective template

Long projects can feel like a climb with no clear view of the distance already covered. The Mountain Climber retrospective turns that journey into four concrete conversations about progress, rough terrain, missing supplies, and the summit the team wants to reach next.

Duration
35–45 minutes
Team size
3–12 people
Best for
Long projects, milestone reviews, and a demanding next stage
Mountain Climber retrospective template preview

What each column means

Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.

Base Camp Wins

3

Which progress or capability has the team secured?

  • The migration now runs with real data.
  • The team can deploy without help from a specialist.
  • The customers in the beta completed the full workflow that the team put in front of them, all the way to the end.

Steep Sections

3

Where did progress become unusually difficult or draining?

  • Setting up tests consumed most of the story.
  • Ownership changed during implementation.
  • The dependency failed and gave the team no useful error messages.

Supplies We Need

3

Which support, knowledge, tool, or decision does the team need next?

  • A named security reviewer.
  • Production-like performance data covering the conditions the team expects to face while it works through the next stage and toward the summit.
  • Dedicated time with the support team.

Summit Next

3

Which concrete outcome should the team reach next?

  • Ten customers complete onboarding.
  • On-call can diagnose a failure within ten minutes, using the evidence available during the incident and following the same path anyone else would use.
  • The old service is retired safely.

35–45 minutes agenda

A complete path from framing the room to assigning one concrete follow-up.

  1. 01

    Frame the review

    Name the sprint or project being reviewed, restate the purpose of each column, and remind everyone to describe observable events.

    3 minutes
  2. 02

    Write observations silently

    Give everyone uninterrupted time to add one specific observation per card across every column.

    7 minutes
  3. 03

    Share and clarify

    Read the cards column by column and let authors add context without debating solutions yet.

    7 minutes
  4. 04

    Group and vote

    Combine cards that describe the same pattern, then vote for the themes that would most improve the next iteration.

    5 minutes
  5. 05

    Discuss the leading themes

    Explore causes, consequences, and tradeoffs behind the highest-voted themes while making space for dissenting evidence.

    10 minutes
  6. 06

    Commit to one change

    Turn the strongest insight into a small action with an owner, deadline, and signal the team can review next time.

    5 minutes

Use this format when

  • The work stretches across several sprints.
  • The team needs a lift and some practical preparation for what comes next.
  • One milestone is ending as the next begins, and the team needs enough time to connect what it learned with the demands ahead.

Choose another format when

  • The team needs a quick weekly check on its process.
  • The group has no shared objective for the next stage.
  • An urgent conversation needs direct language, especially when a climbing metaphor would slow the group down or soften a point that needs to land clearly.

Facilitation tips

  • Start by naming the journey under review and the next summit.
  • Celebrate new capability alongside completed tickets.
  • Keep difficult terrain separate from the supplies that would help the team cross it.
  • Make the summit outcome clear.
  • Choose an owner for each needed supply before the next climb starts.

Useful variations

Release climb

Set the launch outcome as the summit and treat readiness gaps as missing supplies.

Quarterly expedition

Trace progress toward one objective across several sprints.

Learning climb

Treat knowledge gained as a win and missing evidence as a needed supply.

Before the retro

Recommended warm-up

Draw & Guess icebreaker game preview

Draw & Guess

Start visually before exploring the team's climb, obstacles, and summit.

Play the warm-up

Frequently asked questions

What are the Mountain Climber retrospective columns?

The four columns are Base Camp Wins, Steep Sections, Supplies We Need, and Summit Next.

When is the Mountain Climber format useful?

Choose it for a long project, a milestone transition, or a team preparing for a demanding next stage.

What should go in Supplies We Need?

Add a specific resource, decision, skill, relationship, or piece of evidence the team requires for the next outcome.

How is it different from Sailboat?

Mountain Climber follows progress through stages and checks readiness for the next one. Sailboat looks at forces, drag, risk, and destination.

Run this Mountain Climber Retrospective

Open the ready-made columns, invite the team, collect observations, vote, and leave with an owned improvement.