Supplies

What kept us going and fuelled our progress?

Our daily stand-ups kept everyone aligned and energised throughout the sprint.
The new CI pipeline saved us hours of manual testing.
Strong support from the product owner meant we never lacked direction.
Blizzards

What storms slowed us down or blocked our path?

Constant context switching between projects killed our focus.
Unclear requirements forced us to redo work twice.
A flaky staging environment ate up a whole day of debugging.
Icebergs

What hidden risks could threaten us ahead?

Our growing tech debt in the payments module could slow future releases.
Only one person understands the legacy authentication code.
We're relying on a third-party API with no fallback plan.
North Star

What goal should keep us oriented going forward?

Reduce our average bug resolution time by half next sprint.
Ship the new onboarding flow that customers have been asking for.
Pay down the biggest chunk of tech debt before adding new features.

What is the Arctic Expedition retrospective

Embark on a chilly adventure where your team charts its course across uncharted frozen terrain. The Arctic Expedition retrospective uses the metaphor of a polar journey to help teams reflect on what propelled them forward, what slowed them down, and how to survive the next leg of the trek. By framing the sprint or project as an expedition, teams can step back and view their progress with fresh perspective and a sense of shared adventure. This format works by guiding participants through four expedition-themed lenses: the supplies that kept them going, the blizzards that blocked their path, the icebergs that posed hidden risks, and the North Star that keeps them oriented toward their goal. Each lens prompts honest reflection while keeping the mood light and collaborative. The playful theme lowers defensiveness, encourages quieter team members to contribute, and turns problem-solving into a collective quest. The Arctic Expedition retrospective is ideal for teams looking to break out of standard retrospective formats and inject energy into their reflection sessions. It surfaces both achievements and obstacles, helps prioritise risks before they become crises, and aligns the team around a shared destination. Whether you are wrapping up a sprint, closing a project, or simply taking a seasonal pause, this themed retro keeps engagement high while delivering actionable insights.

Arctic Expedition retrospective format

Supplies

What kept us going and fuelled our progress?

Supplies represent the resources, strengths, and positive practices that sustained the team on its journey. Encourage participants to think about tools, support, skills, and habits that helped them keep moving forward. This is a great place to celebrate wins and recognise what to protect for the next expedition.

Blizzards

What storms slowed us down or blocked our path?

Blizzards are the obstacles, blockers, and disruptions that hindered the team's progress. Ask participants to name what made the journey harder and to be specific about the impact. Keep the tone constructive so the focus stays on the problem rather than on blame.

Icebergs

What hidden risks could threaten us ahead?

Icebergs represent the risks lurking beneath the surface that could derail the team if ignored. Prompt participants to surface concerns, technical debt, and looming dangers that are not yet causing problems but could. Identifying these early helps the team plan mitigations before they become crises.

North Star

What goal should keep us oriented going forward?

The North Star is the shared goal or direction the team wants to head toward next. Use this topic to align everyone on priorities and to translate reflections into a clear sense of purpose. Encourage actionable, inspiring statements that the team can rally behind.

When to use this retrospective

  • When you want to refresh a standard sprint retrospective with an engaging, themed format that re-energises the team.
  • When wrapping up a project or milestone and you want to capture both achievements and lurking risks.
  • When the team needs to proactively identify hidden dangers and technical debt before they cause problems.
  • When you want to align the team around a shared goal or direction after a period of intense work.
  • During seasonal or end-of-year sessions where a lighthearted theme boosts participation.

Suggested icebreaker questions

  • If you were heading on a real Arctic expedition, what one item would you absolutely have to pack?
  • Would you rather face a blizzard, a polar bear, or a week of total darkness, and why?

Ideas and tips for your retrospective meeting

  • Set the scene at the start by describing the expedition metaphor so everyone understands what each topic represents.
  • Timebox each column to keep momentum and prevent the discussion from drifting into one area for too long.
  • Encourage quieter members to contribute by inviting input on the Icebergs column, where surfacing hidden risks is everyone's job.
  • Group similar ideas together before voting so the team can prioritise the most important blizzards and icebergs.
  • Turn the North Star reflections into concrete action items with clear owners so insights translate into change.
  • Keep the tone playful but focused, ensuring blizzards are framed as challenges to solve rather than people to blame.

Frequently asked questions

How long does an Arctic Expedition retrospective take?
Most sessions run between 45 and 60 minutes for a team of five to eight people. Allow extra time if you have a larger group or many items to discuss in the Blizzards and Icebergs columns.
When should I use the Arctic Expedition retrospective?
It works well at the end of a sprint, project, or milestone, especially when you want a fresh, engaging format. It's also a great choice for seasonal or year-end sessions where a themed approach lifts participation.
How is it different from a standard Start, Stop, Continue retrospective?
The Arctic Expedition adds a dedicated focus on hidden risks through the Icebergs column and a forward-looking goal through the North Star. The expedition metaphor also keeps engagement high and lowers defensiveness compared to plain reflection prompts.
What do the four columns mean?
Supplies are the resources and strengths that helped you, Blizzards are the obstacles that slowed you down, Icebergs are the hidden risks ahead, and the North Star is the shared goal that keeps the team oriented.
Can remote and distributed teams use this retrospective?
Yes. In TeamRetro everyone can add ideas, group them, vote, and discuss in real time or asynchronously, making it ideal for co-located, hybrid, and fully remote teams.

New to retrospectives? Read our guide on how to run a retrospective →