I saw a discussion of blame

Context
I sent out an e-mail to the staff of our Main Library today to let them know about a computer glitch we thought might affect patrons and taking responsibility on behalf of my department. The director of the library, being a nice guy, sent an e-mail back saying, "No one is to blame here." Then, because it was Friday afternoon, we got into a silly discussion of who really was to blame. We decided on the framers of the Constitution.

Commentary
OK, you had to be there. But I understand Dr. Heezen's intent, as it mirrors something I often say, "I'm not interested in assessing blame; I want to solve the problem." On the other hand, in order to prevent a problem from recurring it's often necessary to know who caused it in the first place. Plus I'm a firm believer, with Samuel Smiles, that a mistake is the best opportunity for learning on the planet.

So is there a way to get to get the benefits of assigning responsibility for errors without oppressing those guilty of them? There may be, if we stick to some basic principles:

1) Assessing responsibility is not the end of the story. It's the beginning of a process of improvement that ideally includes not just the person who made the error, but also anyone who can help her/him prevent it in the future, like a trainer, copy editor or beta tester (Yup, that's what we needed today!).

2) You cannot judge a person's character by one of his/her actions. A person who makes a mistake is not a screw-up, anymore than a person who drinks a glass of water is the ocean.

3) The person who bore the brunt of the consequences of a mistake may not be ideal for helping the person responsible recover. AA step 9 is to make amends to the people you've wronged, but you don't usually ask those people to be your sponsor. A disinterested third-party often brings a more solution-oriented perspective.

What did you see today?