What is the Sherlock Retrospective?
The Sherlock Retrospective transforms team reflection into an engaging detective experience, inspired by the methodical problem-solving approach of literature's greatest detective, Sherlock Holmes. Using the power of deductive reasoning and careful observation, teams investigate their work processes, successes, and challenges. This format encourages participants to think like detectives, examining evidence (data and experiences), following clues (patterns and insights), and solving mysteries (challenges and opportunities). By framing retrospective discussions in investigative terms, teams can maintain objectivity while diving deep into complex issues. The structure promotes both analytical thinking and creative problem-solving, making it particularly effective for teams dealing with complex problems or seeking to understand root causes of recurring issues. The detective theme helps maintain engagement while ensuring thorough examination of team dynamics and project outcomes.
Sherlock Retrospective Format
Case closed
What did we solve?
Focus on completed challenges and successful outcomes. Encourage participants to share specific examples of problems solved and goals achieved. Help the team identify patterns in their successful problem-solving approaches.
Clues
What helped us on the way?
Guide the team in identifying tools, practices, and behaviors that contributed to their success. Look for both obvious and subtle factors that helped progress. Encourage discussion about how these helpful elements can be leveraged in the future.
Elementary
What have we learned?
Focus on key learnings and insights gained during the period. Encourage participants to think about both technical and process-related discoveries. Help the team articulate these lessons in a way that can guide future actions.
Puzzles
What remains a mystery?
Help the team identify ongoing challenges, unknowns, and areas needing investigation. Encourage them to frame these as opportunities for learning rather than just problems. Guide the discussion toward potential approaches for solving these mysteries.
When to use this retrospective
- When the team needs to investigate complex problems or recurring issues
- After completing a challenging project to understand what led to success or failure
- When you want to encourage deeper analytical thinking in your retrospectives
- When the team needs a fresh and engaging approach to problem-solving
Suggested icebreaker questions
- If you were a detective, what would be your signature method for solving cases?
- What's the biggest mystery you've solved in your professional life?
Ideas and tips for your retrospective meeting
- Encourage participants to bring evidence and observations to support their points, just like a detective would
- Use the 'detective' theme to maintain objectivity and avoid blame - focus on facts and patterns
- Allow sufficient time for 'investigation' - don't rush to conclusions without examining all the clues
- Keep a 'case file' of actions and insights to track progress over time
- Use probing questions to dig deeper into issues and uncover root causes
- Create a safe space where team members feel comfortable sharing their observations and theories
New to retrospectives? Read our guide on how to run a retrospective →
Related templates
A clear-cut way to identify successes and improvement areas
Quarterly Retrospective
Reflect, realign, and recharge your team every quarter.
SCOR Futurespective
Strategic planning framework to analyze future scenarios and prepare for what's ahead
Marketing Team Retrospective
Reflect, refine, and amplify your marketing campaigns together.