10 ms·
I'm currently in the process of introducing checklists into a process, and the hardest part of the entire endeavor is giving the people who are using the checkl
by extrapickles 7y ago
I'm currently in the process of introducing checklists into a process, and the hardest part of the entire endeavor is giving the people who are using the checklist the power to modify them, and keeping other people from forcing the system to have chiseled into stone type checklists.
So far, the biggest contributor to 'checklist fatigue' among people using the system is from them not being able to modify the checklist to suit the task at hand. Checklists really need to be living documents, so errors and usability improvements can be made. The article does mention that the more proscribed from on-high the checklist was, the more the performance of the checklist was degraded.
- privateSFacct 7y ago100% agreed! There is the attitude of "get over it" and follow the list - that does NOT work. What does work is exactly that - make the thing useful and people will actually love it. That means local adaption, ability to update and refine. What works wonders is if you can introduce policy changes and improvements through the list. Ie, the list leads rather than follows and gets outdated.