Pull-Down Menus: Out of Sight, Out of Mind (continued)

TOOL BARS AS CRYPTOSOLUTIONS Research shows that users dislike searching for hidden command options. Therefore, word processors use toobar icons to represent options in an attempt to make the hidden pull-down commands visible. (This is direct evidence of the pull-down problem!) Meanwhile, we must avoid the cryptonotion that a toolbar ribbon in your transaction-oriented applications solves the problems of pull-downs. While toolbars serve well in applications that need a blank page, it creates problem for other applications. First, the icons are difficult to interpret for new or casual user of a transaction application. They at least need labels. (Have you memorized all your word processor icons yet?) Second, in corporate applications, we often find navigation icons mixed with other icons that merely change settings or provide ancillary functions. Thus, users lose contextual clues for understanding functions at a glance.

THE TASK IS THE THING Can we distinguish the guerilla pull-downs from civilian pull-downs yet? Let's look at some guidelines for correct use of pull-downs in corporate applications that handle data entry or data viewing. Let's use our VIMM model discussed in last month's column.

Issue: With pull-downs, users must play hide-and-seek with the option they want.

Solution: Keep frequently used actions on the screen, probably as push buttons, secondarily as labeled toolbar icons. Users can let their eyes do the walking faster than their fingers can explore pull-downs! If you are really tight on screen space, the best candidates for pull-downs are system-wide function that are used infrequently. Furthermore, since users navigate frequently and need to stay oriented to where they are, really really really try to avoid pull-downs for navigation.

Issue: pull-downs use shorter phrases than can be placed on push buttons. This makes them harder to understand. Also, since pull-down or toolbar options are lumped together, they are not associated with the screen task flow. You may have to figure out for yourself where the action fits in the task flow.

Solution: Put the options on push buttons. Buttons and menus can handle longer phrases than pull-downs. You get clear communication for casual and new users. You can position the push button on the screen at the place the user needs it, matching the task flow as it goes in a left-right, top-down pattern. If a command appears on several screens, try to design a task flow that allows a consistent position for the buttons.

When using pull-downs, never change menubar names! (Play the slots with a slot machine, not a menubar.) If an option doesn't apply in a particular situation, deactivate it by dimming it rather than "offing" it.