The Retrospective Prime Directive is a statement read at the beginning of retrospectives to establish psychological safety and prevent blame. Created by Norm Kerth, it sets the foundation for honest, constructive discussions by reminding everyone that the goal is improvement, not finger-pointing.

If your retrospectives sometimes turn into blame sessions, or team members seem hesitant to share honestly, the Prime Directive can help transform your meetings.

The Retrospective Prime Directive: Full Text

“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.”

— Norm Kerth, Project Retrospectives: A Handbook for Team Reviews

Read this statement aloud at the start of your retrospective. Let it sink in. It changes how people approach the discussion.

Why the Prime Directive Matters

It Prevents Blame

Without the Prime Directive, retrospectives can devolve into:

• “Why didn’t you finish on time?”
• “Who broke the build?”
• “If only X had done their job…”

With the Prime Directive, discussions shift to:

• “What made finishing on time difficult?”
• “What caused the build to break?”
• “What systemic issues contributed to this?”

It Creates Psychological Safety

Psychological safety—the ability to speak up without fear of punishment—is essential for effective retrospectives. The Prime Directive explicitly establishes this safety.

When people believe they won’t be blamed, they:

• Share honest feedback
• Admit mistakes openly
• Discuss sensitive topics
• Contribute without fear

It Focuses on Systems, Not Individuals

The Prime Directive assumes people did their best given their circumstances. This shifts focus from individual failures to systemic issues:

Blame Focus	System Focus
”John should have tested more"	"Our testing process has gaps"
"Sarah missed the deadline"	"Our estimation process needs work"
"The new hire broke production"	"Our onboarding doesn’t cover deployment safety”

Systems can be fixed. Blaming individuals just creates defensiveness.

It Acknowledges Reality

The Prime Directive recognizes that people operate under constraints:

• “What they knew at the time” — We can’t expect perfect decisions with incomplete information
• “Their skills and abilities” — Not everyone has the same expertise
• “The resources available” — Time, tools, and support vary
• “The situation at hand” — Context matters enormously

This nuanced view prevents simplistic “they should have known better” judgments.

📖 Explore more: our retrospective questions guide

How to Use the Prime Directive

When to Read It

Read the Prime Directive:

• At the start of every retrospective
• After setting the stage but before gathering data
• Especially after difficult sprints or failures
• When new team members join
• When you sense blame creeping into discussions

How to Read It

Don’t just mumble through it. Make it meaningful:

1. Pause before reading to get attention
2. Read slowly and clearly
3. Make eye contact with the team
4. Pause again after reading to let it sink in
5. Ask if everyone can commit to this mindset

Example facilitation:

“Before we begin, I want to read the Retrospective Prime Directive. This sets the tone for our discussion.

[Read the directive slowly]

Can everyone commit to approaching today’s discussion with this mindset? We’re here to improve our process, not to assign blame. [Wait for acknowledgment]“

What to Do When Blame Emerges

Even with the Prime Directive, blame can creep in. When it does:

Redirect gently:

“I hear frustration about that situation. Can we explore what systemic factors contributed to it?”

Reference the directive:

“Let’s remember the Prime Directive—assuming good intentions, what circumstances made this outcome more likely?”

Reframe the question:

“Instead of ‘who,’ let’s ask ‘what’—what in our process allowed this to happen?”

The Prime Directive in Different Situations

After a Major Failure

When something went seriously wrong, the Prime Directive is even more important:

“I know this sprint was difficult. Before we discuss what happened, I want to remind us of the Prime Directive. Everyone did their best given the circumstances. Our goal today is to understand what systemic changes can prevent this in the future.”

With New Team Members

New members may not know the Prime Directive or trust that it’s genuine:

“For those new to our retros, we always start with the Prime Directive. This isn’t just words—we genuinely believe it. You’ll see that we focus on processes and systems, not blaming individuals.”

When Trust Is Low

If your team has been through blame-heavy meetings before:

“I know we haven’t always lived up to this, but I’m committing to it today. The Prime Directive means we focus on improving our work, not criticizing each other. Can we all agree to try?”

In Written Form

For async retrospectives, include it in writing:

Before adding your feedback, please read:

“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.”

Keep this in mind as you share your thoughts.

Common Questions About the Prime Directive

”What if someone genuinely didn’t try their best?”

The Prime Directive doesn’t mean ignoring performance issues. It means:

1. Retrospectives focus on systems and processes
2. Performance conversations happen separately, one-on-one
3. Root cause is often systemic even when it seems individual

