Offers suggestions and examples of how to write clear and effective notes, cautions, and warnings. (SR)

Discusses briefly the challenge of writing the technical documentation for automobiles required by the 1990 Clean Air Act Amendment. (SR)

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

Describes the elements of an effective style guide. Presents methods and techniques required to develop a style guide tailored to the specific needs of an organization. Focuses on two critical steps in the development process that are often ignored or overlooked: (1) conducting the Requirements Analysis; and (2) promoting the style guide. (SR)

Discusses and illustrates how technical communicators can read and write complex documents dialogically by using a new/old strategy to help them in three activities: breaking down complex documents and data into components; solving problems by locating and describing causal components; and following and organizing sequences of components. (SR)

Discusses how too much caution can lead authors to simple verbosity or to the overgeneralization of simple concepts. (SR)

Discusses a proposal's executive summary: its purpose, how long it should be, what should be in it, when it should be started, who should write it, and how it should be reviewed. (SR)

Examines the paradigm "the writer is self-contained," which underlies current writing practices in business and education. Discusses how creating a supportive climate for the writing process relates to the paradigm "every writer needs an editor." Discusses the implications of making such a change in business, industry, and education. (SR)

Discusses four basic categories of restrictions within which the video script writer works: purpose, time, budget, and resources. Discusses how these variables work together to force creation of a document that can be produced. (SR)

Discusses kinds of jargon found in technical writing, how much jargon is acceptable, and the best way to handle jargon. (SR)

Discusses how to get started in hypermedia, offering a springboard for beginning hyperdocument developers. Argues that the key is to transfer the familiar to the unfamiliar by adapting paper-document writing processes and by applying the appropriate, familiar page-design principles. (SR)

Presents an approach to document numbering, document titling, and process measurement which, when used with fundamental techniques of statistical process control, reveals meaningful process-element variation as well as nominal productivity models. (SR)

Identifies and discusses the effects of single sourcing on the writing process. Provides suggestions for incorporating the teaching of single sourcing into technical communication courses. Concludes that educating students about the process of single sourcing is important if they are to become effective technical communicators in the industry. (SG)

Discusses how to make better indexes for online documentation. (SR)

Offers examples of what can happen when writers try to be impressive, and instead are vapid, grandiloquent, opaque, or absurd. (SR)