⏳🔁 Groundhog Day Loop
Relive and revisit your team's daily cycle, just like the movie 'Groundhog Day'. Reflect on what’s repeating, what should change, and what should persist in your iterative journey towards excellence.
Template Columns
🌤️ Bright Beginnings
Highlight practices or experiments your team should begin to break free from monotony or bad habits.
Base column: Start❌ Broken Records
Identify repeated pitfalls, negative patterns, or ineffective actions the team should stop replaying.
Base column: Stop🔁 Keep the Rhythm
Celebrate patterns and practices that bring value and should continue in your agile journey.
Base column: ContinueAbout this template
Explore recurring patterns and identify changes to improve your team's process with the Groundhog Day Loop retrospective.
When to use this template
Use this retrospective to examine routine cycles within your team, addressing persisting issues and celebrating effective practices.
How to facilitate
Begin by setting the stage explaining the purpose of the retrospective: analyzing daily cycles within the team's operations and striving for meaningful improvement.
Present the three columns and explain their intent: Bright Beginnings for new opportunities, Broken Records to address recurring issues, and Keep the Rhythm to reinforce what is working.
Allocate time for team members to reflect and add their thoughts under each column. Encouraging reflective thinking about past iterations is crucial.
Group the notes in each column, identify common themes, and prioritize them based on team discussion.
Lead a structured discussion focusing on each prioritized theme, debating action items, and possible solutions.
Wrap up by recording agreed changes, distributing responsibilities for action items, and reflecting briefly on how addressing these points feels for the team.
Pro Tips
Encourage open sharing by emphasizing a non-judgmental space.
Use storytelling to help illustrate cases of Broken Records for better context.
Rotate facilitators to bring new perspectives to discussions.
FAQ
What if the team struggles to identify "Broken Records"?
Prompt with examples or revisit recent feedback or sprint reviews for cues about potential repeated issues.
How do we ensure continuity in addressing these patterns?
Document action items clearly, assign responsibilities, and review progress in the next retrospective.
At a glance
- Duration
40-60 min
- Team Size
5-12 people
- Columns
3 columns
- Base Format
Start, Stop, Continue
Tags
Ready to get started?
Use this template to run your next retrospective