← All playbooks
Tier 3: Dumpster Fire

How do you defend yourself when you're blamed for someone else's mistake?

The short answer

Reply with a dated timeline of what you did and when, without naming a culprit, and offer to help fix the actual problem. Correcting the record with evidence and no counter-attack is the only version of this that improves your standing rather than making it a two-person fight.

What's actually at stake

  • 01Whoever escalates emotionally loses, regardless of who was right.
  • 02A timeline is unarguable. An objection is arguable.
  • 03Volunteering for the fix reframes you as the adult in the thread.

Do

  • · Put the timeline in writing with timestamps and links.
  • · Correct in the same forum the blame landed in.
  • · Offer a concrete next step to actually resolve it.

Don't

  • · Do not name who you think did it.
  • · Do not use 'as I said in my earlier email'.
  • · Do not litigate it over DM where there is no record.

A draft you can send now

Adding some dates so we're all working from the same picture: spec was signed off 3 June (link), my build was merged 7 June and passed review, and the config change on 12 June came from outside my scope. Happy to be corrected if I've missed something. Either way, I can have a fix up by Thursday if that's useful — want me to take it?
Tailor this to my exact disaster →

Questions people actually ask

Should I reply in public or private?
Correct the record wherever the blame was stated. A private correction leaves the public version standing.
What if my manager believes it?
Ask for fifteen minutes and walk the timeline. Do not send it as a wall of text first.

Take it further

Related incidents

All CYABot tools →