If someone consistently underperforms, that’s a management conversation—not a retrospective topic.

”Does this mean we can’t discuss what went wrong?”

Absolutely not! You should discuss failures—just without blame. Compare:

With Blame	Without Blame
”The release failed because QA didn’t catch the bug"	"The release failed because our QA process missed this type of bug. How do we improve?"
"We missed the deadline because John took too long"	"We missed the deadline because we underestimated complexity. How do we estimate better?"

"What if people take advantage and never improve?”

The Prime Directive applies to retrospectives. It doesn’t mean:

• No accountability ever
• No performance management
• No feedback on individual work

It means: “In this meeting, we focus on systems.” Individual development happens through other channels.

”Is the Prime Directive always appropriate?”

Almost always. The rare exception might be:

• Ethical violations (which are HR issues, not retro topics)
• Legal matters (which require different processes)
• Deliberate sabotage (extremely rare)

For normal work situations, the Prime Directive applies.

The Science Behind the Prime Directive

Fundamental Attribution Error

Humans tend to attribute others’ mistakes to character (“they’re careless”) rather than circumstances (“they were rushed”). This is called the fundamental attribution error.

The Prime Directive counteracts this by explicitly asking us to consider circumstances.

Psychological Safety Research

Google’s Project Aristotle found that psychological safety was the #1 factor in high-performing teams. Teams where members felt safe to take risks and admit mistakes outperformed those where blame was common.

The Prime Directive directly creates this safety.

Blameless Postmortems

Tech industry practices like blameless postmortems (popularized by companies like Google and Etsy) follow similar principles:

• Focus on systems, not individuals
• Assume good intentions
• Look for process improvements
• Create safety for honest discussion

The Prime Directive predates these practices but shares the same foundation.

Adapting these questions for a distributed team? Our remote retrospectives guide covers virtual facilitation.

Creating a Blameless Culture

The Prime Directive works best as part of a broader blameless culture:

In Retrospectives

• Read the Prime Directive
• Redirect blame when it occurs
• Thank people for honest sharing
• Focus action items on systems

Beyond Retrospectives

• Handle performance issues privately
• Celebrate learning from mistakes
• Model vulnerability as leaders
• Reward process improvements over hero culture

Leadership Behavior

• When things go wrong, ask “what” not “who”
• Share your own mistakes openly
• Thank people for surfacing problems
• Never punish messengers

Prime Directive Variations

Some teams adapt the Prime Directive. Here are variations:

Shorter Version

“We believe everyone did their best given what they knew and had at the time.”

Question Format

“Can we agree that everyone here did their best given their circumstances? Our goal today is to improve our systems, not assign blame.”

Team-Written Version

Some teams write their own version that feels more authentic to them.

Visual Reminder

Display the Prime Directive on a poster or digital background throughout the retrospective.

Related Concepts

• Psychological Safety in Retrospectives — Creating safe environments
• Retrospective Anti-Patterns — Common mistakes including blame
• How to Facilitate a Retrospective — Facilitation techniques

Frequently Asked Questions

What is the Retrospective Prime Directive?

The Prime Directive, written by Norm Kerth, states: “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.”

Should you read the Prime Directive at every retrospective?

Not necessarily every time — but always for new teams, after difficult sprints, or when you sense blame creeping in. Experienced teams often internalize the principle but benefit from periodic reminders when tensions are high.

Does the Prime Directive mean you cannot discuss problems?

No. The Prime Directive means you discuss problems without blaming individuals. You focus on systems, processes, and situations — not on who messed up. It creates the safety needed for honest problem-solving.

Run Blameless Retrospectives with RetroFlow

Create a safe space for honest feedback. RetroFlow supports blameless retrospectives:

• ✅ Anonymous input — Share without fear
• ✅ Prime Directive prompt — Built-in reminder
• ✅ Focus on actions — Turn insights into improvements
• ✅ 100% free — No limits, no credit card
• ✅ No signup required — Start in seconds

Start Free Retrospective →

Summary

The Retrospective Prime Directive establishes the foundation for effective retrospectives:

“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.”

Read it at the start of every retrospective. Mean it. Redirect blame when it occurs. Focus on systems, not individuals. Build a culture where honest feedback leads to real improvement.

You Might Also Like

• how retrospectives evolved over time
• Psychological Safety in Retrospectives — Creating safe spaces
• How to Facilitate a Retrospective — Facilitation guide
• Sprint Retrospective Formats — 30+ format options
• What is a Sprint Retrospective? — Complete beginner’s guide