The Prime Directive

When to use

First retro with a new team. First retro after an incident or a launch failure. Any retro you suspect will get personal. Skip it on the weekly cadence — repetition burns out the meaning. Skip it as a substitute for actually creating safety; reading the directive doesn't make a fear-based team blameless, it just gives the boss a script.

How it runs

1. Read it exactly

   Quote Kerth verbatim, not a paraphrase. The four-clause structure ('what they knew, their skills, the resources, the situation') is what does the work — losing any of the four loses the directive.

2. Pause for ten seconds

   After reading, pause. Don't move to the agenda. The pause is the difference between a frame and a throat-clear; without it the directive lands as a formality.

3. Reference it if needed

   If the conversation turns to a specific person's actions, name the directive — 'going back to what we read at the start' — and redirect to the system. Don't recite it again; that's hectoring.

4. Don't read it next time

   Read it the first time, the post-incident time, the after-a-difficult-launch time. Skip it the routine sprint after that. The directive is for moments that need it, not for every meeting.

Why it works

The four-clause structure is the mechanism. 'They did the best they could' on its own is a platitude. 'Given what they knew at the time, their skills and abilities, the resources available, and the situation at hand' is a checklist — every clause names a specific reason a person's behaviour was rational from inside their context. The directive works because it gives the team four specific ways to read a colleague's choice as reasonable.

Variations

• Read it once at the start of a new team's life — a single time, not at every retro.
• Print it on the wall, or at the top of the retro doc, instead of reading it aloud. Same frame, less ritual.
• After a major incident: read it before the post-mortem, not just before the retro. Sets the tone for the whole investigation.

Facilitator notes

If somebody in the room genuinely was negligent, the directive is not the right tool — it can be used to silence accountability, and that's its honest failure mode. Address the negligence in the appropriate forum (1:1, performance conversation) and run the retro about the systems that allowed it. The directive frames a blameless retro; it doesn't excuse harm.

Pitfalls

• Paraphrasing it. 'Let's be blameless today' is not the directive — it's a vibe. Read the four clauses or skip it.
• Reciting it weekly. Repetition empties the meaning; the team starts hearing it as throat-clearing.
• Using it to deflect a real accountability conversation. The directive is about systems, not a shield against feedback.
• Skipping the pause. Read-and-go makes it a formality; the ten seconds is what makes it a frame.

Remote tips

Pin the directive at the top of the retro doc or board so people can see it during the meeting, not just hear it read once. On video the spoken word disappears fast; the visible text catches the reference back to it later.

Example outputs

• The exact wording (Kerth, 2001): '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.'
• A facilitator's reference back, mid-retro: 'Going back to what we read — let's stay on the system that produced this, not on who was on-call.'
• A note at the top of the retro doc: 'Prime Directive applies. We are talking about systems today.'

FAQ

Should I read the Prime Directive before every retro?

No. First retro with a new team, first retro after an incident, first retro after a launch failure — yes. Every sprint — no. Repetition kills the meaning faster than any other failure mode.

Prime Directive or ESVP?

Different jobs. ESVP reads the room; the Prime Directive sets the frame. If you're running a hard retro, do both — ESVP at the top to read the temperature, the directive immediately after to set the rules of engagement.

What if someone genuinely was negligent?

The directive doesn't excuse it. Handle the accountability in the right forum (1:1, performance conversation) and use the retro to talk about the systems that allowed the negligence. The directive frames the conversation; it isn't a shield.

Related activities

Recommended use cases