How Blame Rolls Your Way in a Retro

The laws of blame physics

In most teams, blame doesn't follow "whoever broke it owns it" Newtonian mechanics. It follows three laws:

1. An incident needs a face. The team wants a story, and "one person messed up" is a much cleaner story than "the process, the schedule, and the review all failed." One owner completes the narrative.
2. Blame rolls downhill to the nearest body. Whose module it was, who was on call, who last touched that file — none of it matters. Whoever is closest to the scene looks most responsible.
3. Blame sticks to whoever doesn't push back. The person who mumbles "I guess I share some responsibility" magically becomes the primary owner. The person who says "let me walk through the timeline" is oddly left alone.

Once you see the three laws, you understand: the blame rolls to you not because you're wrong, but because you're standing on the slope.

The right move: hand over a timeline, not an apology

When it's genuinely not yours, remember the formula: fact + time + person.

"At 14:03 my commit only touched config parsing; at 14:20 branch B merged the routing change; at 14:31 I approved the deploy — that part I'll own, though the change window had already passed."

Notice the last line: own a process edge even when the core blame isn't yours. The person who deflects everything looks guilty; the one who owns the paperwork while clearing the code is playing the high ground.

When you should own it

If it is your fault: own it. But own it properly:

• Own the fact, not the motive: "I merged it, I didn't test that branch" — fine. "I was careless" — no. Motives only get darker the more you explain them.
• Own this incident, not your identity: don't let one incident become someone's label for you.
• Follow the ownership with a fix: rollback plan, hotfix ETA, retro action items. The incident passes; how you handled it stays.

One honest line

The actual function of a retro is rarely "prevent recurrence" — it's "close this incident with an owner." Once you see that, you'll stop chasing fairness in the meeting. Fairness lives in the timeline, not in the emotions.

Next time the blame starts rolling, dump the situation into Saynook. It'll help you read the slope before you're standing at the bottom of it.