The Basics
In very practical terms, technical communication is used every day by professionals and consumers to solve problems in the workplace. The motive of technical communication is to employ words and images to help readers, not writers, accomplish their goals which might include helping employees learn something important for their job, perform a task on the job, or make critical decisions that impact the long-term security of the company.
Whatever the goal, technical communication should be accessible, clear, and easily understood so readers can accomplish whatever they need by using the message you create. Now letâs lay some groundwork by discussing the basics of technical communication.
Of course, to communicate, you must start with something you want to expressâinformation that is directed to someone, and for our purposes we call that someone the âend user.â
Users in the domain of technical communication are the rhetorical audience who need our documents for some particular workplace purpose. They are the ones that we want to empathize with and plan our writing around in order to give it the strongest effect.
For instance, say you are tasked with writing an internal-proposal for your teamâs latest brainstorm session. The end user might be your immediate supervisor, or even the board of directors at your company. Your end users in this scenario are the decision-makers: the ones that will read your writing and determine whether or not to spend resources on the new project.
While the example of a proposal is a particular genre of technical writing, we should expand our definition of technical communication to include presentations, reports, descriptions, instructions, audiovisual forms, numerical communications, etc.
For instance, in a presentation, the technical communicator would be considering the way a presentation looks and how the design of their communication can help the user stay engaged and how the design might also communicate credibility (or lack thereof).
Itâs important to keep in mind that technical communication can be used in a variety of forms and that elements of document design can influence whether an end user will read and understand the message or whether the document appears confusing or frustrating.
Now we need to focus in on technical writing as a vital category within technical communication, with a functional definition of its own. Technical writing can be defined as the delivery of practical, scientific, or mechanical information in a way that is clear, accurate, and easily accessible for a specific group of people. As we said above, we define those people as users, since the kind of writing weâre talking about is used routinely by people to solve problems in daily life.
Technical communication is also the way important information is shared and passed on in scientific or engineering sites and work-places. Although there are a lot of types of technical writing, theyâre all tied together by a definition that includes the everyday goals of the end user. The definitions below are not mutually exclusive, but important to take into account as features and goals of good technical writing.
Technical writing should:
- Transmit what may be detailed and complex information as quickly and clearly as possible. Although the material may be difficult, your goal is to pass it on to your end user in a succinct and effective manner. Communicate with appropriate complexity, using the right vocabulary, for the user and situation. You must know who your users are and what they need the information for.
- Use standardized forms, called genres, that follow expected and familiar conventions. In this way, technical users can understand more information on the first read and avoid slogging through an unfamiliar format. Itâs the mark of a professional to learn how to communicate in the genre of the community youâre trying to inform or persuade. Anticipate what your end user expects and communicate according to those expectations through problem-solving and critical thinking.
- Be objective. Objectivity is required in most instances of technical writing because the information is whatâs important, not the opinion of the writer. Being objective signals that the focus is on facts, not feelings. Objectivity can assist in presenting a message clearly, without imposing barriers that opinion or bias can create, such as emotion-based disagreements or responses.
Even though technical writing requires objectivity and the human element isnât always present in the writing itself, the technical writer should be conscious that her or his end user is made up of real people with real problems.
Burying meaning in difficult jargon or convoluted phrasing (sometimes called âlegalese,â âacademese,â or any other â-eseâ depending on the audience) will frustrate the userâs goal of getting quickly to the pertinent information they need. Rather, the meaning should be clear and accessible so information is useful and comprehensible.
Attention to the conventions of technical writing, appropriate complexity, proper objectivity, and c...