{"id":130,"date":"2018-11-24T20:34:35","date_gmt":"2018-11-25T01:34:35","guid":{"rendered":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/chapter\/writinginstructions\/"},"modified":"2021-02-26T14:36:56","modified_gmt":"2021-02-26T19:36:56","slug":"writinginstructions","status":"publish","type":"chapter","link":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/chapter\/writinginstructions\/","title":{"raw":"7.7 Writing Instructions","rendered":"7.7 Writing Instructions"},"content":{"raw":"One of the most common and important uses of technical writing is to provide instructions, those step-by-step explanations of how to assemble, operate, repair, or do routine maintenance on something. Although they may seems intuitive and simple to write, instructions are some of the worst-written documents you can find. Most of us have probably had many infuriating experiences with badly written instructions. This chapter will show you what professionals consider the best techniques in providing instructions.\n\nAn effective set of instruction requires the following:\n<ul>\n \t<li>Clear, precise, and simple writing<\/li>\n \t<li>A thorough understanding of the procedure in all its technical detail<\/li>\n \t<li>The ability to put yourself in the place of the reader, the person trying to use your instructions<\/li>\n \t<li>The ability to visualize the procedure in detail and to capture that awareness on paper<\/li>\n \t<li>Willingness to test your instructions on the kind of person you wrote them for.<\/li>\n<\/ul>\n<h1>Preliminary Steps<\/h1>\nAt the beginning of a project to write a set of instructions, it is important to determine the structure or characteristics of the particular procedure you are going to write about. Here are some steps to follow:\n<h2>1. <span class=\"runin_heading\">Do a careful audience and task analysis<\/span><\/h2>\nEarly in the process, define the audience and situation of your instructions. Remember that defining an audience means defining the level of familiarity your readers have with the topic.\n<h2><span class=\"runin_heading\">2. Determine the number of tasks<\/span><\/h2>\nHow many tasks are there in the procedure you are writing about? Let's use the term <i>procedure<\/i> to refer to the whole set of activities your instructions are intended to discuss. A <i>task<\/i> is a semi-independent group of actions within the procedure: for example, setting the clock on a microwave oven is one task in the big overall procedure of operating a microwave oven.\n\nA simple procedure like changing the oil in a car contains only one task; there are no semi-independent groupings of activities. A more complex procedure like using a microwave oven contains several semi-independent tasks:\u00a0 setting the clock; setting the power level; using the timer; cleaning and maintaining the microwave, among others.\n\nSome instructions have only a single task, but have many steps within that single task. For example, imagine a set of instructions for assembling a kids' swing set. In my own experience, there were more than a 130 steps! That can be a bit daunting. A good approach is to group similar and related steps into phases, and start renumbering the steps at each new phase. A <i>phase<\/i> then is a group of similar steps within a single-task procedure. In the swing-set example, setting up the frame would be a phase; anchoring the thing in the ground would be another; assembling the box swing would be still another.\n<h2><span class=\"runin_heading\">3.\u00a0 Determine the best approach to the step-by-step discussion<\/span><\/h2>\nFor most instructions, you can focus on tasks, or you can focus on tools (or features of tools).\u00a0 In a <i>task approach<\/i> (also known as task orientation) to instructions on using a phone-answering service, you'd have these sections:\n<ul>\n \t<li>Recording your greeting<\/li>\n \t<li>Playing back your messages<\/li>\n \t<li>Saving your messages<\/li>\n \t<li>Forwarding your messages<\/li>\n \t<li>Deleting your messages, and so on<\/li>\n<\/ul>\nThese are tasks\u2014the typical things we'd want to do with the machine.\n\nOn the other hand, in a <i>tools approach<\/i> to instructions on using a photocopier, there likely would be sections on how to use specific features:\n<ul>\n \t<li>Copy button<\/li>\n \t<li>Cancel button<\/li>\n \t<li>Enlarge\/reduce button<\/li>\n \t<li>Collate\/staple button<\/li>\n \t<li>Copy-size button, and so on<\/li>\n<\/ul>\nIf you designed a set of instructions on this plan, you'd write steps for using each button or feature of the photocopier. Instructions using this tools approach are hard to make work. Sometimes, the name of the button doesn't quite match the task it is associated with; sometimes you have to use more than just the one button to accomplish the task. Still, there can be times when the tools\/feature approach may be preferable.\n<h2><span class=\"runin_heading\">4.\u00a0 Design groupings of tasks<\/span><\/h2>\nListing tasks may not be all that you need to do. There may be so many tasks that you must group them so that readers can find individual ones more easily. For example, the following are common task groupings in instructions:\n<ol>\n \t<li>Unpacking and setup tasks<\/li>\n \t<li>Installing and customizing tasks<\/li>\n \t<li>Basic operating tasks<\/li>\n \t<li>Routine maintenance tasks<\/li>\n \t<li>Troubleshooting tasks.<\/li>\n<\/ol>\n<h1>Common Sections in Instructions<\/h1>\nThe following is a review of the sections you'll commonly find in instructions. Don't assume that each one of them <i>must<\/i> be in the actual instructions you write, nor that they have to be in the order presented here, nor that these are the only sections possible in a set of instructions.\n<p class=\"textbox__title\">For alternative formats, check out the <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/models.html#instructions\" target=\"_blank\" rel=\"noopener\">example instructions<\/a>.<span class=\"figure_label\"><\/span><\/p>\n\n<div class=\"textbox textbox--learning-objectives\"><header class=\"textbox__header\">A Set of Instructions Often Includes the Following<\/header>\n<div class=\"textbox__content\">\n\n<strong><span class=\"runin_heading\">Introduction:\u00a0<\/span><\/strong> plan the introduction to your instructions carefully. It might include any of the following (but not necessarily in this order):\n<ul>\n \t<li>Indicate the specific tasks or procedure to be explained as well as the scope (what will and will not be covered)<\/li>\n \t<li>Indicate what the audience needs in terms of knowledge and background to understand the instructions<\/li>\n \t<li>Give a general idea of the procedure and what it accomplishes<\/li>\n \t<li>Indicate the conditions when these instructions should (or should not) be used<\/li>\n \t<li>Give an overview of the contents of the instructions.<\/li>\n<\/ul>\n<span class=\"runin_heading\"><strong>General warning, caution, danger notices<\/strong>:\u00a0<\/span> instructions often must alert readers to the possibility of ruining their equipment, screwing up the procedure, and hurting themselves. Also, instructions must often emphasize key points or exceptions. For these situations, you use <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/notices.html\" target=\"_blank\" rel=\"noopener\">special notices<\/a>\u2014note, warning, caution, and danger notices. Notice how these special notices are used in the example instructions listed above.\n\n<strong><span class=\"runin_heading\">Technical background or theory:\u00a0<\/span> <\/strong>at the beginning of certain kinds of instructions (after the introduction), you may need a discussion of background related to the procedure. For certain instructions, this background is critical\u2014otherwise, the steps in the procedure make no sense. For example, you may have had some experience with those software applets in which you define your own colors by nudging red, green, and blue slider bars around. To really understand what you're doing, you need to have some background on color. Similarly, you can imagine that, for certain instructions using cameras, some theory might be needed as well.\n\n<strong><span class=\"runin_heading\">Equipment and supplies:\u00a0<\/span><\/strong> notice that most instructions include a list of the things you need to gather before you start the procedure. This includes <i>equipment<\/i>, the tools you use in the procedure (such as mixing bowls, spoons, bread pans, hammers, drills, and saws) and <i>supplies<\/i>, the things that are consumed in the procedure (such as wood, paint, oil, flour, and nails). In instructions, these typically are listed either in a simple vertical list or in a two-column list. Use the two-column list if you need to add some specifications to some or all of the items\u2014for example, brand names, sizes, amounts, types, model numbers, and so on.\n\n<strong><span class=\"runin_heading\">Discussion of the steps:\u00a0<\/span><\/strong> when you get to the actual writing of the steps, there are several things to keep in mind: (1) the structure and format of those steps, (2) supplementary information that might be needed, and (3) the point of view and general writing style.\n\n<strong><span class=\"subrunin_heading\">Structure and format:\u00a0<\/span><\/strong> normally, we imagine a set of instructions as being formatted as vertical numbered lists. And most are in fact. Normally, you format your actual step-by-step instructions this way. There are some variations, however, as well as some other considerations:\n<ul>\n \t<li><strong><i>Fixed-order steps<\/i><\/strong> are steps that must be performed in the order presented. For example, if you are changing the oil in a car, draining the oil is a step that <i>must<\/i> come before putting the new oil. These are numbered lists (usually, vertical numbered lists).<\/li>\n \t<li><strong><em>Variable-order steps<\/em><\/strong> are steps that can be performed in practically any order. Good examples are those troubleshooting guides that tell you to check this, check that where you are trying to fix something. You can do these kinds of steps in practically any order. With this type, the bulleted list is the appropriate format.<\/li>\n \t<li><strong><i>Alternate steps<\/i><\/strong> are those in which two or more ways to accomplish the same thing are presented. Alternate steps are also used when various conditions might exist. Use bulleted lists with this type, with OR inserted between the alternatives, or the lead-in indicating that alternatives are about to be presented.<\/li>\n \t<li><strong><i>Nested steps <\/i><\/strong>may be used in\u00a0 cases when individual steps within a procedure are rather complex in their own right and need to be broken down into sub-steps. In this case, you indent further and sequence the sub-steps as a, b, c, and so on.<\/li>\n \t<li><strong><i>\"Step-less\" instructions<\/i><\/strong>. can be used when you really cannot use numbered vertical list or provide straightforward instructional-style directing of the reader. Some situations must be so generalized or so variable that steps cannot be stated.<\/li>\n<\/ul>\n<strong><span class=\"subrunin_heading\">Supplementary discussion:<\/span> <\/strong>often, it is not enough simply to tell readers to do this or to do that. They need additional explanatory information such as how the thing should look before and after the step; why they should care about doing this step; what mechanical principle is behind what they are doing; even more micro-level explanation of the step\u2014discussion of the specific actions that make up the step.\n\nThe problem with supplementary discussion, however, is that it can hide the actual step. You want the actual step\u2014the specific actions the reader is to take\u2014to stand out. You don't want it all buried in a heap of words. There are at least two techniques to avoid this problem: you can split the instruction from the supplement into separate paragraphs; or you can bold the instruction.\n\n<\/div>\n<\/div>\n<h1><span class=\"subrunin_heading\">Writing Style<\/span><\/h1>\nPlacing the key user steps in <strong>bold<\/strong> can a very helpful way to signal clearly what the reader needs to do.\u00a0 Often the command verb is bolded; sometimes bold font highlights the key component being discussed.\n\nUse of the <strong>passive voice<\/strong> in instructions can be problematic. For some strange reason, some instructions sound like this: \"The <strong>Pause<\/strong> button should be depressed in order to stop the display temporarily.\" Not only are we worried about the pause button's mental health, but we wonder who's supposed to depress the thing (<em>ninjas<\/em>?). It would be more helpful to indicate when the reader must \"<strong>press<\/strong> the Pause button.\"\u00a0\u00a0 Consider this example: \"The Timer button is then set to 3:00.\" Again, one might ask, \"is set by whom?\u00a0 <em>Ninjas<\/em>?\" The person following these instructions might think it is simply a reference to some existing state, or she might wonder, \"Are they talking to me?\" Using the third person can also lead to awkwardness: \"The user should then press the Pause button.\" Instructions should typically be written using command verb forms and using \"you\" to make it perfectly clear what the reader should do.\n<h1>Illustrating Your Instructions<\/h1>\nPerhaps more than in any other form of technical writing, graphics are crucial to instructions. Sometimes, words simply cannot explain the step. Illustrations are often critical to the readers' ability to visualize what they are supposed to do.\u00a0 Be sure that the graphics represent the image from the reader's perspective.\n<h1>Formatting Your Instructions<\/h1>\nSince people rarely <em>want<\/em> to read instructions, but often <em>have<\/em> to, format your instructions for reluctant readability. Try to make your reader <em>want<\/em> to read them, or at least not <em>resistant<\/em> to the idea of consulting them.\u00a0 Highly readable format will allow readers who have figured out some of the instructions on their own to skip to the section where they are stuck.\u00a0 Use what you have learned about <a href=\"\/technicalwritingh5p\/chapter\/headings\/\" target=\"_blank\" rel=\"noopener\">headings<\/a>, <a href=\"\/technicalwritingh5p\/chapter\/lists\/\" target=\"_blank\" rel=\"noopener\">lists<\/a>, <a href=\"\/technicalwritingh5p\/chapter\/figurestables\/\" target=\"_blank\" rel=\"noopener\">visuals<\/a>, and passive space to create effective and readable instructions:\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Headings<\/strong>:<span><\/span><\/span> normally, you'd want headings for any background section you might have, the equipment and supplies section, a general heading for the actual instructions section, and subheadings for the individual tasks or phases within that section.<\/p>\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Lists<\/strong>:<\/span> similarly, instructions typically make extensive use of lists, particularly numbered vertical lists for the actual step-by-step explanations. Simple vertical lists or two-column lists are usually good for the equipment and supplies section. In-sentence lists are good whenever you give an overview of things to come.<\/p>\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Special Notices<\/strong>:\u00a0 you may have to <\/span>alert readers to possibilities in which they may damage their equipment, waste supplies, cause the entire procedure to fail, injure themselves or others\u2014even seriously or fatally. Companies have been sued for lack of these special notices, for poorly written special notices, or for special notices that were out of place. See <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/notices.html\" target=\"_blank\" rel=\"noopener\">special notices<\/a> for a complete discussion of the proper use of these special notices as well as their format and placement within instructions.<\/p>\n\n<div class=\"textbox textbox--learning-objectives\"><header class=\"textbox__header\">Revision Checklist for Written Instructions<\/header>\n<div class=\"textbox__content\">\n\nAs you reread and revise your instructions, check that they do the following:\n<ul>\n \t<li>Clearly describe the exact procedure to be explained<\/li>\n \t<li>Provide an overview of content<\/li>\n \t<li>Indicate audience requirements<\/li>\n \t<li>Use various types of lists wherever appropriate; in particular, use numbered lists for sequential steps<\/li>\n \t<li>Use headings and subheadings to divide the main sections and subsections in a logical, coherent order<\/li>\n \t<li>Use special notices as appropriate<\/li>\n \t<li>Use graphics to illustrate key actions and objects<\/li>\n \t<li>Provide additional supplementary explanation of the steps as necessary<\/li>\n \t<li>Create a section listing equipment and supplies if necessary.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n\n<hr>\n\n<div class=\"textbox\">This chapter was adapted from <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\" target=\"_blank\" rel=\"noopener\">Online Technical Writing<\/a> by David McMurrey, which is under a <a href=\"https:\/\/creativecommons.org\/licenses\/by\/4.0\" target=\"_blank\" rel=\"noopener\">Creative Commons Attribution 4.0 International License<\/a>.<\/div>","rendered":"<p>One of the most common and important uses of technical writing is to provide instructions, those step-by-step explanations of how to assemble, operate, repair, or do routine maintenance on something. Although they may seems intuitive and simple to write, instructions are some of the worst-written documents you can find. Most of us have probably had many infuriating experiences with badly written instructions. This chapter will show you what professionals consider the best techniques in providing instructions.<\/p>\n<p>An effective set of instruction requires the following:<\/p>\n<ul>\n<li>Clear, precise, and simple writing<\/li>\n<li>A thorough understanding of the procedure in all its technical detail<\/li>\n<li>The ability to put yourself in the place of the reader, the person trying to use your instructions<\/li>\n<li>The ability to visualize the procedure in detail and to capture that awareness on paper<\/li>\n<li>Willingness to test your instructions on the kind of person you wrote them for.<\/li>\n<\/ul>\n<h1>Preliminary Steps<\/h1>\n<p>At the beginning of a project to write a set of instructions, it is important to determine the structure or characteristics of the particular procedure you are going to write about. Here are some steps to follow:<\/p>\n<h2>1. <span class=\"runin_heading\">Do a careful audience and task analysis<\/span><\/h2>\n<p>Early in the process, define the audience and situation of your instructions. Remember that defining an audience means defining the level of familiarity your readers have with the topic.<\/p>\n<h2><span class=\"runin_heading\">2. Determine the number of tasks<\/span><\/h2>\n<p>How many tasks are there in the procedure you are writing about? Let&#8217;s use the term <i>procedure<\/i> to refer to the whole set of activities your instructions are intended to discuss. A <i>task<\/i> is a semi-independent group of actions within the procedure: for example, setting the clock on a microwave oven is one task in the big overall procedure of operating a microwave oven.<\/p>\n<p>A simple procedure like changing the oil in a car contains only one task; there are no semi-independent groupings of activities. A more complex procedure like using a microwave oven contains several semi-independent tasks:\u00a0 setting the clock; setting the power level; using the timer; cleaning and maintaining the microwave, among others.<\/p>\n<p>Some instructions have only a single task, but have many steps within that single task. For example, imagine a set of instructions for assembling a kids&#8217; swing set. In my own experience, there were more than a 130 steps! That can be a bit daunting. A good approach is to group similar and related steps into phases, and start renumbering the steps at each new phase. A <i>phase<\/i> then is a group of similar steps within a single-task procedure. In the swing-set example, setting up the frame would be a phase; anchoring the thing in the ground would be another; assembling the box swing would be still another.<\/p>\n<h2><span class=\"runin_heading\">3.\u00a0 Determine the best approach to the step-by-step discussion<\/span><\/h2>\n<p>For most instructions, you can focus on tasks, or you can focus on tools (or features of tools).\u00a0 In a <i>task approach<\/i> (also known as task orientation) to instructions on using a phone-answering service, you&#8217;d have these sections:<\/p>\n<ul>\n<li>Recording your greeting<\/li>\n<li>Playing back your messages<\/li>\n<li>Saving your messages<\/li>\n<li>Forwarding your messages<\/li>\n<li>Deleting your messages, and so on<\/li>\n<\/ul>\n<p>These are tasks\u2014the typical things we&#8217;d want to do with the machine.<\/p>\n<p>On the other hand, in a <i>tools approach<\/i> to instructions on using a photocopier, there likely would be sections on how to use specific features:<\/p>\n<ul>\n<li>Copy button<\/li>\n<li>Cancel button<\/li>\n<li>Enlarge\/reduce button<\/li>\n<li>Collate\/staple button<\/li>\n<li>Copy-size button, and so on<\/li>\n<\/ul>\n<p>If you designed a set of instructions on this plan, you&#8217;d write steps for using each button or feature of the photocopier. Instructions using this tools approach are hard to make work. Sometimes, the name of the button doesn&#8217;t quite match the task it is associated with; sometimes you have to use more than just the one button to accomplish the task. Still, there can be times when the tools\/feature approach may be preferable.<\/p>\n<h2><span class=\"runin_heading\">4.\u00a0 Design groupings of tasks<\/span><\/h2>\n<p>Listing tasks may not be all that you need to do. There may be so many tasks that you must group them so that readers can find individual ones more easily. For example, the following are common task groupings in instructions:<\/p>\n<ol>\n<li>Unpacking and setup tasks<\/li>\n<li>Installing and customizing tasks<\/li>\n<li>Basic operating tasks<\/li>\n<li>Routine maintenance tasks<\/li>\n<li>Troubleshooting tasks.<\/li>\n<\/ol>\n<h1>Common Sections in Instructions<\/h1>\n<p>The following is a review of the sections you&#8217;ll commonly find in instructions. Don&#8217;t assume that each one of them <i>must<\/i> be in the actual instructions you write, nor that they have to be in the order presented here, nor that these are the only sections possible in a set of instructions.<\/p>\n<p class=\"textbox__title\">For alternative formats, check out the <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/models.html#instructions\" target=\"_blank\" rel=\"noopener\">example instructions<\/a>.<span class=\"figure_label\"><\/span><\/p>\n<div class=\"textbox textbox--learning-objectives\">\n<header class=\"textbox__header\">A Set of Instructions Often Includes the Following<\/header>\n<div class=\"textbox__content\">\n<p><strong><span class=\"runin_heading\">Introduction:\u00a0<\/span><\/strong> plan the introduction to your instructions carefully. It might include any of the following (but not necessarily in this order):<\/p>\n<ul>\n<li>Indicate the specific tasks or procedure to be explained as well as the scope (what will and will not be covered)<\/li>\n<li>Indicate what the audience needs in terms of knowledge and background to understand the instructions<\/li>\n<li>Give a general idea of the procedure and what it accomplishes<\/li>\n<li>Indicate the conditions when these instructions should (or should not) be used<\/li>\n<li>Give an overview of the contents of the instructions.<\/li>\n<\/ul>\n<p><span class=\"runin_heading\"><strong>General warning, caution, danger notices<\/strong>:\u00a0<\/span> instructions often must alert readers to the possibility of ruining their equipment, screwing up the procedure, and hurting themselves. Also, instructions must often emphasize key points or exceptions. For these situations, you use <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/notices.html\" target=\"_blank\" rel=\"noopener\">special notices<\/a>\u2014note, warning, caution, and danger notices. Notice how these special notices are used in the example instructions listed above.<\/p>\n<p><strong><span class=\"runin_heading\">Technical background or theory:\u00a0<\/span> <\/strong>at the beginning of certain kinds of instructions (after the introduction), you may need a discussion of background related to the procedure. For certain instructions, this background is critical\u2014otherwise, the steps in the procedure make no sense. For example, you may have had some experience with those software applets in which you define your own colors by nudging red, green, and blue slider bars around. To really understand what you&#8217;re doing, you need to have some background on color. Similarly, you can imagine that, for certain instructions using cameras, some theory might be needed as well.<\/p>\n<p><strong><span class=\"runin_heading\">Equipment and supplies:\u00a0<\/span><\/strong> notice that most instructions include a list of the things you need to gather before you start the procedure. This includes <i>equipment<\/i>, the tools you use in the procedure (such as mixing bowls, spoons, bread pans, hammers, drills, and saws) and <i>supplies<\/i>, the things that are consumed in the procedure (such as wood, paint, oil, flour, and nails). In instructions, these typically are listed either in a simple vertical list or in a two-column list. Use the two-column list if you need to add some specifications to some or all of the items\u2014for example, brand names, sizes, amounts, types, model numbers, and so on.<\/p>\n<p><strong><span class=\"runin_heading\">Discussion of the steps:\u00a0<\/span><\/strong> when you get to the actual writing of the steps, there are several things to keep in mind: (1) the structure and format of those steps, (2) supplementary information that might be needed, and (3) the point of view and general writing style.<\/p>\n<p><strong><span class=\"subrunin_heading\">Structure and format:\u00a0<\/span><\/strong> normally, we imagine a set of instructions as being formatted as vertical numbered lists. And most are in fact. Normally, you format your actual step-by-step instructions this way. There are some variations, however, as well as some other considerations:<\/p>\n<ul>\n<li><strong><i>Fixed-order steps<\/i><\/strong> are steps that must be performed in the order presented. For example, if you are changing the oil in a car, draining the oil is a step that <i>must<\/i> come before putting the new oil. These are numbered lists (usually, vertical numbered lists).<\/li>\n<li><strong><em>Variable-order steps<\/em><\/strong> are steps that can be performed in practically any order. Good examples are those troubleshooting guides that tell you to check this, check that where you are trying to fix something. You can do these kinds of steps in practically any order. With this type, the bulleted list is the appropriate format.<\/li>\n<li><strong><i>Alternate steps<\/i><\/strong> are those in which two or more ways to accomplish the same thing are presented. Alternate steps are also used when various conditions might exist. Use bulleted lists with this type, with OR inserted between the alternatives, or the lead-in indicating that alternatives are about to be presented.<\/li>\n<li><strong><i>Nested steps <\/i><\/strong>may be used in\u00a0 cases when individual steps within a procedure are rather complex in their own right and need to be broken down into sub-steps. In this case, you indent further and sequence the sub-steps as a, b, c, and so on.<\/li>\n<li><strong><i>&#8220;Step-less&#8221; instructions<\/i><\/strong>. can be used when you really cannot use numbered vertical list or provide straightforward instructional-style directing of the reader. Some situations must be so generalized or so variable that steps cannot be stated.<\/li>\n<\/ul>\n<p><strong><span class=\"subrunin_heading\">Supplementary discussion:<\/span> <\/strong>often, it is not enough simply to tell readers to do this or to do that. They need additional explanatory information such as how the thing should look before and after the step; why they should care about doing this step; what mechanical principle is behind what they are doing; even more micro-level explanation of the step\u2014discussion of the specific actions that make up the step.<\/p>\n<p>The problem with supplementary discussion, however, is that it can hide the actual step. You want the actual step\u2014the specific actions the reader is to take\u2014to stand out. You don&#8217;t want it all buried in a heap of words. There are at least two techniques to avoid this problem: you can split the instruction from the supplement into separate paragraphs; or you can bold the instruction.<\/p>\n<\/div>\n<\/div>\n<h1><span class=\"subrunin_heading\">Writing Style<\/span><\/h1>\n<p>Placing the key user steps in <strong>bold<\/strong> can a very helpful way to signal clearly what the reader needs to do.\u00a0 Often the command verb is bolded; sometimes bold font highlights the key component being discussed.<\/p>\n<p>Use of the <strong>passive voice<\/strong> in instructions can be problematic. For some strange reason, some instructions sound like this: &#8220;The <strong>Pause<\/strong> button should be depressed in order to stop the display temporarily.&#8221; Not only are we worried about the pause button&#8217;s mental health, but we wonder who&#8217;s supposed to depress the thing (<em>ninjas<\/em>?). It would be more helpful to indicate when the reader must &#8220;<strong>press<\/strong> the Pause button.&#8221;\u00a0\u00a0 Consider this example: &#8220;The Timer button is then set to 3:00.&#8221; Again, one might ask, &#8220;is set by whom?\u00a0 <em>Ninjas<\/em>?&#8221; The person following these instructions might think it is simply a reference to some existing state, or she might wonder, &#8220;Are they talking to me?&#8221; Using the third person can also lead to awkwardness: &#8220;The user should then press the Pause button.&#8221; Instructions should typically be written using command verb forms and using &#8220;you&#8221; to make it perfectly clear what the reader should do.<\/p>\n<h1>Illustrating Your Instructions<\/h1>\n<p>Perhaps more than in any other form of technical writing, graphics are crucial to instructions. Sometimes, words simply cannot explain the step. Illustrations are often critical to the readers&#8217; ability to visualize what they are supposed to do.\u00a0 Be sure that the graphics represent the image from the reader&#8217;s perspective.<\/p>\n<h1>Formatting Your Instructions<\/h1>\n<p>Since people rarely <em>want<\/em> to read instructions, but often <em>have<\/em> to, format your instructions for reluctant readability. Try to make your reader <em>want<\/em> to read them, or at least not <em>resistant<\/em> to the idea of consulting them.\u00a0 Highly readable format will allow readers who have figured out some of the instructions on their own to skip to the section where they are stuck.\u00a0 Use what you have learned about <a href=\"\/technicalwritingh5p\/chapter\/headings\/\" target=\"_blank\" rel=\"noopener\">headings<\/a>, <a href=\"\/technicalwritingh5p\/chapter\/lists\/\" target=\"_blank\" rel=\"noopener\">lists<\/a>, <a href=\"\/technicalwritingh5p\/chapter\/figurestables\/\" target=\"_blank\" rel=\"noopener\">visuals<\/a>, and passive space to create effective and readable instructions:<\/p>\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Headings<\/strong>:<span><\/span><\/span> normally, you&#8217;d want headings for any background section you might have, the equipment and supplies section, a general heading for the actual instructions section, and subheadings for the individual tasks or phases within that section.<\/p>\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Lists<\/strong>:<\/span> similarly, instructions typically make extensive use of lists, particularly numbered vertical lists for the actual step-by-step explanations. Simple vertical lists or two-column lists are usually good for the equipment and supplies section. In-sentence lists are good whenever you give an overview of things to come.<\/p>\n<p style=\"padding-left: 30px;\"><span class=\"runin_heading\"><strong>Special Notices<\/strong>:\u00a0 you may have to <\/span>alert readers to possibilities in which they may damage their equipment, waste supplies, cause the entire procedure to fail, injure themselves or others\u2014even seriously or fatally. Companies have been sued for lack of these special notices, for poorly written special notices, or for special notices that were out of place. See <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\/notices.html\" target=\"_blank\" rel=\"noopener\">special notices<\/a> for a complete discussion of the proper use of these special notices as well as their format and placement within instructions.<\/p>\n<div class=\"textbox textbox--learning-objectives\">\n<header class=\"textbox__header\">Revision Checklist for Written Instructions<\/header>\n<div class=\"textbox__content\">\n<p>As you reread and revise your instructions, check that they do the following:<\/p>\n<ul>\n<li>Clearly describe the exact procedure to be explained<\/li>\n<li>Provide an overview of content<\/li>\n<li>Indicate audience requirements<\/li>\n<li>Use various types of lists wherever appropriate; in particular, use numbered lists for sequential steps<\/li>\n<li>Use headings and subheadings to divide the main sections and subsections in a logical, coherent order<\/li>\n<li>Use special notices as appropriate<\/li>\n<li>Use graphics to illustrate key actions and objects<\/li>\n<li>Provide additional supplementary explanation of the steps as necessary<\/li>\n<li>Create a section listing equipment and supplies if necessary.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<hr \/>\n<div class=\"textbox\">This chapter was adapted from <a href=\"https:\/\/www.prismnet.com\/~hcexres\/textbook\" target=\"_blank\" rel=\"noopener\">Online Technical Writing<\/a> by David McMurrey, which is under a <a href=\"https:\/\/creativecommons.org\/licenses\/by\/4.0\" target=\"_blank\" rel=\"noopener\">Creative Commons Attribution 4.0 International License<\/a>.<\/div>\n","protected":false},"author":103,"menu_order":7,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-130","chapter","type-chapter","status-publish","hentry"],"part":110,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapters\/130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/wp\/v2\/users\/103"}],"version-history":[{"count":1,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapters\/130\/revisions"}],"predecessor-version":[{"id":131,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapters\/130\/revisions\/131"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/parts\/110"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapters\/130\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/pressbooks\/v2\/chapter-type?post=130"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/wp\/v2\/contributor?post=130"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/technicalwritingh5p\/wp-json\/wp\/v2\/license?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}