Arctic Expedition Retrospective

Spot the blizzards and hidden icebergs before your next sprint.

Try this retrospective live

Supplies

What kept us going and fueled our progress?

Our daily stand-ups kept everyone aligned and energized 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

The Arctic Expedition retrospective pictures your sprint or project as a polar trek. Your team looks at what kept it moving, what slowed it down, which dangers are hiding ahead and which goal should guide the next leg. Stepping into the expedition gives people some distance from the day-to-day, which makes it easier to see the whole route. The board has four topics. Supplies are the resources, strengths and habits that kept you going. Blizzards are the obstacles that blocked your path. Icebergs are the risks below the surface that haven't caused trouble yet but could, like knowledge held by one person or growing tech debt. North Star is the shared goal that keeps the team oriented. Icebergs is what sets this format apart, because it gets risks onto the board before they turn into crises. Use it to wrap up a sprint or project, or for a seasonal session when your team wants a change from standard formats. The theme keeps the mood light, and quieter team members often find it easier to raise a concern as an iceberg than as a complaint.

Arctic Expedition retrospective format

Supplies

What kept us going and fueled our progress?

Supplies are the resources, strengths and habits that kept the team going. Ask about the tools, support, skills and routines that helped. This is the place to celebrate wins and name what to protect on the next expedition.

Blizzards

What storms slowed us down or blocked our path?

Blizzards are the obstacles and disruptions that slowed the team down. Ask people to name what made the work harder and to be specific about the impact. Keep the focus on the problem, not on who was involved.

Icebergs

What hidden risks could threaten us ahead?

Icebergs are risks under the surface: concerns, technical debt and dangers that aren't causing problems yet but could. Ask everyone to add at least one, since people often see risks they haven't mentioned. Spotting them now gives the team time to plan around them.

North Star

What goal should keep us oriented going forward?

The North Star is the goal the team wants to head toward next. Use it to agree on priorities and turn the session into a clear direction. Ask for goals specific enough that you'll know when you've reached them.

When to use this retrospective

  • When you want to refresh a standard sprint retrospective with a themed format.
  • When wrapping up a project or milestone and you want to capture both achievements and the risks ahead.
  • When the team needs to surface hidden risks and technical debt before they cause problems.
  • When you need to agree on a shared goal after a period of intense work.
  • For a seasonal or end-of-year session where a lighter theme helps people join in.

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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Describe the expedition at the start so everyone knows what each topic stands for.
  • Timebox each topic so the discussion doesn't stall in one place.
  • Ask quieter members for Icebergs in particular, since spotting hidden risks is everyone's job.
  • Group similar ideas before voting so you can prioritize the biggest blizzards and icebergs.
  • Turn the North Star into concrete action items with clear owners.
  • Keep the tone light but focused, and treat blizzards as problems to solve, not people to blame.

Frequently asked questions

How long does an Arctic Expedition retrospective take?
Most sessions run 45 to 60 minutes for a team of five to eight people. Allow extra time for a larger group or a long list of blizzards and icebergs.
When should I use the Arctic Expedition retrospective?
Use it at the end of a sprint, project or milestone, especially when your team wants a change of format. It also suits seasonal or year-end sessions.
How is it different from a standard Start, Stop, Continue retrospective?
Start Stop Continue looks at behaviors to change. The Arctic Expedition adds a column for hidden risks (Icebergs) and a forward-looking goal (North Star), so you talk about what's coming as well as what happened.
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, vote and discuss in real time or asynchronously, so it works for co-located, hybrid and fully remote teams.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live