I think that the Checklist Manifesto is a must read for testers.
In his book, Atul Gawande demonstrated how Boeing developed the idea of using checklists after investigating test flight crashes. It turned out that no matter how experienced the pilot was, it was easy to forget something important when piloting a complex airplane. The same held true for doctors and their surgeries.
It turns out that no matter how experienced a tester is, it’s easy to forget something important when testing a complex system.
But now I don’t mean traditional test cases by the concept of a checklist. Conventional test cases seem to be what Dr. Gawande describes as read-do -lists, and they don’t seem to work that well in a professional environment.
A testing checklist might instead be a suitably crafted mindmap to support exploratory testing. That would lean towards the do-confirm -kind of list which Gawande described in the book as the way to go.