Let's discuss

What should we talk about?

I've noticed our deployment process is causing delays in delivery
The new collaboration tools aren't being used consistently
Our sprint planning meetings could be more efficient
Let's change

What areas of change could we pursue?

We could automate our deployment pipeline
Let's establish clear guidelines for tool usage
We should create a new sprint planning template
Let's try

What should we try or experiment with?

Try a new deployment tool for two sprints
Test weekly tool training sessions for one month
Pilot a 30-minute sprint planning format

What is the Pathfinder Retrospective?

The Pathfinder retrospective is a forward-thinking approach that helps teams chart their course toward improvement and innovation. By focusing on discussion, change, and experimentation, this format encourages teams to explore new possibilities and create actionable paths forward. This retrospective format is particularly effective for teams who want to break out of established patterns and discover fresh approaches to their work. It combines elements of strategic planning with practical experimentation, helping teams move from idea generation to concrete action. The three-phase structure guides teams through a natural progression: first exploring topics through open discussion, then identifying potential changes, and finally committing to specific experiments. This approach ensures that conversations lead to tangible outcomes and meaningful progress.

Pathfinder Retrospective Format

Let's discuss

What should we talk about?

This is the discovery phase where teams surface important topics and opportunities. Encourage participants to share observations about processes, team dynamics, or challenges they've noticed. Keep the discussion open and ensure everyone has a chance to contribute their perspectives.

Let's change

What areas of change could we pursue?

Guide the team in identifying specific changes that could address the discussed topics. Focus on realistic and actionable changes that the team has the power to implement. Help the team prioritize changes based on potential impact and feasibility.

Let's try

What should we try or experiment with?

Help the team convert their change ideas into concrete experiments. Each experiment should have a clear goal, timeline, and success criteria. Encourage small, manageable experiments that can provide quick learning opportunities.

When to use this retrospective

  • When the team feels stuck in current practices and needs fresh perspectives
  • During periods of organizational change when new approaches are needed
  • When you want to encourage innovation and experimental thinking
  • After identifying recurring issues that require new solutions

Suggested icebreaker questions

  • What's the most interesting experiment or new approach you've tried recently, either at work or in your personal life?
  • If you could instantly change one thing about how we work together, what would it be?

Ideas and tips for your retrospective meeting

  • Keep experiments small and timeboxed to reduce risk and increase learning opportunities
  • Ensure each experiment has clear success criteria and a defined evaluation period
  • Document both successful and unsuccessful experiments to build organizational knowledge
  • Encourage participation from all team members, as diverse perspectives lead to better experiments
  • Follow up on experiments in subsequent retrospectives to track progress and adjust as needed

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