Pokémon Trainer's Journey Retrospective

Review your sprint as a trainer's journey, battles included.

Try this retrospective live

Pokémon We Caught

What wins and achievements did we capture this time?

We finally caught that legendary payment integration bug that's been evading us for weeks.
Shipped the new onboarding flow ahead of schedule. A shiny catch for sure.
Our pair-programming sessions leveled up the whole team's confidence.
Gym Battles We Fought

What challenges or obstacles did we battle along the way?

The deployment process knocked us out a few times before we figured out the fix.
Unclear requirements meant we kept rebattling the same scope discussions.
Too many context switches drained our HP across the week.
Badges We Earned

What new skills, lessons or insights did we gain?

Earned the 'Documentation Badge' by finally writing up our deployment runbook.
Learned that breaking stories down smaller made estimation way more accurate.
We discovered a faster way to run our test suite, and it's knowledge worth keeping.
The Next Route

Where do we go next and what actions will get us there?

Let's automate the deployment steps before the next sprint begins.
Set up a shared requirements review to avoid rebattling scope.
Plan to invest one day into fixing the flaky tests.

What is the Pokémon Trainer's Journey retrospective?

The Pokémon Trainer's Journey retrospective borrows the shape of a trainer's adventure from the games. Your team sets out on a sprint or project, catches some wins, fights its way through a few tough battles, picks up new skills and then decides where to head next. Most people know the structure already, which makes it quick to explain and easy to play along with. The board has four stages. Pokémon We Caught is for wins and achievements, from small bug fixes to major releases. Gym Battles We Fought covers the challenges and obstacles the team battled, like unclear requirements or flaky tests. Badges We Earned is for the skills and lessons gained, including the ones that came from setbacks. The Next Route turns all of that into a few specific actions with an owner. It suits teams that enjoy a bit of gaming nostalgia and want a break from their usual format, at the end of a sprint, a milestone or a release. Framing problems as battles to win makes them easier to name, and the Badges stage gives the team a moment to see how much it has learned.

Pokémon Trainer's Journey retrospective format

Pokémon We Caught

What wins and achievements did we capture this time?

This is the celebration stage. Ask people to list every Pokémon they caught, from small bug fixes to major feature releases, and to recognize individual wins as well as team ones. Leave room for shout-outs so everyone's contribution gets noticed, and keep the tone upbeat to start the retro on a good footing.

Gym Battles We Fought

What challenges or obstacles did we battle along the way?

Frame challenges as gym battles: tough encounters the team can win. Ask what made things hard, whether that was unclear requirements, technical debt or competing priorities. Keep it constructive, and look for the gym leaders the team keeps facing, because a recurring battle is a pattern worth fixing.

Badges We Earned

What new skills, lessons or insights did we gain?

Badges are the lessons and skills the team picked up along the way. Ask about new skills, better processes and "aha" moments, including ones that came out of setbacks. This stage helps the team see how far it has come.

The Next Route

Where do we go next and what actions will get us there?

This is where the team plots the next leg of the journey. Turn what came up in the earlier stages into specific actions and goals, with a name next to each one. Keep the number of commitments small so the team actually reaches the next town.

When to use this retrospective

  • When your team wants a themed break from its standard retrospective format
  • At the end of a sprint, project milestone or major release, to celebrate progress and plan ahead
  • For gaming communities, hackathon teams or any group that enjoys a game-style session
  • When you want the team to see setbacks as part of how it learns
  • When a difficult topic needs a lighter frame so people will talk about it

Suggested icebreaker questions

  • If you could have one Pokémon on your team this sprint, which would it be and why?
  • What's your team 'starter Pokémon', the strength you always rely on to get going?

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

Ideas and tips for your retrospective meeting

  • Set the scene at the start by reminding everyone they're trainers on a shared adventure
  • Timebox each stage so celebrating wins doesn't crowd out the actions and goals
  • Keep Gym Battles We Fought constructive and blame-free: talk about the obstacle, not the person
  • Invite shout-outs in Pokémon We Caught so quieter team members get recognized
  • Limit The Next Route to a few achievable commitments, each with a clear owner
  • Not everyone will know Pokémon, so keep the metaphors light and explain what each stage means

Frequently asked questions

What is a Pokémon Trainer's Journey retrospective?
It's a themed retrospective that frames your team's sprint as a trainer's adventure. You log the wins you caught, the gym battles you fought (challenges), the badges you earned (lessons) and the next route (actions).
How long does a Pokémon Trainer's Journey retrospective take?
Most teams finish in 45–60 minutes. That covers an icebreaker, brainstorming across the four stages, grouping and discussion, and agreeing on actions.
When should I use this retrospective format?
It works best at the end of a sprint, milestone or release, especially when you want a change of pace or need a lighter frame for a tough conversation.
Do my team members need to know Pokémon to take part?
No. The four stages map to wins, challenges, lessons and next steps, so anyone can take part fully without knowing the games.
How is this different from a standard sprint retrospective?
It covers the same ground as a typical retro, but the gaming theme frames progress as a journey with battles and badges. That makes it easier to talk about setbacks as something the team learned from.
How do I run this retrospective in TeamRetro?
Select the Pokémon Trainer's Journey template and invite your team. Work through the four stages by brainstorming, grouping ideas and voting on what matters most, then capture action items in TeamRetro.

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