The best GUI is so-intuitive that the user requires minimal training. This is our strength!
The user’s expected workflow should not change significantly.
-
- The collection of related data should be in the order in which the user maintains the data;
- When converting from a manual system to a software system, the user interface (screens and menus) should be similar to the manual methods and workflows that the user had become accustomed to complete;
- When converting from a legacy software system, the user screens, menus and reports of the new system should visually appear, as consistently as possible, to the appearance of the legacy system;
- It is far-cheaper to pay for more programming than to lose valued employees who cannot adjust to a new software application.
The user must feel “in control”.
-
- Extensive error-trapping code is important;
- Every possible error thrown by the database or the operating system must be defined in a lookup table within the program;
- Errors should be:
- forgiving and reversible;
- complete,
- as wordy as necessary,
- offering a solution, and
- definitely NOT be cryptic;
- Each action on the screen should be reinforcing and informative by providing feedback to the user when appropriate;
- Buttons and other “action controls” should be clearly labeled. For example:
- “Exit this screen” – not “OK” or “Exit”;
- “Save and Continue” or “Update and Continue” or “Save and Exit” – not “Save” or “Update” or “Exit”;
- Use “tool tips” (balloon descriptors when hovering over a data entry field) to describe every data field that is being used or viewed;
- A compelling use of “breadcrumbs” should appear somewhere (and in the same place) on every screen to let the user know how he/she arrived at a screen.
- Extensive error-trapping code is important;