Maybe flight crews/maintenance staff should configure the machine randomly after a flight/maintenance, so as to force the next crew to actually run the checklis

Maybe flight crews/maintenance staff should configure the machine randomly after a flight/maintenance, so as to force the next crew to actually run the checklist carefully? This reminds me a little of Adam Langley's advice for keeping software protocol extensibility points well-oiled: You might want to define and implement dummy extensions once a year or such, and retire old ones on a similar schedule. When extensions contain lists of values, define a range of values that clients insert at random. (https://www.imperialviolet.org/2016/05/16/agility.html https://www.imperialviolet.org/2016/05/16/agility.html)