![]() |
|
|||||||
|
I attended my first STC WebEx Seminar, which was held at CheckFree i-Solutions in Waterloo. I’d like to take a moment to properly thank Peter Szabo and his colleagues at CheckFree for their hospitality. The seminar room was roomy and comfortable, and I appreciated the large display screen at the front of the room. Thank you all for holding a great event! Dissatisfaction with HelpOur speaker, Saul Carliner, began by discussing common complaints about help. Help is unattractive to look at, easy to get lost in, boring to develop, and poorly addresses the needs of multiple kinds of readers, who have varying needs and tolerances. A common thread of online help dissatisfaction stems from a help system’s inability to help a user. Online Help originated in the 1980’s and is associated with just-in-time knowledge delivery. Help authors find it challenging to provide just-in-time assistance while simultaneously knowing exactly what kind of reader to address. For example, context-sensitive or field-level assistance details the function of fields in a software application. Context-sensitive help can’t provide context and workflow information at that level. An application’s fields and function are a means to an end, whereas task-based details offer the end result. Make Help Task-basedSuccessful help systems support user performance and tasks instead of simply describing features and functions. Help authors want to tell people things and get people to do things. Help systems tell many different people how to do things. How we detail the task and choose the information we expose must vary by user experience. Saul Carliner introduced three audience levels for software applications that include Newbies, Arrogant, and Humble.
Mass-Customize InformationWhen you design help systems, address multiple audiences by layering the information by level of experience. The resulting documentation appears as though it’s tailored to specific readers because each type of reader looks in specific places for details and uses specific tools in the help system. To design a help system for Newbies, Arrogant, and Humble, layer and target the details to address each audience type. For example: Newbies see what they need at the surface of the help system–one direct, simple way to perform the 5-10 most common tasks–using the Table of Contents. Arrogant users drill down a layer or two in the Table of Contents or using Find options, where the shortcuts, options, alternative operations, and the next 20-30 most common tasks exist. Humble users prefer queries and search options to help find instances of particular words, phrases, or concepts, as well as access to suggestions and direction on where to go next to find more details, such as user groups and communities of experts. Seven Ideas for HelpSaul offered us seven ideas for sprucing up any help system, including:
![]() |
||||||||
About Carrie SpiraCarrie has a BA in Rhetoric and Professional Writing from the University of Waterloo. She lives in Kitchener with her family and works as a Technical Writer in Waterloo. Carrie enjoys puttering in her gardens, experimenting with digital photography, and makes time for cardio and weight training activities at the YMCA most days after work. |
||||||||
In this issue:Contents | President's Message | Council Members | Competition | Coming Events | Introductions and Overviews | Sprucing Up Help | England | CIC SIG | Software vs. Robotics | Job Bank | American Education | Getting Published | STC Director's Message | STC Transformation | About the Quill |
||||||||