Minimalism (technical communication)

Last updated

Minimalism in structured writing, topic-based authoring, and technical writing in general is based on the ideas of John Millar Carroll and others. Minimalism strives to reduce interference of information delivery with the user's sense-making process. It does not try to eliminate any chance of the user making a mistake, but regards an error as a teachable moment that content can exploit.

Like Robert E. Horn's work on information mapping, John Carroll's principles of Minimalism were based in part on cognitive studies and learning research at Harvard and Columbia University, by Jerome Bruner, Jerome Kagan, B.F. Skinner, George A. Miller, and others. Carroll argues that training materials should present short task-oriented chunks, not lengthy, monolithic documentation that tries to explain everything in a long narrative.

A historian of technical communication, R. John Brockmann, points out that Fred Bethke and others at IBM enunciated task orientation as a principle a decade earlier in a report on IBM Publishing Guidelines.

Carroll observes that modern users are often already familiar with much of what a typical long manual describes. What they need is information to solve a task at hand. He feels that documentation should encourage them to do this with a minimum of systematic instruction.

Darwin Information Typing Architecture (DITA) is built on Carroll's theories of Minimalism and Horn's theories of Information Mapping.

Minimalism is a large part of JoAnn Hackos' workshops and books on information development using structured writing and the DITA XML standard.

Good writing means that the message is directly clear to the projected audience. Adopting a minimalist method may appear, in the short-term, to cost more, as writers must cut up and rephrase content into single free-standing chunks. However, the longer-term brings cost-saving benefits, particularly in translation and localization, where often sum is on a ‘per word’ basis. But the greatest advantage for companies is user fulfillment. The less time a customer spends working out how to do something, the more likely they are to purchase again.

Related Research Articles

Usability engineering is a professional discipline that focuses on improving the usability of interactive systems. It draws on theories from computer science and psychology to define problems that occur during the use of such a system. Usability Engineering involves the testing of designs at various stages of the development process, with users or with usability experts. The history of usability engineering in this context dates back to the 1980s. In 1988, authors John Whiteside and John Bennett—of Digital Equipment Corporation and IBM, respectively—published material on the subject, isolating the early setting of goals, iterative evaluation, and prototyping as key activities. The usability expert Jakob Nielsen is a leader in the field of usability engineering. In his 1993 book Usability Engineering, Nielsen describes methods to use throughout a product development process—so designers can ensure they take into account the most important barriers to learnability, efficiency, memorability, error-free use, and subjective satisfaction before implementing the product. Nielsen’s work describes how to perform usability tests and how to use usability heuristics in the usability engineering lifecycle. Ensuring good usability via this process prevents problems in product adoption after release. Rather than focusing on finding solutions for usability problems—which is the focus of a UX or interaction designer—a usability engineer mainly concentrates on the research phase. In this sense, it is not strictly a design role, and many usability engineers have a background in computer science because of this. Despite this point, its connection to the design trade is absolutely crucial, not least as it delivers the framework by which designers can work so as to be sure that their products will connect properly with their target usership.

Content management (CM) are a set of processes and technologies that support the collection, managing, and publishing of information in any form or medium. When stored and accessed via computers, this information may be more specifically referred to as digital content, or simply as content.

A technical writer is a professional communicator whose task is to convey complex information in simple terms to an audience of the general public or a very select group of readers. Technical writers research and create information through a variety of delivery media. Example types of information include online help, manuals, white papers, design specifications, project plans, and software test plans. With the rise of e-learning, technical writers are increasingly hired to develop online training material.

Jerome Howard "Jerry" Saltzer is an American computer scientist.

<span class="mw-page-title-main">Technical writing</span> Type of written communication

Technical writing is a specialized form of communication used by many of today's industrial and scientific organizations to clearly and accurately convey complex information to a user. An organization's customers, employees, assembly workers, engineers, and scientists are some of the most common users who reference this form of content to complete a task or research a subject. Most technical writing relies on simplified grammar, supported by easy-to-understand visual communication to clearly and accurately explain complex information.

The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types. It is an open standard that is defined and maintained by the OASIS DITA Technical Committee.

Task analysis is a fundamental tool of human factors engineering. It entails analyzing how a task is accomplished, including a detailed description of both manual and mental activities, task and element durations, task frequency, task allocation, task complexity, environmental conditions, necessary clothing and equipment, and any other unique factors involved in or required for one or more people to perform a given task.

Single-source publishing, also known as single-sourcing publishing, is a content management method which allows the same source content to be used across different forms of media and more than one time. The labor-intensive and expensive work of editing need only be carried out once, on only one document; that source document can then be stored in one place and reused. This reduces the potential for error, as corrections are only made one time in the source document.

<span class="mw-page-title-main">JoAnn Hackos</span> Consultant and writer on technical communication

JoAnn T. Hackos is a lecturer, consultant, and author of a number of books about technical communication. Now retired, Hackos is the founder of the Center for Information-Development Management (CIDM) and the president emeritus of Comtech Services in Denver, Colorado. She is also a fellow and past president of the Society for Technical Communication. She is a member of the IEEE Standards Association and active in the ISO SC7 Working Groups that is developing standards for information developers. She is the co-author of the standards on content management and information-development management.

In computing, a scenario is a narrative of foreseeable interactions of user roles and the technical system, which usually includes computer hardware and software.

In computing, minimalism refers to the application of minimalist philosophies and principles in the design and use of hardware and software. Minimalism, in this sense, means designing systems that use the least hardware and software resources possible.

Minimalism is a movement in visual arts, music, and other media that began in post–World War II Western art.

In technical communication, topic-based authoring or topic-based writing is a modular approach to content creation where content is structured around topics that can be mixed and reused in different contexts. It is defined in contrast with book-oriented or narrative content, written in the linear structure of written books.

John Millar Carroll is an American distinguished professor of Information Sciences and Technology at Pennsylvania State University, where he previously served as the Edward Frymoyer Chair of Information Sciences and Technology. Carroll is perhaps best known for his theory of Minimalism in computer instruction, training, and technical communication.

<span class="mw-page-title-main">Structured writing</span>

Structured writing is a form of technical writing that uses and creates structured documents to allow people to digest information both faster and easier. From 1963 to 1965, Robert E. Horn worked to develop a way to structure and connect large amounts of information, taking inspiration from geographical maps. He coined the term "Information Mapping" to describe his method of analyzing, organizing, and displaying knowledge in print and in the new online presentation of text and graphics.

SIGDOC is the Special Interest Group on Design of Communication of the Association for Computing Machinery (ACM), an international learned society for computing. ACM SIGDOC was founded in 1975 by Joseph "Joe" T. Rigo.

Technical documentation is a generic term for the classes of information created to describe the use, functionality or architecture of a product, system or service.

A component content management system (CCMS) is a content management system that manages content at a granular level (component) rather than at the document level. Each component represents a single topic, concept or asset.

Janice "Ginny" Redish is an American usability writer and consultant. She graduated from Bryn Mawr College and holds a Ph.D. in Linguistics from Harvard University.

References