March '96 Meeting Reportby Craig Cardimon, Data
Analyst
Knowledge Express Data Systems (Berwyn, Pennsylvania)
As the replacement speaker for Cheryl Lockett Zubak, Donna Timpone from UserEdge in Clinton, NJ, spoke about designing help systems at the March meeting held at Williamson's Restaurant in Horsham, PA.
Timpone explained that usability is the key issue in designing help systems, and usability audits should be conducted. In performing an audit, be sure to test users on the system prototype; conduct user focus groups; test users on the help prototype; talk to the help desk/training staff; take advantage of peer reviews and expert reviews; and conduct beta testing where possible.
There often isn't time to do all these things, however, because management wants the product out the door pronto. So Timpone suggested that, at the very least, help developers take advantage of research findings in the field of usability.
A good help system should take into account how users will use the system when they have a problem. Using online help commonly involves the following processes:
The five core usablity issues are content, structure, writing style, screen design, and access techniques. These can be evaluated using expert reviews (open-ended assessments, automated assessments, ratings or checklists, and peer reviews) and end-user evaluations (beta testing and focus groups).
When persuading management to accept the idea of usability testing, first seek out a manager who will champion usability. Communicate that a positive response to the help system will help market the application and that a bad help system will waste money. Review case studies and your competitors' help systems.
Copyright 1996 STC Philadelphia Metro Chapter
The Meeting Reports editor is Emily Skarzenski.
Return to . . .