Purpose

The Team Journey Retrospective maps the team's evolution over a longer period — a quarter, a release, or a project — as a journey with stages, milestones, and turning points. Unlike sprint-level retros, it takes a big-picture view of team development, helping identify long-term patterns, growth areas, and recurring obstacles.

At a glance

• Group size: 4–12 people
• Duration: 25 minutes
• Difficulty: Intermediate
• Facilitation style: Semi-structured
• Setting: Both / Remote-friendly

How to run

1. Draw a journey path (road, river, or trail) representing the time period under review.
2. Together, mark key milestones, achievements, and setbacks along the path (5 minutes).
3. Each person adds personal highlights and lowlights (5 minutes).
4. Walk through the journey together, discussing turning points and patterns (10 minutes).
5. Look ahead: what does the next stretch of the journey need? Define 1–2 actions (5 minutes).

Materials needed

• Large whiteboard or paper
• Sticky notes
• Markers (multiple colours)
• Timer

Pitfalls & common mistakes

• Trying to cover too long a period — cap at one quarter or one release.
• Only marking milestones without personal observations — the personal layer adds depth.
• Not looking forward at the end — a journey retro should inform the next leg.

Inclusion & accessibility

• New team members can mark when they joined and share their onboarding experience.
• Use a digital board for remote participants to contribute equally.
• Allow written and verbal contributions.

Variations

• Hero's Journey: map the team journey to Joseph Campbell's monomyth stages.
• Journey Map with Emotions: add an emotion curve alongside the journey path.
• Photo Journey: use actual photos or screenshots from the period for visual anchoring.

When NOT to use this

• For short sprints where a simpler retro format suffices.
• When the team is brand new and has no journey to map yet.

Source & further reading

• Agile coaching community practices.
• Retromat (retromat.org).