The Prime Directive

What it is

The Prime Directive is one paragraph from Kerth's 2001 book, read aloud at the start of a retro to set the rules of engagement: everyone did the best job they could with what they had. It's not a ritual and it's not a vibe — it's a working assumption that keeps the conversation about systems instead of individuals. The four-clause structure (what they knew, their skills, the resources, the situation) is the directive; the paraphrase isn't. This category exists with one activity in it because the directive is the load-bearing frame for half the other formats in the catalogue. Sailboat, pre-mortem, post-incident retros — all of them collapse into blame without it. Putting it in its own category isn't padding; it's giving the frame the visibility it earns.

When to use

Read it the first time with a new team. Read it before a hard retro — post-incident, post-launch failure, after an argument. Skip it on the weekly cadence; a directive recited every sprint stops being a directive and becomes a throat-clear. Skip it when somebody on the team genuinely was negligent — the directive frames a blameless retro, it doesn't excuse accountability. And read it verbatim from Kerth's text, not the paraphrase your retro tool ships with; the four-clause structure is the directive, the summary version is decoration.

Which one to pick

First retro with a new team

Read the directive aloud, exactly. Pause for ten seconds. Then start.

First retro after an incident or launch failure

Read it again. Reset the frame before the conversation starts — the room walked in with a story about who's at fault.

Routine sprint retro number ten

Skip it. A directive recited weekly stops being a directive and becomes a throat-clear.

Post-mortem on a real failure with a real cause

Read it. Then run Fishbone or Five Whys — the directive is what keeps the technique from collapsing into blame.

Common mistakes

• Paraphrasing the directive. The four-clause structure is the directive — 'what they knew, their skills, the resources, the situation.' The summary version your tool ships with isn't the same thing.
• Reading it every sprint. Recited weekly, the directive stops landing. Save it for retros that need the reset.
• Treating it as a vibe rather than a working assumption. It's a rule about where to point the conversation, not a feeling to invoke.
• Using it to excuse genuine negligence. The directive frames a blameless retro; it doesn't bypass accountability when someone actually shipped the wrong thing on purpose.
• Skipping it on the post-incident retro. That's the meeting where the room walked in with a story about who's at fault — that's exactly when you need the frame.

All the prime directive