Ch. 15: Technical Communication
Technical communication is meant to be useful. People need technical communication when they have to do something or understand something in a practical, functional way. If you’ve ever had to train a new employee, show your parents how to use social media, explain a product’s features to a customer, or teach a sports teammate a new move, you have experience with technical communication.
These kinds of messages can be communicated in a few different ways. The best choice out of these options will depend on the needs created by the situation. Some of the more common forms include:
- Standard Operating Procedure / “How To” Instructions
- Procedural Analysis
- White Paper
- Status Report
- Usability Tests / Interviews / Surveys
Technical Communication: MAPS or PAMS?
We can draw from Chapter 2’s lesson about MAPS to better understand technical communication. Remember, MAPS stands for message, audience, purpose, style. These are the four factors that need to be considered when planning, drafting, and editing your communication.
The most powerful common denominator between different kinds of technical communication is purpose. Technical communication is valuable when it is put to use. This, of course, implies that someone must be using it. Because someone will use the information, audience must also be given priority early on in the planning stage.
Imagine a scenario where you’re teaching someone how to swim. If you’re teaching someone how to swim (purpose), does it matter whether they are a small child or an adult (audience)? Does it matter whether they are a beginner or an Olympic champion (audience)? Ideally, you would consider these variables and other audience awareness factors before deciding which specific swimming skills to teach (message). Hopefully, you would still be mindful of audience when choosing what specific words, gestures, and tone to use (style).
This is a good reminder that MAPS is always useful when you plan your writing, but you don’t always have to start your planning with “M,” the message. Technical communication is needs-based, so your planning will probably go in order of PAMS (purpose, audience, message, style). There is never one perfect order for working with MAPS. Do what works for your situation.
Here are some examples of how different kinds technical communication are defined by their purpose and audience. Notice that when the purpose changes, the ideal audience often changes, too, as does the type of message being communicated.
| Intended Purpose | Communication Type for that Purpose | Sample Audience Type | Sample Message Title |
| To direct someone in how to do something: | Standard Operating Procedure / “How To” Instructions | technicians, individuals | “How to Change a Tire” |
| To explain a complex process to someone: | Procedural Analysis | project leads, supply chain managers, the public | “How Tires Are Manufactured” |
| To summarize a situation so that others can make decisions or take action: | White Paper | political leaders, administrators | “Top 3 Environmental Impacts of Tire Recycling” |
| To update others on the progress of a project: | Status Report | research & development leads, managers, investors | “Using Alternative Materials for Innovative Tire Production” |
| To document user experience: | Usability Tests / Interviews / Surveys | marketing specialists, advertisers, user interface designers | “Testing Snow Tire Handling in Extreme Weather Conditions “ |
In each of these cases, the general topic of “tires” is the same. The defining differences, however, are purpose (what does someone need to do with this information?) and audience (who am I communicating with?). Only once these two pieces are understood can you produce functional, successful technical communication.
