What did we do well?

What achievements are you most proud of from this period?

We delivered all our sprint commitments ahead of schedule this time.
Our communication with stakeholders improved significantly after implementing weekly updates.
The pair programming sessions helped us solve complex problems more efficiently.
What did we learn?

What insights or discoveries will you carry forward?

Breaking down the authentication feature into smaller tasks made it more manageable.
I discovered a more efficient way to handle database migrations that reduced downtime.
We learned that early stakeholder involvement prevents major rework later.
What should we do differently?

What changes would improve our performance next time?

We should establish clearer acceptance criteria before starting development work.
I think we need to allocate more time for code reviews to maintain quality.
Let's create a shared glossary to ensure we're all using the same terminology.
What still puzzles us?

What questions or uncertainties remain unresolved?

I'm still not clear why the performance issues only appear in the production environment.
How can we better estimate tasks that involve external dependencies?
Why do our velocity metrics fluctuate so dramatically between sprints?

What is the Prime Directive Retrospective?

The Prime Directive Retrospective, based on Norm Kerth's groundbreaking work in project retrospectives, creates a safe environment for teams to reflect honestly on their performance without blame or judgment. This powerful format centers around Kerth's original four questions that encourage teams to examine their experiences from multiple perspectives. At its core, this retrospective acknowledges that team members did the best they could with the knowledge, skills, and resources available to them at the time. By starting with this fundamental assumption, the Prime Directive creates psychological safety that allows for more honest and productive conversations about what happened and why. Teams can explore successes, challenges, insights, and opportunities for growth without defensiveness. The Prime Directive Retrospective is particularly valuable for teams dealing with challenging projects or difficult transitions, as it balances critical analysis with empathy. By focusing on learning rather than blame, teams can identify actionable improvements while preserving team cohesion and trust. Kerth's approach has become a cornerstone of effective retrospectives across industries because it consistently delivers meaningful insights that drive continuous improvement.

Prime Directive Retrospective format

What did we do well?

What achievements are you most proud of from this period?

This topic focuses on celebrating successes and identifying positive patterns. Encourage team members to recognize both large accomplishments and small wins. Look for recurring themes that might indicate team strengths worth leveraging in the future.

What did we learn?

What insights or discoveries will you carry forward?

This topic helps capture knowledge gained through experience. Encourage team members to share both technical learnings and process insights. These learnings often represent valuable intellectual capital that can benefit future work and other teams.

What should we do differently?

What changes would improve our performance next time?

This topic focuses on identifying specific, actionable improvements. Guide the team to think about concrete changes rather than vague aspirations. Look for patterns that might indicate systemic issues rather than one-off problems.

What still puzzles us?

What questions or uncertainties remain unresolved?

This topic captures open questions and unresolved issues that may need further investigation. These items often represent risks or opportunities that deserve attention. Consider assigning owners to research key puzzles before the next retrospective.

When to use this retrospective

  • After completing a significant project milestone or release to capture learnings while they're still fresh.
  • When the team has experienced challenges or setbacks and needs a blame-free way to discuss what happened.
  • For teams that are new to retrospectives, as the structure provides clear guidance while encouraging meaningful reflection.
  • When team trust needs rebuilding, as the Prime Directive's emphasis on assuming positive intent helps create psychological safety.

Suggested icebreaker questions

  • If you could have one superpower to help the team perform better, what would it be and why?
  • What's one unexpected thing you learned during our last work cycle that surprised you?

Ideas and tips for your retrospective meeting

  • Begin by reading Norm Kerth's Prime Directive aloud: 'Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.'
  • Consider addressing the 'What still puzzles us?' question last, as it often builds on insights from the other questions and can help identify areas for future exploration.
  • Encourage participants to provide specific examples rather than generalizations to make the discussion more concrete and actionable.
  • If the team seems hesitant to share, try a round-robin approach where each person contributes at least one item to each category.
  • After gathering all reflections, prioritize the items in 'What should we do differently?' to create a focused improvement plan with clear owners and timelines.

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