Discusses problems in a piece of technical writing which is very well written but has extra words and overly long sentences. (SR)

Presents an extensive bibliography of books, articles, review essays, and reviews published in 1993 on a wide range of fields with information relevant to scientific and technical communication. (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)

Outlines the process of planning and developing a multimedia documentation project. Discusses audience, task, and information analysis; selection of the most appropriate media; effective design; establishment of the development team; hardware and software requirements; costs; and project planning. (SR)

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)

Points out that understanding the buyer's perspective is critical to developing effective marketing materials. Discusses how to determine the buying concerns that are relevant to customers and products and how to organize good marketing writing. (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)

Lists and briefly describes a number of common misuses or misspellings of words. (SR)

Discusses the difference between a complex sentence and a compound sentence, and how they are used in technical writing and in Victorian fiction. (SR)

Discusses how technical communicators can measure performance, productivity, and quality goals. Discusses developing a daily management system of measures for technical communication, notes other possible measures, and discusses criteria and prediction. (SR)

Demonstrates how the tragedy of the 1986 space shuttle "Challenger" provides an example of how communication through memos and letters concerning O-ring problems went awry. Presents some methods by which the technical writing teacher might incorporate this material into their writing curricula. (HB)

Defines conflict, looks at its causes, discusses the various types of organizational conflict, reviews the Myers-Briggs psychological types as they affect conflict, examines managers' typical reactions to internal and external conflict, and lists six keys to successful conflict resolution. (SR)

Argues that the development of software documentation should be fully integrated with the overall development of new software products. Suggests that, when technical communicators become full members of the development team, they will not cease to communicate but will be able to add communications value to the product as well as to the…

Discusses the use of "there is" and "there are," and recommends notional agreement (agreement of a verb with its subject or of a pronoun with its antecedent in accordance with the notion of number rather than with the presence of an overt grammatical marker for that notion) as a useful approach to deciding which to use. (SR)

Offers suggestions to help technical writers get a start in marketing writing. Discusses thinking differently, making the transition, and good beginner projects. (SR)