🍟🥔 Crisp Adventures
Welcome to the crunchy world of crisps! Let's explore the flavors of our project by examining what we savor, discard, and improve. Together, let's ensure our work becomes the ultimate satisfying crunch.
Template Columns
🗑️ Stale Chips
Identify tasks or approaches that have become stale and aren't adding value.
Base column: Drop✨ New Flavors
Suggest new ideas or approaches that could spice up our workflow.
Base column: Add👍 Classic Crunch
Celebrate tried-and-true practices that continue to deliver great results.
Base column: Keep🛠️ Better Recipe
Discuss ways to refine or adjust our processes for better outcomes.
Base column: ImproveAbout this template
The Crisp Adventures retrospective uses a playful and engaging way to evaluate a project's performance, encouraging teams to drop stale practices, brainstorm fresh ideas, celebrate successes, and improve processes.
When to use this template
Use this format when the team needs a creative and engaging way to reflect on a project or sprint, especially if project dynamics need to be reinvigorated.
How to facilitate
Explain the purpose of the retrospective and introduce the columns: Stale Chips (tasks to drop), New Flavors (innovative ideas), Classic Crunch (strengths), and Better Recipe (areas for improvement).
Provide team members with 5–10 minutes to reflect and write feedback under each column.
Facilitate a group discussion by reviewing each column, clustering similar ideas, and ensuring everyone has the chance to contribute.
Discuss key insights and prioritize action items from the columns, with particular focus on practical application.
Conclude the session by summarizing the outcomes and thanking the team for their participation.
Pro Tips
Encourage participants to think beyond immediate tasks and consider long-term processes.
Use the whimsical theme to engage the team and foster open communication.
Consider using prompts for each column to stimulate thoughts and ideas.
Allocate time for individual reflection and group discussion to balance perspectives.
Revisit issues and actions from earlier retros for continuity.
FAQ
What if the team struggles to come up with new ideas under 'New Flavors'?
Encourage lateral thinking and consider using prompts or examples to stimulate creativity.
How can I ensure quieter team members participate?
Use techniques like anonymous idea submission tools to make contributions easier for everyone.
What should I do with the outcomes of this retrospective?
Document key takeaways and action items in a shared tracker for follow-up.
What preparation is needed before running this session?
Familiarize yourself with the structure and ensure participants are aware of the retrospective's objectives.
At a glance
- Duration
40–60 minutes
- Team Size
4-12 people
- Columns
4 columns
- Base Format
Drop, Add, Keep, Improve
Tags
Ready to get started?
Use this template to run your next retrospective