Technical communication (or Tech Comm) is communication of technical subject matter such as engineering, science, or technology content. The largest part of it tends to be technical writing, though importantly it often requires aspects of visual communication (which in turn sometimes entails technical drawing, requiring more specialized training). Technical communication also encompasses oral delivery modes such as presentations involving technical material. When technical communication occurs in workplace settings, it's considered a major branch of professional communication. In research or R&D contexts (academic or industrial), it can overlap with scientific writing.
Technical communication is used to convey scientific, engineering, or other technical information.[1] Individuals in a variety of contexts and with varied professional credentials engage in technical communication. Some individuals are designated as technical communicators or technical writers as their primary role; for some others, the role is inherently part of their technical position (e.g., engineers). In either case, these individuals utilize appropriate skills to research, document, and present technical information as needed. Technical communicators may use modalities including paper documents, digital files, audio and video media, and live delivery.
The Society for Technical Communication defines the field as any form of communication that focuses on technical or specialized topics, communicates specifically by using technology, or provides instructions on how to do something.[2][3] More succinctly, the Institute of Scientific and Technical Communicators defines technical communication as factual communication, usually about products and services.[4] The European Association for Technical Communication briefly defines technical communication as "the process of defining, creating and delivering information products for the safe, efficient and effective use of products (technical systems, software, services)".[5]
Whatever the definition of technical communication, the overarching goal of the practice is to create easily accessible information for a specific audience.[6]
Technical communicators generally tailor information to a specific audience, which may be subject matter experts, consumers, end-users, etc. Technical communicators often work collaboratively to create deliverables that include online help, user manuals, classroom training guides, computer-based training, white papers, government documents, industrial videos, reference cards, data sheets, journal articles, and patents. Technical domains can be of any kind, including the soft and hard sciences, high technology including computers and software, and consumer electronics. Technical communicators often work with a range of subject-matter experts (SMEs) on these projects.
Technical communication jobs include the following:[3] API writer, e-learning author, information architect, technical content developer, technical editor, technical illustrator, technical trainer, technical translator, technical writer, usability expert, user experience designer, and user interface designer. Other jobs available to technical communicators include digital strategist, marketing specialist, and content manager.
In 2015, the European Association for Technical Communication published a competence framework for the professional field of technical communication.[7]
Much like technology and the world economy, technical communication as a profession has evolved over the last half-century.[8][9] In a nutshell, technical communicators take the physiological research of a project and apply it to the communication process itself.
Historically, Technical & Professional Communication (TPC) has been as an industry that practices writing and communication. However, recently User Experience (UX) Design has become more prominent in TPC as companies look to develop content for a wide range of audiences and experiences.[10]
The User Experience Professionals Association defines user experience, or UX, as "Every aspect of the user's interaction with a product, service, or company that make up the user's perception of the whole."[11] Therefore, "user experience design as a discipline is concerned with all the elements that together make up that interface, including layout, visual design, text, brand, sound, and interaction."[11]
It is now an expectation that technical communication skills should be coupled with UX design. As Verhulsdonck, Howard, and Tham state "...it is not enough to write good content. According to industry expectations, next to writing good content, it is now also crucial to design good experiences around that content." Technical communicators must now consider different platforms such as social media and apps, as well as different channels like web and mobile.[10]
As Redish explains, TPC no longer writes content but "writes around the interface" itself as the user experience surrounding content is developed. This includes usable content customized to specific user needs, that addresses user emotions, feelings, and thoughts across different channels in a UX ecology.[12][10]
Lauer and Brumberger further assert, "…UX is a natural extension of the work that technical communicators already do, especially in the modern technological context of responsive design, in which content is deployed across a wide range of interfaces and environments."[13]
Technical communication is a task performed by specialized employees or consultants. For example, a professional writer may work with a company to produce a user manual. Some companies give considerable technical communication responsibility to other technical professionals—such as programmers, engineers, and scientists. Often, a professional technical writer edits such work to bring it up to modern technical communication standards.
To begin the documentation process, technical communicators identify the audience and their information needs. The technical communicator researches and structures the content into a framework that can guide detailed development. As the body of information comes together, the technical communicator ensures that the intended audience can understand the content and retrieve the information they need. This process, known as the writing process, has been a central focus of writing theory since the 1970s, and some contemporary textbook authors apply it to technical communication. Technical communication is important to most professions, as a way to contain and organize information and maintain accuracy.
The technical writing process is based on Cicero's 5 canons of rhetoric, and can be divided into six steps:
All technical communication serves a particular purpose—typically to communicate ideas and concepts to an audience, or instruct an audience in a particular task. Technical communication professionals use various techniques to understand the audience and, when possible, test content on the target audience. For example, if bank workers don't properly post deposits, a technical communicator would review existing instructional material (or lack thereof), interview bank workers to identify conceptual errors, interview subject matter experts to learn the correct procedures, author new material that instructs workers in the correct procedures, and test the new material on the bank workers.
Similarly, a sales manager who wonders which of two sites is better for a new store might ask a marketing professional to study the sites and write a report with recommendations. The marketing professional hands the report off to a technical communicator (in this case, a technical editor or technical writer), who edits, formats, and sometimes elaborates the document in order to make the marketing professional's expert assessment usable to the sales manager. The process is not one of knowledge transfer, but the accommodation of knowledge across fields of expertise and contexts of use. This is the basic definition of technical communication.
Audience type affects many aspects of communication, from word selection and graphics use to style and organization. Most often, to address a particular audience, a technical communicator must consider what qualities make a text useful (capable of supporting a meaningful task) and usable (capable of being used in service of that task). A non-technical audience might misunderstand or not even read a document that is heavy with jargon—while a technical audience might crave detail critical to their work such as vector notation. Busy audiences often don't have time to read entire documents, so content must be organized for ease of searching—for example by frequent headings, white space, and other cues that guide attention. Other requirements vary according to a particular audience's needs.
Technical communicators may need to translate, globalize, or localize their documents to meet the needs of audiences in different linguistic and cultural markets. Globalization involves producing technical content that meets the needs of "as many audiences as possible," ideally an international audience.[14] Localization adapts existing technical content to fit the "cultural, rhetorical, educational, ethical, [and] legal" expectations of users in a specific local context.[14]
Technical communication, in the government, is particular and detailed. Depending on the segment of government (and country), the government component must follow distinct specifications. Information changes continuously and technical communications (technical manuals, interactive electronic technical manuals, technical bulletins, etc.) must be updated.
Technical communicators must collect all information that each document requires. They may collect information through primary (first-hand) research—or secondary research, using information from existing work by other authors. Technical communicators must acknowledge all sources they use to produce their work. To this end, technical communicators typically distinguish quotations, paraphrases, and summaries when taking notes.
Before writing the initial draft, the technical communicator organizes ideas in a way that makes the document flow well. Once each idea is organized, the writer organizes the document as a whole—accomplishing this task in various ways:
After organizing the whole document, the writer typically creates a final outline that shows the document's structure. Outlines make the writing process easier and save the author time.
After the outline is complete, the writer begins the first draft, following the outline's structure. Setting aside blocks of an hour or more, in a place free of distractions, helps the writer maintain a flow. Most writers prefer to wait until the draft is complete before any revising so they don't break their flow. Typically, the writer should start with the easiest section, and write the summary only after the body is drafted.
The ABC (abstract, body, and conclusion) format can be used when writing a first draft of some document types. The abstract describes the subject so that the reader knows what the document covers. The body is the majority of the document and covers topics in depth. Lastly, the conclusion section restates the document's main topics. The ABC format can also apply to individual paragraphs—beginning with a topic sentence that states the paragraph's topic, followed by the topic, and finally, a concluding sentence.
Once the initial draft is laid out, editing and revising can be done to fine-tune the draft into a final copy. Usability testing can be helpful to evaluate how well the writing and/or design meets the needs of end-users and to suggest improvements [[15]] Four tasks transform the early draft into its final form, suggested by Pfeiffer and Boogard:[citation needed]
In this step, the writer revises the draft to elaborate on topics that need more attention, shorten other sections—and relocate certain paragraphs, sentences, or entire topics.
Good style makes writing more interesting, appealing, and readable. In general, the personal writing style of the writer is not evident in technical writing. Modern technical writing style relies on attributes that contribute to clarity: headings, lists, graphics; generous white space, short sentences, present tense, simple nouns, active voice[16] (though some scientific applications still use the passive voice), second and third person as required
Technical writing as a discipline usually requires that a technical writer use a style guide. These guides may relate to a specific project, product, company, or brand. They ensure that technical writing reflects formatting, punctuation, and general stylistic standards that the audience expects. In the United States, many consider the Chicago Manual of Style the bible for general technical communication. Other style guides have their adherents, particularly for specific industries—such as the Microsoft Style Guide in some information technology settings.
At this point, the writer performs a mechanical edit, checking the document for grammar, punctuation, common word confusions, passive voice, overly long sentences, etc.
