Argues that technical communicators should have a working definition of icons, know when to use them, and understand some of the problems inherent in icon design. Recommends using a workable icon classification system and adhering to some practical design guidelines. (SR)

Shows how and why errors get introduced into examples in computer software documentation and what actions technical communicators can take to minimize this occurrence. Proposes a method to test examples. Suggests that technical writers can avoid these sources of error by creating and implementing a good test plan, maintaining and updating the…

Notes that many companies want to reduce paper documentation necessary to support their products. Maintains that, if technical communicators are to avoid being downsized out of a job, they must build on their existing communication skills and move toward product design, helping to produce products so obvious that they need no manuals. (SR)

Explains the controversy surrounding the Office Assistant ("Paper-Clip") in Microsoft's Office 97. Discusses why actual readers rejected the default Office Assistant's role as implied writer and rebelled against the reader role implied for them. Notes users resented its intrusive behavior, rejected its implied writer role, and refused to…

Discusses what usability is and how to test for it. Offers nine suggestions for technical communicators working on usability testing. (SR)