Discusses how technical communicators can get their clients to participate in case studies (for use in marketing the technical communicator's services) by analyzing the case study strategy, selecting appropriate clients, understanding their concerns, and developing a professional presentation. (RS)

Discusses a six-step method for writing "customer stories"--a form of promotional writing that highlights the practical benefits of the product a company develops, markets, and supports. (RS)

Offers an eight-step approach to the team writing process that will help document managers avoid, minimize, and resolve problems found in the team writing process. (SR)

Presents a rhetoric of visuals in relationship to their accompanying text. Discusses prior research in graphics, outlines a syntax of graphics and their level of abstraction, describes tagmemic analysis of visuals, and discusses rhetorical integration of text and visuals. (SR)

Calls for a concerted effort by publication professionals and government to establish quality standards and trade regulations for technical documents, including consumer product information. Discusses various quality-assurance mechanisms. (PRA)

Maintains that classical rhetoric is an appropriate rhetoric for technical writing courses and textbooks. Presents three key concepts that provide the basic framework for incorporating classical rhetorical theory into contemporary technical writing studies. (SR)

Discusses writing indexes in computer documentation. Describes kinds of indexes, what subject matter to index, creating specific entries, design alternatives, and phrasing of entries. (SR)

Details the "technical documentation process," a basic five-step process for managing technical documentation projects: assessment, analysis, design, development, and validation. (SR)

Discusses professionalism and being professional in the field of technical communication. (SR)

Discusses grammatical arthritis (an internal buildup of rules that hinders writing flexibility); four new "rules" (concerning "data is,""none are,""hopefully," and the restrictive "which"); attitudes toward English grammar; how to be a helpful editor; and where to learn about grammar. (SR)

Considers Edward Tufte's nine principles for design in terms of scientific illustration. (SR)

Discusses important points for the freelance technical writer to consider when setting guidelines and developing contracts. (SR)

Discusses the purposes served by visual elements in a document, and notes some conventions that have been dropped in the last few years in an attempt to eliminate clutter. (SR)

Discusses the impetus for considering new terminology for the field of communication. Presents four categories to consider as alternative labels to describes what many "technical writers" actually do: information developer of functional analyst, interface professional, project manager, and information manager. (SR)

Describes "builds" and "filters," two simple forms to interactive media that the viewer can control to reveal new layers of information and that often save resources by replacing many separate graphics. (SR)