Treasure

What is our ultimate treasure?

Launching our product with zero critical bugs by Q3
Achieving 95% customer satisfaction rating
Building a self-organizing team that can handle any challenge
Rocks

What risks and issues could we face?

Limited access to senior stakeholders for big decisions
Technical debt in our legacy systems
Team members working remotely across different time zones
Navigation

What will guide our way forward?

Weekly progress check-ins to keep us on track toward our goals
Clear definition of done for all deliverables
Regular customer feedback sessions to validate direction
Crew

What skills and tools do we need?

DevOps expertise to improve our deployment pipeline
Better collaboration tools for remote work
Training in new technologies we plan to adopt

What is the Treasure Hunt Retrospective?

The Treasure Hunt Retrospective is a planning session dressed as an expedition. Your team agrees on the treasure it's after, then works out what could sink the voyage and what it needs to get there. The board has four columns. Treasure is the goal, described specifically enough that you'll know when you've reached it. Rocks are the risks and issues that could get in the way, from technical debt to a third-party dependency. Navigation covers the practices and principles that will keep you on course, and Crew is for the skills and tools the team has or still needs. Because it looks forward more than back, it works best at the start of a project, a new quarter or any planning session where the team needs to agree on a target. Naming the rocks and the crew gaps early gives you a short list of risks to manage and resources to ask for before the work begins.

Treasure Hunt Retrospective Format

Treasure

What is our ultimate treasure?

Ask the team what it's really after and what success would look like. Push for specifics, such as a date, a number or a customer outcome, so the treasure is something you'll recognize when you reach it.

Rocks

What risks and issues could we face?

List the obstacles that could slow or stop the team, technical and non-technical. Naming risks early gives you time to plan around them.

Navigation

What will guide our way forward?

Identify the principles, practices and check-ins that will keep the team on course, such as a clear definition of done or regular customer feedback.

Crew

What skills and tools do we need?

Look at the skills, tools and resources the team already has and the ones it's missing. Gaps here often turn into the most concrete actions, like training or a request for help.

When to use this retrospective

  • At the start of a new project or initiative that needs a clear goal and an early look at risks
  • During a strategic planning session, when you want the whole team involved in setting direction
  • When the team needs to agree on its objectives and what it will take to reach them
  • When you want a planning session that people remember

Suggested icebreaker questions

  • If you could discover any treasure in the world, what would it be and why?
  • What's the best thing you've ever found by accident?

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

Ideas and tips for your retrospective meeting

  • Use maritime or adventure language through the session to keep the theme going
  • Keep all four columns in view so people can see how the rocks, navigation and crew connect to the treasure
  • Go around the room for each column so everyone contributes
  • Keep a parking lot for detailed discussions that would derail the main session
  • Record each action with an owner and a timeline
  • Finish by drawing a treasure map that shows the path forward

Frequently asked questions

What is a Treasure Hunt retrospective?
It's a planning-focused retrospective that frames your team's goal as a treasure expedition. The board has four columns: Treasure (the goal), Rocks (risks), Navigation (what guides you) and Crew (skills and tools).
How do you run a Treasure Hunt retrospective?
Agree on the treasure first, then give everyone a few minutes to add notes privately to Rocks, Navigation and Crew. Group and vote, then turn the biggest risks and crew gaps into actions with an owner.
When should a team use the Treasure Hunt retrospective?
Use it for strategic planning or goal setting, such as the start of a project or quarter, when the team needs to agree on a target and look ahead at what could get in the way.
Is it a retrospective or a planning session?
Both. It looks forward more than most retrospectives, so it works best when you're about to start something. To review a finished sprint, a backward-looking format like Start Stop Continue fits better.
How long does a Treasure Hunt retrospective take?
Plan for 60 minutes. Agreeing on the treasure can take a while, so timebox that discussion before moving on to the other columns.
Ready to run this retrospective?Try this retrospective live