|
Problems with UI Guidelines and Consistency
Some feelings I have about UI Guidelines, Consistency, and the misuse and abuse of it all.
|
As a UI designer or developer, following UI guidelines might help ensure that the product you give your users allows them to apply skills they’ve already learned to common tasks and learn new tasks more easily. However, you cannot rely solely on guidelines to ensure the usability of your product. UI guidelines are often too general. On the one hand, to be guidelines they must be somewhat general. Yet it is that very generality that makes them difficult to apply. That is always a challenge when creating a document about guidelines. When you are trying to make specific decisions within the context of your product, a general set of guidelines might not give you enough information for you to make a decision. An example is when you’re trying to decide between method A and method B of presenting information in a dialog box.
On the other hand, guidelines can be too specific. For example, a guideline might specify having no more than seven items on a menu. However, adding additional menus might be more confusing to users than having more than seven choices on any one menu. Additionally, guidelines may conflict with one another. For example, one guideline might specify having no more than seven items on a menu, and another might specify keeping similar items grouped together on menus. Which guideline takes precedence? How would you know? It is one of the many challenges and issues that any document deals with when it comes to creating UI guidelines.
Nevertheless, when designing an application, visual consistency can be helpful. Consider the consistency you find in Microsoft Word and Microsoft Excel. The user interfaces in these software products are very similar in the basic elements such as menus, toolbars, and placement of buttons in dialog boxes—the surface-level interface. In addition, they are consistent in how they handle many common tasks: formatting text, saving files, and so on. Consistency in these and other elements can make it easier for users to transfer skills when learning different applications. Specific UI guidelines help maintain consistency across different products, but consistency by itself is not the ultimate goal.
Moreover, consistency in itself doesn’t ensure usability. It is a mistake to think that consistency in the surface properties of the interface will lead to good design.
These problems really boil down to context: You need to be able to design the user interface for your specific users, goals, and tasks. Guidelines may be a reasonable starting point, but they are only a starting point. The value in UI consistency lies in effective learning, by making it easy to transfer knowledge from another product. However, sometimes ease of learning can get in the way of ease of use;
|
Brought to you by smbius on Tuesday, June 10, 2003 (UMST)
|