Skip to content
← Ritual Library

Milestone ritual

Blameless Retrospective

After any project or incident, the team reflects on what happened, what helped, what hindered and what they'll change — without blame.

Why it matters

Builds psychological safety and a learning culture by separating people from problems, so mistakes become sources of improvement instead of fear.

How to run it

  1. Set the prime directive. "Everyone did the best they could with what they knew at the time."
  2. Rebuild the timeline (10 min). What actually happened, in order?
  3. Silent writing (10 min). Everyone adds notes to four columns: Helped, Hindered, Surprised us, Ideas.
  4. Cluster and discuss (20 min). Group similar notes and talk through the biggest clusters.
  5. Commit to one or two changes with clear owners and a date to check back.

Watch out for

  • Leaders speaking first and anchoring the conversation
  • Ending with a long action list nobody owns — pick one or two changes

When not to use it

For HR or conduct issues — those need a separate, confidential process.

Keep exploring

Nudge

The Feedback Intervention Paradox

Feedback makes performance worse surprisingly often. Whether it was positive or negative barely matters — what matters is whether it points attention at the work or at the person.

2-minute read10 Oct 2026
Article

The “CC everyone” epidemic

Copying the boss “just in case” looks like transparency. It’s really a symptom of fear — and leaders can cure it one reply at a time.

8 Oct 2026
Nudge

The 19-Word Note

One sentence attached to critical feedback dramatically increased how many people acted on it — especially those who trusted the giver least.

2-minute read27 Aug 2026