Return to Answer

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

 

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

If you need to trigger five shortcuts sequentially to trigger the action, and a combination of those shortcuts does not perform any other action, the ejector seat is very well hidden.

However, as Terdon suggests, in the OPs case the first four shortcuts in the sequence can be used to perform many different actions (mostly navigating menus).

You only have to get the final shortcut in the sequence wrong to potentially activate the ejector seat.

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

If you need to trigger five shortcuts sequentially to trigger the action, and a combination of those shortcuts does not perform any other action, the ejector seat is very well hidden.

However, as Terdon suggests, in the OPs case the first four shortcuts in the sequence can be used to perform many different actions (mostly navigating menus).

You only have to get the final shortcut in the sequence wrong to potentially activate the ejector seat.

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

The OP has since clarified that you would need to trigger five shortcuts sequentially to trigger the action, so in this case the ejector seat is very well hidden.

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

If you need to trigger five shortcuts sequentially to trigger the action, and a combination of those shortcuts does not perform any other action, the ejector seat is very well hidden.

However, as Terdon suggests, in the OPs case the first four shortcuts in the sequence can be used to perform many different actions (mostly navigating menus).

You only have to get the final shortcut in the sequence wrong to potentially activate the ejector seat.

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

Alan Cooper uses an ejector seat analogy in About Face which is pertinent here:

Just as a jet fighter needs an ejector seat lever, complex desktop applications need configuration facilities. Applications must have ejector seat levers so that users can occasionally dramatically (sometimes irreversibly) alter the application's function, behaviour, or content.

The one thing which must never happen is accidental deployment of the ejector seat. The interface design must ensure that the user can never inadvertently fire the ejector seat when all he wants to do is make a minor adjustment to the application.

The OP has since clarified that you would need to trigger five shortcuts sequentially to trigger the action, so in this case the ejector seat is very well hidden.