Checklists are an easily observable symptom of an team drive for improvement of outcomes. But you can't reverse that and plop down checklists that are used under threat.
I'm going to try to find it. But, if I don't, you got the gist of it:
Have a checklist, and stick to it. Don't expect one person, or even multiple people, to remember all of the steps off the top of their head.
It's an -excellent- book about the application of checklists to error reduction etc.
I'm worried it might have been .NET Rocks![1] They have a great podcast, but their episodes aren't indexed by Google because of their website structure.
I'm gonna keep looking, and even check my home computer's history when I get home tonight, but I wouldn't hold your breath. Someone a bit above linked to a book that I'm pretty sure was the impetus behind the podcast I listened to, so it might be worth giving that a read.
EDIT: HA! I found it! It was actually in the press section on the book's web page.
http://www.npr.org/templates/story/story.php?storyId=1222261...