Ask Eric: Questions & Answers

November 11, 2002 – submitted by Malc Wilson of USA

Question: In a functional Web page, when should I use "Reset" & "Apply" and when should I use "Cancel" & "Save"?

Eric's response: Use "Reset" and "Apply" for technically savvy users and for users you want to confuse. I find that many DEVELOPERS don't know what "reset" is supposed to mean. We have also seen many users have trouble with the concept of "Apply". "Cancel" and "Save" are more commonly understood.

August 26, 2002 – submitted by S. Udovic of Holmdel, NJ

Question: We need to collect information from users that will automate a sequence of numbers they have to type frequently. The sequence contains numbers with an embedded password. We could collect this all in one string, but the password must appear in a password field so that it is not visible on the screen but appears as *** characters. So, we can break this into three text input fields OR we can have them enter the password in a password field and enter the other characters in a field that allows you to enter the entire string and "code" where the password should appear, for example, the field would contain 530126Password555 with the "code" character entered here as the word "Password." Clearly, this is not simple to represent in either case, but I'd like to know whether there is any data showing that the latter technique would be too confusing.

Thanks in advance.

Eric's response: First I would suggest you consider a general macro facility. It is often useful to let the USERS setup and administer a set of macros as you describe. They will use them in ways you don't expect.

Be sure you really NEED the protection of non-display of the password in the setup procedure. It seems like overkill. I would like the user to be able to enter a string of characters, and just enter a tab for when the system should enter a tab.

If you must have a non-visible field you will have trouble with a generic facility. In this case it would be best to have the separate fields shown, with a protected password field. Do NOT introduce a coding sequence. This is more complex and less conventional. Use separate fields.

April 24, 2002 – submitted by Erwin Van Trier of Plano, TX

Question: We are currently having a discussion on the implementation of different functions manipulating the same feature (within 1 GUI). The functions are Display, Create, Modify and Remove

The question is if we need to represent these functions via a radio button or do we represent them via TABS.

For me the TAB option is the better one because each pane would only show the parameters that are applicable for that function.

With the radio button option we need to gray out non-applicable parameters.

Whenever we decide about this implementation do we need to have all other GUIs to follow the same rule, or could there be a good reason not to be consistent over all GUIs?

Eric's response: Several things. First it is generally a BAD thing to have multiple ways of doing one function. It increases complexity and clutter. So only do this if there is a clear user need that forces such flexibility.

Second, tabs and radio buttons can be used in an identical way. In these cases tabs are more obvious and present larger (and therefore quicker to hit) targets. Radio buttons reduce space.

Third, the functions Display, Create, Modify and Remove are almost never organized like that in a taskflow. This is the way the database designer sees it. The users usually look at the items (display) and then maybe delete or modify. Creating is often a separate task. Therefore, the appropriate design is almost never just a set of buttons to Display, Create, Modify and Remove. So I want ONE display from which I can see the item, change it, and delete it.

Lastly, all the GUIs need the same design for this... unless there is a really amazing compelling reason to do it differently.

January 18, 2002 – submitted by Anonymous

Question: I have a usability question regarding pre-populating fields in Web applications. If a form is being prepopulated by a web application and a particular field has no associated data for a particular record, is it better to leave the field blank or to populate the field with some verbiage such as "N/A"? Thank you for your time with answering this question.

Eric's response: It is good to provide default (prepopulated) data if you know what the user will enter with about 80% probability. But with prepopulation, any field you are not sure of is simply left blank. Putting N/A is misleading, as the user is likely to think it is not a required field. If you are prepopulating as defaults, then it IS applicable. You just do not know what to put in it. In addition, the user has the work of highlighting the indicator to erase it before putting in the required data. It is very normal for users to see default data in Web applications, prefilled by logic or based on previous entries. Just add the data you have and leave the rest of the form as it is.

If you do NOT mean 'defaults' and you really know exactly what the user must enter, WHY are you asking the user to view it? And if the field is really not required, WHY are you showing it at all?

January 8, 2002 – submitted by Donna Way of Hartford, CT

Question: Do you have any data or studies that reflect how users react to a top/bottom versus left hand navigation bar? We are attempting to design a company-wide template that will effect thousands of users and I haven't been able to locate any specific data.

Eric's response: Donna, we have data that indicates that users expect that a left-hand set of navigation controls are expected to have "internal links." This means selection results in changing the display area without leaving the navigation structure (try picking links on the left side of www.humanfactors.com). We know that links on the right and also sometimes on the lower part of the left are expected to be external. This means they go to another place. I have not seen a comparison of top vs. bottom. But I would expect a very similar distinction. Top should be internal. Bottom is less often used, but should probably be external links.