1. WHAT IS TECHNICAL COMMUNICATION?
Chapter 1 Learning Objectives
This chapter will help you
- Understand what technical writing is, why its important, and what it looks like
- Apply a “problem-solving” approach to communications tasks, starting by learning how to fully define the problem before looking for solutions
- Recognize the main conventions and characteristics of technical writing, and how they differ from other forms, such as academic and journalistic writing
- Understand the importance of defining the “rhetorical situation” in which you are communicating
- Apply what you have learned so far by examining “case studies” that demonstrate the costs of p/technicalwriting/chapter/1-2-understanding-the-rhetorical-situation//technicalwriting/chapter/understandingrhetoricalsituation/oor communication
- Appreciate the complexity and iterative nature of a writing process in determining what writing process works best for you.
When you hear the term “technical communication,” what comes to mind? Perhaps you think of scientific reports, specifications, instructions, software documentation, or technical manuals. And you would be correct. However, technical communication is so much more than that. Technical Writing is a genre of non-fiction writing that encompasses not only technical materials such as manuals, instructions, specifications, and software documentation, but it also includes writing produced in day-to-day business operations such as correspondence, proposals, internal communications, media releases, and many kinds of reports. It includes the communication of specialized technical information, whether relating to computers and scientific instruments, or the intricacies of meditation. And because oral and visual presentations are such an important part of professional life, technical communication also encompasses these as well.
Why are Technical Communication Skills Important?
In a recent presentation on the topic of Co-op Work Term Reports, [1] the Engineering co-op coordinator for the University of Victoria presented the following statistics regarding the importance of communication skills in the professional world of engineering:
The Reality: Technical Writing and Communication
- How graduate engineers spend their time:
- 25-50% Problem solving of some kind
- 50-75% Communicating (Writing and reading reports, letters, memos, proposals, presentations, discussions w/colleagues, managers, clients)
- Performance evaluations and job advancement usually depend more on communications skills than on technical skills
He added that engineers who are more advanced in their careers spend only 5-10% of their time engaged in problem solving of some kind and 90-95% of their time engaging in related communications tasks: researching, writing and reading reports, proposals, emails, letters, memos; giving or attending presentations; discussing and meeting with colleagues, team mates, managers, clients, and so forth. In a recent survey of over 1000 professionals from various professions, over 70% of engineers and almost 50% of programmers rated the quality of their writing as either “very important” or “extremely important” to the performance of their jobs.[2] Clearly, as Barry Hyman asserts in Fundamentals of Engineering Design, “the stereotype that engineering is for inarticulate nerds is way off base.” [3]
Technical communication is “transactional” – it entails a purposeful transaction between sender and receiver that provides specific information for practical and specific purposes (informing, instructing, persuading) and is usually geared towards the needs of a specific audience. Technical communicators produce a wide variety of documents and other products, such as
- Proposals and requests for proposals (RFPs)
- Technical or research reports
- Documentation records and product specifications
- User guides (step-by-step instructions, procedures, manuals)
- Online help, technical support
- Reference information (encylopedia-style information)
- Consumer literature (information for the public about regulations, safety issues, etc.)
- Marketing literature (product specifications, brochures, promotional literature)
- Technical journalism (found in trade magazines, media releases, etc.)
Thus, it is a highly “designed” form of communication that requires practitioners to have a heightened awareness of the conventions (rules and expectations) and rhetorical situations (audience, purpose, context) in which they are communicating.
This textbook aims to provide you with that heightened awareness – that is, to introduce you to the basic conventions of technical communications, and to train you to take a reader-centred or audience-centred approach to communications tasks, to find the tools and methods that will work best to communicate your ideas to your target audience, and to achieve the desired results.
What Does Technical Writing Look Like?
Technical communications can take many forms, depending on the purpose and intended audience. Consider the following example of technical writing, which is an excerpt adapted from a book called Scientific Sailboat Racing by Ted Wells. [4] From the excerpt in the box below, what can you tell about the intended audience?
The most common question asked by skippers wanting to get to the windward mark faster than they have been doing is “How can I make my boat point higher?” Getting to the windward mark first depends primarily on the skill and experience of the skipper; however, having a well-rigged boat will make a significant difference. Look for the following, in order of importance:
- Sails: Have good quality sails, and use the appropriate sails for the wind conditions expected. No one can win races with poor sails, so use the best you can afford. Keep in mind that the leeches of all sails flutter a little, the jib will backwind the luff of the main on any full or medium sail, and in very light wind, even a perfectly cut sail will probably develop a wrinkle along the front of the battens. If the sails are obviously no good, replace them.
- Mast and Centerboard: Ensure that the mast is far enough forward and the centerboard is far enough back so that there is little or no weather helm. Make sure the stiffness of the mast suits the sails.
- Jib Fairleads: Ensure jib fairleads are properly located for the type of jib being used and the strength of wind expected.
- Cleats: Have cleats for both jib and mainsheet; place cleats so that crew can easily make small adjustments for varying wind velocities and hang on the to the jib sheet without having it pop out of the cleat.
- Traveler: Have a mainsheet traveler that allows the main to be pulled down without pulling the boom in too far; it should allow the sail to be pulled down tightly enough so that the leech does not fall off without pulling the boom in any further than it should be.
- Tiller: Have a flexible tiller extension that allows you to sit well forward, but can be adjusted so that it does not get in the way when coming about.
- Boat Weight: Keep the boat as close to minimum weight as possible. Clearly, a lighter boat is easier to handle, but this is not as critical as other factors. If choosing between a lighter crew member with less skill and experience, and a heavier crew member who has greater skill, the latter is usually preferable.
Once the boat is properly set up, a skilled and experienced skipper can point significantly higher than expected by understanding and using wind deflection from other boats. Immediately to leeward of any boat and extending for a distance of about three mast lengths, there is a wind shadow where the wind velocity is greatly decreased. To leeward of the bow of the boat there is a very small region where the direction of the wind is deflected opposite to the normal deflection and where the velocity is accelerated slightly (see Figure 34). Except in the direct wind shadow, the deflection of the wind is more important than the decrease in wind velocity, as the decrease in velocity is very slight except in the immediate shadow of the sails of the windward boat.
Because of this wind deflection, a boat on the opposite tack cutting behind another boat will be able to point appreciably higher than it normally would. Many skippers on port tacks who thought they could clear starboard tackers have been fooled by not realizing this fact. The deflection of their wind in trying to cross in front of the starboard tacker will enable the starboard tacker to point higher without luffing than he normally would be able to do, and the port tacker who thought he could squeeze by suddenly finds that he cannot (See Figure 35).
EXERCISE 1.1 Draft some technical writing related to your interests
Reflect on the description and example of technical writing above in relation to your experience as an employee, as a student, or as a practitioner of a hobby. What kinds of documents have you written that could fall under the genre of Technical Writing?
Write a paragraph or two on a topic about which you have specialized knowledge, and can use specialized terminology to explain the idea or instruct the reader. For example, you might write about effective techniques for executing certain skateboard maneuvers or how to execute a yoga position such as a “downward facing dog.” Consider your audience when choosing how to write this. Will the audience have to be familiar with the terminology used, as in the above sailing example? See if you can “baffle me with your techno-jargon” and then re-write for a general audience, using plain language.
- S. McConkey, “Writing a work term report,” ENGR 120 Plenary Lecture, University of Victoria, March 3, 2017. ↵
- J. Swartz, S. Pigg, J. Larsen, J. Helo Gonzalez, R. De Haas, and E. Wagner, "Communication in the workplace: What can NC State students expect?" Professional Writing Program, North Carolina State University, 2018 [Online]. Available: https://docs.google.com/document/d/1pMpVbDRWIN6HssQQQ4MeQ6U-oB-sGUrtRswD7feuRB0/edit ↵
- B. Hyman, “Ch. 2: Problem formulation,” in Fundamentals of Engineering Design, Upper Saddle River, NJ: Prentice Hall, 2002, p. 42. ↵
- T. Wells, Scientific Sailboat Racing, New York: Dodd, Mead, and Co., 1950, pp. 94-96. ↵
