Templates/Mountain Climb
Engineering, Scrum, Sprint Review

Mountain Climb Retrospective Template

A forward-looking retrospective format that helps goal-oriented teams reflect on progress, identify blockers, and plan the next sprint like climbing a mountain.

20–30 min5 columnsRemote friendly
Create a board
Mountain Climb template illustration
Interactive preview

See it in action

Drag example cards between columns or try voting to explore the format.

14 example cards · changes stay in this previewDrag cards between columns

Start3

What should we begin doing in the next sprint? New habits, processes, or tools to adopt.

Write integration tests for payment pipeline

Run bi-weekly tech debt reduction sessions

Use feature flags for all new deployments

Stop2

What's not serving us? Practices, meetings, or processes to eliminate.

Assigning tickets without clear acceptance criteria

Having a separate status-update meeting — use async check-ins

Continue3

What's working well that we should keep doing? Reinforce positive behaviors and effective processes.

Daily standups — they're tight and focused

Using squash-and-merge for cleaner commit history

Weekly retro — it keeps us honest

Outcomes3

What did we achieve last sprint? Celebrate wins and completed goals before diving into improvements.

Shipped the new onboarding flow — 40% fewer drop-offs

Cut P95 API latency from 800ms to 200ms

Onboarded two new engineers to the team

Goals3

What do we want to achieve in the upcoming sprint? Clear, measurable targets aligned with team OKRs.

Achieve 90% test coverage on all new PRs

Ship the team dashboard by end of sprint

Reduce CI pipeline time to under 10 minutes

The prompts behind the format

What goes in each column?

Use these prompts and example cards to start a focused conversation.

Outcomes

What did we achieve last sprint? Celebrate wins and completed goals before diving into improvements.

Example cards

  • Shipped user authentication module on time
  • Reduced API response time by 40%
  • Completed migration to new CI/CD pipeline

Keep in mind: Don't list tasks instead of outcomes

Start

What should we begin doing in the next sprint? New habits, processes, or tools to adopt.

Example cards

  • Start writing integration tests for all new endpoints
  • Start a shared on-call rotation doc
  • Start weekly demo sessions for stakeholders

Keep in mind: Don't list things that should already be happening

Stop

What's not serving us? Practices, meetings, or processes to eliminate.

Example cards

  • Stop having status-only standups
  • Stop assigning tickets without acceptance criteria
  • Stop context-switching between three active projects

Keep in mind: Don't call out individuals — keep it process-focused

Continue

What's working well that we should keep doing? Reinforce positive behaviors and effective processes.

Example cards

  • Continue pair programming for complex features
  • Continue Friday demo sessions
  • Continue using our current sprint planning cadence

Keep in mind: Don't treat this as a filler column

Goals

What do we want to achieve in the upcoming sprint? Clear, measurable targets aligned with team OKRs.

Example cards

  • Reduce bug count by 30% next sprint
  • Complete user dashboard feature
  • Achieve 90% test coverage on new code

Keep in mind: Don't set vague goals without measurable outcomes

Timeline

How to run it

Mountain Climb takes about 20–30 min. Here's the flow.

5
01

Introduction

Facilitator explains the climb metaphor and each column. Remind the team this is blameless and future-focused.

10
02

Add cards

Team silently adds cards to each column. Start, Stop, Continue get most attention; Goals and Outcomes are forward-looking.

8
03

Discussion

Group cards by theme, discuss the most-voted items. Focus on patterns, not individual complaints.

5
04

Voting

Each team member gets 3–5 votes. Prioritize action items that will have the most impact on the next sprint.

2
05

Actions

Assign owners and due dates for top-voted action items. Link directly to GitHub issues or Linear tickets.

Best practices
  • ✓Keep the entire retro under 30 minutes — momentum matters more than exhaustive discussion.
  • ✓Vote before discussing to surface what the team collectively cares about.
  • ✓Assign owners and due dates to every action item — unowned actions never happen.
  • ✓Use anonymous mode for the Stop column to surface honest feedback.
  • ✓Link outcomes back to sprint goals so the team sees progress over time.
  • ✓Rotate the facilitator role each sprint to share ownership.
Common mistakes
  • ✗Skipping the Outcomes column — celebrating wins is what makes this format motivational.
  • ✗Letting one person dominate discussion — use round-robin or timed turns.
  • ✗Too many action items — pick 2-3 maximum and execute them well.
  • ✗No follow-up on previous sprint's actions — start each retro reviewing last sprint's commitments.
  • ✗Treating it as a complaint session — keep the focus on forward-looking improvement.
  • ✗Running without a facilitator — someone needs to keep time and guide the flow.
About this template

What is a Mountain Climb retrospective?

The Mountain Climb retrospective is a powerful Agile retrospective format designed for teams that thrive on progress and goal-oriented reflection. Unlike traditional retrospectives that focus primarily on problems, Mountain Climb frames each sprint as a climb — with a clear summit (your goal), the path you took (what worked), the obstacles you encountered (what didn't), and the gear you'll need for the next ascent.

Originating from the software engineering community as an evolution of Start/Stop/Continue, Mountain Climb adds two critical columns — Goals and Outcomes — that make it uniquely effective for Scrum teams running sprint-based work. The format was popularized by engineering leaders who found that traditional retrospectives focused too heavily on negative feedback without enough emphasis on tracking progress toward larger objectives.

The psychology behind Mountain Climb is rooted in progress theory. Humans are motivated more by a sense of forward momentum than by avoiding problems. By structuring the retro around a climb metaphor, teams naturally shift from blame-oriented thinking to growth-oriented thinking. Each column represents a phase of the journey: Outcomes acknowledge where you've been, Start/Stop/Continue define your immediate actions, and Goals point to where you're going.

FAQ

Frequently asked questions

What is a Mountain Climb retrospective?

Mountain Climb is a goal-oriented retrospective format that frames each sprint as a climb. Columns include Start, Stop, Continue, Goals, and Outcomes — helping teams reflect on progress and plan forward.

How long should a Mountain Climb retro take?

20–30 minutes is the sweet spot. The format is structured so teams move efficiently through each column without getting stuck on any single topic.

Who should facilitate a Mountain Climb retrospective?

Anyone on the team can facilitate. Rotate the role each sprint — it builds facilitation skills across the team and brings fresh perspectives to the process.

Is Mountain Climb good for remote teams?

Yes — LetRetro's async and real-time modes make Mountain Climb ideal for distributed teams. Team members can add cards in their own time, then vote and discuss synchronously.

Can I run Mountain Climb asynchronously?

Absolutely. LetRetro supports async retrospectives where team members add cards throughout the day, vote asynchronously, and the AI generates a summary for discussion.

What's the difference between Mountain Climb and Sailboat?

Mountain Climb is forward-looking and goal-oriented (Start, Stop, Continue, Goals, Outcomes), while Sailboat uses a journey metaphor with Anchors (what's holding us back), Wind (what pushes us forward), and Rocks (risks ahead).

What's the difference between Mountain Climb and Start/Stop/Continue?

Mountain Climb extends Start/Stop/Continue with Goals and Outcomes columns, making it better suited for teams that want to track progress toward larger objectives across sprints.

Can AI summarize Mountain Climb results?

Yes — LetRetro's AI automatically generates summaries and extracts action items from every retrospective, helping you spot trends and track follow-through.

Run your mountain climb retrospective

Free forever plan. Start running better retrospectives in under 2 minutes.

Get Started Free