Home Runs

What were some great outcomes?

Successfully launched the new feature ahead of schedule!
Our customer satisfaction scores hit an all-time high this quarter
The new onboarding process reduced training time by 50%
Strikes

What did we miss?

We could have communicated the deployment schedule better
Missed including QA team in initial planning sessions
Documentation updates fell behind sprint work
Curveballs

What was tricky?

The sudden requirement change threw off our sprint planning
Unexpected server downtime affected our testing schedule
Three team members got sick during critical project phase
Batter Up

What should be our next play?

Let's implement weekly knowledge sharing sessions
Create a backup plan for critical system dependencies
Schedule regular cross-team sync meetings

What is the Baseball Retrospective?

The Baseball Retrospective is an engaging way to reflect on team performance using America's favorite pastime as a metaphor. Drawing parallels between baseball and project delivery, this format helps teams identify successes (home runs), missed opportunities (strikes), challenges (curveballs), and future strategies (batting up). This retrospective format makes feedback sessions more approachable and fun by leveraging familiar baseball terminology. It encourages team members to think about their work in terms of hits, misses, and upcoming plays, creating a playful atmosphere while maintaining professional focus. Originally adapted from sporting metaphor retrospectives, this format works particularly well with teams who enjoy sports analogies or need a fresh perspective on their regular retrospective meetings.

Baseball Retrospective Format

Home Runs

What were some great outcomes?

Home runs represent major successes and achievements. Encourage participants to celebrate both individual and team victories, no matter how big or small. This helps build confidence and identifies what's working well.

Strikes

What did we miss?

Strikes represent missed opportunities or areas where we fell short. Frame these as learning opportunities rather than failures. Focus on identifying patterns and systemic issues rather than individual mistakes.

Curveballs

What was tricky?

Curveballs represent unexpected challenges or obstacles. Help the team identify both internal and external factors that made their work more difficult, and discuss how to better prepare for similar situations in the future.

Batter Up

What should be our next play?

This forward-looking topic focuses on actionable improvements and next steps. Encourage specific, achievable suggestions rather than vague ideas. Help the team prioritize these actions based on impact and feasibility.

When to use this retrospective

  • When you want to make retrospectives more engaging for sports-minded team members
  • After completing a major project milestone or release to evaluate team performance
  • When the team needs a fresh perspective on their regular retrospective format
  • When you want to encourage more metaphorical thinking about successes and failures
  • When team morale needs a boost through a more playful retrospective format

Suggested icebreaker questions

  • If your last sprint was a baseball game, what position would you have played and why?
  • What's your favorite sports memory that taught you something about teamwork?

Ideas and tips for your retrospective meeting

  • Keep the baseball metaphor consistent but don't overdo it - focus on the core concepts rather than forcing every baseball term to fit
  • Consider using baseball sound effects or visuals to enhance the experience and make it more immersive
  • Rotate who 'pitches' topics first to ensure everyone gets a chance to lead the discussion
  • Use a 'dugout' approach where team members can take a moment to reflect before sharing
  • Keep a 'scorecard' of action items and follow up on them in the next retrospective
  • Ensure the baseball theme doesn't exclude team members who aren't familiar with the sport

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