There's a reason why Murphy's Law is so commonly acknowledged, though. When you've got a process like this that gets repeated over and over by a bunch of different people, you simply must recognize that that, if it's possible for someone to fuck up, then somebody will fuck up.
And a relatively straightforward corollary of that reality is that, when somebody fucks up, putting too much personal blame on them is pointless. If it weren't them, it would have been somebody else.
In other words, this "blame is due where blame is due" framing is mostly useful as a cop-out excuse that helps incompetent managers who've been skimping on quality controls and failsafes to shift the blame away from where it really belongs.
> There's a reason why Murphy's Law is so commonly acknowledged, though.
In particular, the original formulation of Murphy's Law. The folk version has morphed into "anything that can go wrong, will go wrong". But the original was "If there are two or more ways to do something and one of those results in a catastrophe, then someone will do it that way".
And a relatively straightforward corollary of that reality is that, when somebody fucks up, putting too much personal blame on them is pointless. If it weren't them, it would have been somebody else.
In other words, this "blame is due where blame is due" framing is mostly useful as a cop-out excuse that helps incompetent managers who've been skimping on quality controls and failsafes to shift the blame away from where it really belongs.