In computing, a wizard breaks a complex task into a series of simple steps. The Wizard of UX is a newsletter that takes the complex topic of user experience (commonly abbreviated UX) and breaks it into a series of short topics. The Wizard of UX will be published on an irregular basis, to help establish at ASI a better understanding of the principles of UX and how we can work together to achieve a good experience for our customers. Your contributions are welcome; send them to Sara Hardison or Jim Sneeringer, or to UserExperience@advsol.com.
Why do we say User Experience?
The topic of this first issue is the term UX itself. We used to talk about user interface (UI) or usability. Why introduce a new term? Is it to give the field a mystique and create a sense of superiority over outsiders who cannot understand the rapidly changing terminology?
Actually, we want to accurately describe our goal. The phrase user interface connotes something superficial, like a coat of paint – a thin layer between the program and the user, while user experience more accurately suggests that everything about the software works together to help the user accomplish his task. An example may help.
Think of an iMIS user setting up donor clubs, with a structure something like this:
Donations
0 - $499
Bronze
$500 - $999
Silver
$1000 – up
Gold
At first, it may seem best to have the user give the minimum and maximum dollar value for each club. However, in that case the user must specify redundant information, because the maximum value for each level is always just below the minimum for the club above it. Not only does the user have to specify redundant information, but the computer must check it. Suppose the max of the bronze level were $599 and the minimum for Silver were $500. Then we have an error, which the program must detect, report and explain to the user, a lose-lose situation.
A better way is to have the user specify only the minimum for each club. The program can then deduce the maximum for the club below, and both the software and the user have easier jobs.
As you can see, this is not a question about the color, type or size of the controls. It affects the code and the database schema as well. Thus the old term, UI, helped create a misunderstanding of the extent and role of user experience design. This also explains why UX involvement is needed from the beginning of a project.
That’s all for now. Keep your eyes open for the next Wizard of UX.