Favorable Winds

What propelled the team forward this voyage?

Our daily stand-ups kept everyone aligned and we rarely got lost at sea.
Strong support from product owners meant clear priorities the whole sprint.
Pair programming sped us up and caught issues before they grew.
Stormy Seas

What slowed us down or threw us off course?

Unclear requirements meant we reworked the feature twice.
Too many context switches between projects drained our focus.
Flaky tests cost us hours chasing false failures.
Treasure Found

What wins and discoveries are worth celebrating?

We shipped the new dashboard ahead of schedule.
Discovered a simpler architecture that cut load times in half.
A teammate stepped up and mentored two juniors brilliantly.
Uncharted Horizons

Where should we explore or improve next?

Let's trial automated regression tests to catch issues earlier.
We should explore breaking the monolith into smaller services.
Schedule regular refinement to avoid mid-sprint surprises.

What is the Voyage to the New World retrospective?

The Voyage to the New World retrospective frames your team's recent work as an ocean crossing toward unexplored land. Your team looks back at what carried the ship forward and what nearly sank it, then decides where to sail next. The board has four columns. Favorable Winds covers the people, practices and circumstances that helped the team make progress. Stormy Seas is for the blockers and frustrations that slowed you down or threw you off course. Treasure Found collects the wins, lessons and pleasant surprises, and Uncharted Horizons looks ahead to the improvements and experiments you want to try. The expedition theme suits the end of a big project or a quarter, when there's a full voyage to look back on. Because the last column looks forward, the session ends with a course to follow, written as actions with an owner and a due date.

Voyage to the New World retrospective format

Favorable Winds

What propelled the team forward this voyage?

This column is for the tailwinds: the people, practices and circumstances that helped the team make progress. Ask what gave people momentum, from good collaboration to better tools, and note what's worth keeping.

Stormy Seas

What slowed us down or threw us off course?

Name the storms: the blockers, frustrations and headwinds that made the voyage harder. Keep the focus on situations, not individuals, so people can raise difficult issues, and look for patterns you can fix.

Treasure Found

What wins and discoveries are worth celebrating?

Celebrate what the team found along the way, including achievements, lessons and pleasant surprises. Recognize small wins as well as big milestones, and ask what made them happen so you can repeat it.

Uncharted Horizons

Where should we explore or improve next?

Chart the course ahead by naming opportunities, experiments and improvements for the next voyage. Encourage curiosity about new territory as well as fixes for past problems, and turn the best ideas into actions with an owner.

When to use this retrospective

  • When your team wants a story-driven alternative to its standard sprint retrospective.
  • At the end of a major project or milestone, to look back on the whole voyage.
  • When morale needs a lift and you still want to surface real issues.
  • With a newly formed team, to map its shared experience and agree on a direction.
  • For quarterly or release reviews where you want to balance celebration with planning ahead.

Suggested icebreaker questions

  • If you were an explorer in any era, which voyage would you most want to join and why?
  • What's one 'treasure' you'd want to bring back from a journey to a brand new world?

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

Ideas and tips for your retrospective meeting

  • Introduce the voyage metaphor at the start so everyone knows what belongs in each column.
  • Timebox each section so you reach the action planning in Uncharted Horizons.
  • Let people add ideas silently and independently before discussion, so quieter crew members are heard.
  • Keep the Stormy Seas discussion on situations and systems, not individuals.
  • Group similar ideas and dot-vote so you act on the issues that matter most.
  • Turn Uncharted Horizons ideas into actions with an owner and a due date.

Frequently asked questions

How long does a Voyage to the New World retrospective take?
Most teams finish in 45–60 minutes. Larger teams or longer review periods may need up to 90 minutes so each section gets time for discussion and action planning.
When should I use this retrospective instead of a standard one?
Use it when you want a change from routine retrospectives, especially at the end of a major project or milestone, or when morale could use a lift and you still want honest feedback.
How is it different from the Sailboat retrospective?
The Sailboat retrospective has the team picture one boat with wind, anchors and rocks around it. Voyage to the New World frames the work as a full expedition, with more room for celebrating discoveries in Treasure Found and planning where to go next in Uncharted Horizons.
What do the four sections mean?
Favorable Winds covers what helped progress, Stormy Seas covers what slowed the team down, Treasure Found celebrates wins and lessons, and Uncharted Horizons looks ahead to improvements and opportunities.
Can remote and distributed teams run this retrospective?
Yes. In TeamRetro everyone adds ideas independently and at the same time, then the team groups, votes and discusses together, so it works for remote, hybrid and co-located crews.
How do I make sure the retrospective leads to action?
Give Uncharted Horizons real time and turn the top ideas into specific actions with an owner and a due date, so the next voyage benefits from this one.
Ready to run this retrospective?Try this retrospective live