Apps Industrial Deals Prime Book Box Women's statement sneakers nav_sap_plcc_ascpsc Disney Hits New LG V35 ThinQ | $699.99. Save with Prime Exclusive Phones. Introducing Fire TV Cube Grocery Handmade Personalized Jewelry modern furniture and decor Book a house cleaner for 2 or more hours on Amazon TheGrandTour TheGrandTour TheGrandTour  Echo Fire tablets: Designed for entertainment Kindle Paperwhite GNO Shop Now SWMTVT18_gno



Showing 1-10 of 44 reviews(2 star). See all 1,354 reviews
on October 5, 2015
Gawande speaks about checklists and many readers could agree with him. However the anecdote-approach limits the use of the book. For instance,, no mention of checklist criteria design before Annexes and, even there, a very short mention.

Interesting to find that one of the cases mentioned -Hudson river landing- had a problem related with a checklist (the manufacturer did not foresee a full power loss below 20000 ft.) losing precious seconds while using a checklist whose design did not fit the situation. The mention of a second Aviation case -Los Rodeos- is simply wrong and, precisely, investigators found that the pilot whose error was the main factor under the accident had been extremely careful following pre-flight procedures...not a good example to show the checklists use.

If someone is interested in checklist design -that was my case- Degani and Wiener still appear to be unsurpassed and the anecdote approach by Gawande does not fit that objective.
28 people found this helpful
11 comment Report abuse
on July 1, 2018
It's a fine book, checklists can useful, but we sort of know that going in. The author tells some interesting stories about skyscrapers airplane pilots, and investors, but his main argument was a little soft.

Should checklists be Read and Do? Or to Confirm that it's been done. Should they cover things that almost never go wrong or should they just hit the frequent gaffes? Are they like a recipe, to be done in order, or like something you might take to the grocery store? Should you actually check items off, for a record, or can someone just go through it verbally. Any and all of that, I see.

So, it's a pleasant easy read and surely was fun to write, but I came away with just a few simple lessons:. Checklists can be get people to talk to one another, and that's often a good thing. And planning ahead is often a good idea.
0Comment Report abuse
on January 11, 2014
The author seems urgently compelled to teach what many technical people know (and utilize) routinely - we use checklists. It is an interesting read, he has some skill in presenting stories to support his somewhat banal cause - but ultimately, if you understand the importance of tracking complex processes with a checklist... don't bother reading this. While it was far from well laid out, there are some interesting insights on brevity, list structure and the like. I wish he would have made this information more clear. Regardless, it was far from earth shattering.
Not a "how to", more the astonished account of a slightly arrogant man learning that using checklists are important. Welcome to our world Mr. Gawande. You are smart and have great accomplishments to boast about, true. Now you let us know that using a checklist is important.

Thanks.
2 people found this helpful
0Comment Report abuse
on April 27, 2018
Very dry and boring. The Whole idea is just make your own checklist for everything, done, end of book.
One person found this helpful
0Comment Report abuse
on February 22, 2017
I bought this book to learn how to make thorough checklists for engineering projects and because the book has high ratings. But reading this book gave me the feeling that I was listening to someone who talks too much. The author goes on and on about topics that are common knowledge and also about emergency room stories. "Checklists are good" is all I got out of this book.
7 people found this helpful
0Comment Report abuse
on May 23, 2016
I was surprised to find that this text (I think) has been re-written as a narrative, without much hands-on instruction, and without much conceptual organization. Of no use to a philosopher.
One person found this helpful
0Comment Report abuse
on October 16, 2015
What a regretful read. Self-referential, repetitive, badly written and ultimately a bore. This should have been a condensed 30 page autobiography - rather it was an old piece of gum, chewed well beyond it's flavour, drawn out into a faux-Galdwell snoozefest. Particularly for doctors thinking that this might enlighten their practice (as I did) - don't set your expectations too high.
2 people found this helpful
0Comment Report abuse
on January 3, 2016
This book could have been reduced to a 5 to 10 page booklet. All of the stories filled up the rest of the book. I was disappointed.
One person found this helpful
0Comment Report abuse
on May 2, 2014
There were lot of interesting stories about checklists and their benefits, but I was convinced already after 1/4 of them. The whole book was about convincing, I would like to have it rather turn into how to design and implement checklists. Actually after the first 1/4, the only really interesting thing was a one page "checklist for designing checklists" -- I wish the last 50% of the book would have been focusing on that and the techniques!
One person found this helpful
0Comment Report abuse
on December 5, 2014
To sum it up: Checklists are good and help make us safe. Was not exactly what I expected from a writer that impressed me with so many other works.
0Comment Report abuse

Sponsored Links

  (What's this?)