|
Edited by Susan Duncan, Membership Coordinator Victoria A. Kirkpatrick After seven years as an Executive Assistant to the CIO for the largest regional
electronic funds transfer network in the United States, technical writing seemed to be the
next logical step in my career. I had reached the top of the ladder as an executive
secretary, and wanted to continue to learn news skills and utilize the skills I already
had. I approached management and, fortunately, they created a technical writing position
for me. Basil White One day at boarding school, my English teacher, a tall, elderly Texas priest with a full head of shocking white hair, had each student write a set of instructions for folding a piece of paper so that it will fit into a 3 1/2" x 6 1/2" envelope. We then exchanged instructions and followed each other's instructions explicitly. No one folded the paper correctly. That lesson taught me how challenging technical communication can be, and the value of learning how to communicate in a style that minimizes opportunities for misinterpretation. At the 1997 STC conference in Anaheim, then-Usability SIG president Ginny Redish asked the attendees at the Conference SIG meeting what the SIG could do to serve the STC in new ways. I suggested that we should adapt the STC manual evaluation workshops into a method for evaluating the usability of the products for which STC members create technical communication. Since then, the Usability Evaluation Workshop has become a useful way to learn the dialogue of usability, share expertise with others, and provide useful tips to developers on how to improve their products. At the STC conference, I am known as the "usability bouncer," because I stand outside the conference room where the Usability Evaluation Workshop is held and prevent the uninvited from threatening the intellectual property of the unreleased products being evaluated in the room. Become an evaluator, or submit your product! It's fun. |
|||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||