[Extracted from
DontBlameJustDo because it feels like it should have its own page]
Recall that on
ChryslerComprehensiveCompensation, we have an official person to blame. We have a card from
ChetHendrickson, signed, saying "It's my fault". One way you can use this is to say things like "OK, we know it's Chet's fault, but what caused this problem?" It reminds people to keep it light.
Where I have a problem with the no-blame thing is that every program defect I've ever seen was caused by a person, and if we don't drill down to see what that person did, and should have done, we can't improve. So I like to know who did it, and what happened. The C3 team doesn't agree with me on this. Probably I'm wrong. --
RonJeffries
I guess the difference is all in motivation. I can see Ron here as a helpful team leader trying to help the offender be more successful, and that's good. On the other hand, such situations can turn into witch hunts, and that's where
ItsChetsFault can give the angry mob enough pause to put the pitchforks back in their barns and go home. -- JasonPettys
?