This is an interesting note since keyboard design to support high-volume users where errors can be catastrophic is not all that common though there are still many, many users like yours and order-entry clerks, and sales professionals, who use tools not to mention tech support personnel.
Some really basic things and later this weekend, I'll try to dig up some of my references on keyboard design issues: 1. Preventing errors. I've worked with traders and they move quickly so you want to avoid having high-frequency "save" keyboard functions adjacent to low-frequency, but destructive keys. You want to avoid bad one-off errors. 2. Awkward combinations of shortcut keys that require a stretch or that result in undue crossing. 3. Mnemonic value 4. Data entry forms and data validation (don't interrupt too much with inline validation) 5. Lag times and typeahead problems 6. Consistency among their specialized apps and with standard apps 7. Feedback for key operations that allows the user to start again after an interruption (of which there are many) 8. Data logs would be quite useful here. 9. The GOMS KLM model could be quite helpful in your work since you can model keystroke and mouse operations and get estimate of tasks times early in design. 10. The design of all forms and use of keyboard efficient widgets. For example, instead of yes/no/maybe radio buttons, you would just use a text field since they would quickly learn the 3 codes. 11. The use of efficient and consistent codes for text entry where you don't want to force mouse-focused widgets on the users. 12. Consistent rules for assignment of keyboard accelerators, shortcuts, function keys. Chauncey I'll dig up some references On Thu, Jan 22, 2009 at 12:32 PM, Douglas Hollinger < [email protected]> wrote: > > I'm putting together a discovery and research plan for improving the > usability of an equities direct trading application. The primary users of > the application are day traders, and because they need to act quickly to > dynamics in the market in real time, they tend to be very keyboard-oriented. > They are constantly scanning across multiple screens/views and don't like to > take their hands off the keyboard to use a mouse. > > Thus, as we look to improve the interface and functionality of the > application, we need to keep mouse usage to an absolute minimum. The traders > like to use hotkeys and shortcuts to execute standard commands. In addition, > they would like the ability to execute more complex workflows by setting up > customizable hotkey shortcuts. Any new UI will need to accommodate this > behavior. > Has anyone developed for this kind of environment and specialized user > group? Are you aware of related research that might be helpful in terms of > designing for keyboard-oriented users? > Thanks in advance for any advice. > > Doug > _________________________________________________________________ > Hotmail(R) goes where you go. On a PC, on the Web, on your phone. > > http://www.windowslive-hotmail.com/learnmore/versatility.aspx#mobile?ocid=TXT_TAGHM_WL_HM_versatility_121208 > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [email protected] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
