An Unexpected Journey Retrospective

Reflect on the surprises and detours of your team's adventure.

Try this retrospective live

Where We Set Out

What were our original goals and expectations?

We expected this feature to take two sprints and be a straightforward build.
Our goal was to launch before the end of the quarter with all the must-haves in place.
I assumed the requirements were locked and wouldn't change much.
Unexpected Detours

What surprises or obstacles knocked us off course?

A key dependency was delayed, forcing us to reshuffle the whole plan.
We hit an unexpected bug that took days to track down.
A team member went on leave and we had to redistribute work fast.
Treasures Discovered

What good things or wins did we find along the way?

We discovered a faster way to deploy that we'll keep using.
Pair programming during the crunch really lifted our quality.
The team rallied brilliantly when the deadline got tight.
Wisdom for the Next Quest

What lessons will we carry into our next adventure?

Let's build buffer time into estimates for unknown dependencies.
We should flag scope changes earlier and review them as a team.
Keep the new deployment process and document it for everyone.

What is an Unexpected Journey retrospective

Projects rarely follow the plan you started with. The Unexpected Journey retrospective treats your sprint or project as a quest and walks your team back along the route: where you set out to go, what knocked you off course, what you found on the way and what you'll take into the next one. Telling it as a story makes it easier to talk about the twists and the dragons without anyone feeling blamed. The board has four topics. Where We Set Out records the original goals and assumptions. Unexpected Detours covers the blockers and surprises that changed the path. Treasures Discovered is for the wins and good practices you picked up along the way, and Wisdom for the Next Quest turns all of it into actions. Because each person tells their own part of the story, quieter team members get a natural way in, and you often hear about problems a standard checklist would miss. Use it for an end-of-project review, after a milestone, or when your usual format has gone stale. You'll finish with a clear picture of how far the team came and a short list of things to do differently next time.

An Unexpected Journey retrospective format

Where We Set Out

What were our original goals and expectations?

This topic sets the baseline. Ask people to recall the plans, assumptions and hopes they had at the start, before anyone talks about what actually happened. The next two topics compare reality against this list.

Unexpected Detours

What surprises or obstacles knocked us off course?

Here the team names the blockers and surprises that changed the path. Treat them as part of the story so people feel safe sharing, and ask what caused each one rather than who. Look for the kinds of surprise that keep catching the team off guard.

Treasures Discovered

What good things or wins did we find along the way?

This topic is for the upsides: breakthroughs, useful discoveries and moments when the team worked well together. Ask people to recognize how things got done as well as what got done. Anything worth repeating should carry into the next topic.

Wisdom for the Next Quest

What lessons will we carry into our next adventure?

Turn the reflections into commitments here. Push for specific wording, such as "add a mid-project checkpoint," over general lessons like "communicate better." Give each action an owner before you close.

When to use this retrospective

  • At the end of a long or complex project, to compare how it actually unfolded with the plan.
  • After a major milestone, when you want to mark the wins and capture what you learned.
  • When your usual retrospective feels stale and the team needs a different way into the conversation.
  • After a turbulent stretch full of surprises or scope changes, to talk it through without blame.

Suggested icebreaker questions

  • If this project were a movie adventure, what genre would it be and why?
  • What's the most unexpected detour you've ever taken on a real-life trip?

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

Ideas and tips for your retrospective meeting

  • Open with a short story framing so everyone understands the quest before they add notes.
  • Give quieter team members their own turn to tell their part of the journey.
  • Treat detours as part of the story. Ask what caused them, not who.
  • Group similar notes to see which detours and treasures keep coming up before you vote.
  • Timebox each topic so you leave enough room for the Wisdom for the Next Quest actions.
  • Give every lesson an owner and a due date so it turns into a real change.

Frequently asked questions

How long does an Unexpected Journey retrospective take?
Most teams finish in 45 to 60 minutes. Larger teams or long projects may need up to 90 minutes so each part of the journey gets enough discussion.
When should I use this retrospective?
Use it at the end of a project, after a major milestone, or after a stretch full of surprises, when telling the story helps the team pull out the lessons and mark the wins.
How is it different from a standard retrospective?
Instead of plain columns like "what went well," it walks the team through a quest: goals, detours, discoveries and lessons. The story frame makes people less defensive about what went wrong.
Is it suitable for remote and distributed teams?
Yes. In TeamRetro everyone can add ideas, vote and discuss in real time or asynchronously, so the format works the same for co-located and remote teams.
How do I make sure it leads to action?
Leave dedicated time for Wisdom for the Next Quest, turn each lesson into a specific action with an owner, and review those actions at the start of your next retrospective.

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