user vs. standards
The past couple of weeks we have been doing Think Aloud usability testing on the iphone applications that we built wireframes for last quarter. It was great to take the prototypes out and experience a range of reactions to both the application as well as the UI.
We were charged with documenting “critical issues”. In some cases this proved surprising….The iphone is intuitive and easy to use? Following standards make the applications easier to use?
- Words matter.Tags are something most designers and developers are familiar with (standard), but only one case manager understood what that meant. Once I explained what Tags were they stated wow that would be really useful. In their words keywords so I can easily search through notes by topic.
- Symbols can be confusing. The section where the case manager is able to add clients was modeled after the address book on the iphone. There is a plus button to “add” a new client. It was interesting to see that this was not intuitive to the case managers including those that were familiar with iphones. I thought I was following the “standard”, but I would much rather give the users what they were all looking for a “new client” button. I realize there are language issues and that the plus does not require translating, but this is why context is always important.
I am not sure what the answer is for user vs. standards, but feel testing is important to understand the decisions we are making as designers.
Project managers can we please build a little time in the schedule for testing?