Checklists and Flow
Start with the finger flow and mnemonics when appropriate (ie GIFY), then following up with the
checklist has a higher rate of error detection.
Studies show that finger pointing with verbalization during the flow greatly reduces errors in
configuration changes.
When running the checklist, consider using the challenge - response method. Identifying and verifying
each configuration. Read the challenge off the list and then after confirming the configuration change
verbalize the response.
Two ways to do this:
One: The "Do-Verify" method. Each item is read, each action is accomplished, the accomplished
item is confirmed and on to the next item. It's clearly a no-memory way of doing it. Simply read
the list and follow with the action.
Two: The "Challenge-Do-Verify" method. Everything gets done first, usually via a 'flow', and it's
followed by a reading of the checklist for confirmation.
Follow a flow for normal operating and verify against the Check list after. Don’t be afraid to repeat
critical mnemonics multiple times, particularly in the take-off and landing phases.