Good checklist design is not trivial, however. I use checklists professionally, and the list rapidly accumulates cruft for problems that have been solved by design. E.g., suppose one time someone forgot to sign your software release. "Verify release has been signed" is added to the checklist. However a bright soul also integrates signing into the release build. Thus the problem is essentially solved once and for all, but the item will remain on the checklist in perpetuity, which adds overhead & decreases confidence in the checklist process.
I think they make sense for infrequently exercised routines of moderate complexity that are 100% execution. A complex but limited scope machine like a plane is really an ideal example. I guess preparing for a vacation could be another, although I get caught up because packing is totally different every time. I suppose I checklist myself when I rappel or go skiing ("Skins, skis, boots, ... working up the body")
I think they make sense for infrequently exercised routines of moderate complexity that are 100% execution. A complex but limited scope machine like a plane is really an ideal example. I guess preparing for a vacation could be another, although I get caught up because packing is totally different every time. I suppose I checklist myself when I rappel or go skiing ("Skins, skis, boots, ... working up the body")