In the instructor blog number 4 it is discussed that many instruction manuals treat the reader as if they are an “idiot” and this is definitely an approach to avoid because it is not a user-centered approach that will likely leave the user frustrated and upset with the entire product or process. As the creator of the instructions you do not want to make the user feel like they are not smart enough to tackle the instructions because they will then decide they do not like the product, process, or place that the instructions were made to describe. In chapter 19 technical, concrete descriptions are discussed and are made up of specific and precise title, and introductions with an overall description, the descriptions of the features, functions, or stages of a process, use of similes, use of graphics , and a conclusion that shows they thing, place or process in action. Creating technical descriptions appears to be a rather in depth, difficult task and should be properly planned for. To create technical descriptions the creator must do the proper research in order to find out the target audience, find out how the audience will use the information, and the context in which they will use it in. Chapter 19 gives a great list of questions to ask yourself when creating technical descriptions that will be very helpful in the project. I learned in chapter 19 that the purpose statement of the technical descriptions should be able to be written clearly in just one sentence. I also learned more about the four different types of readers and how their needs are very different. Chapter 29 also tells how important it is to fully understand the thing, place or process in which you are describing in order to properly present all angles of it. In chapter 20 the basic structure for how instructions should be written is given and is made up of a title, introduction/background, list of parts, tools, and conditions, the numbered steps, the conclusion, and troubleshooting. Chapter 20 was helpful in that it gave examples of descriptive and non descriptive phrases. Chapter 20 also made me realize the importance of placing cautions in the instructions anywhere that the reader could by chance hurt themselves, even if the creator of the instructions does not find something to be dangerous others could, and that is why a creator must look at the instructions from many different view points.
Better to be Safe than Sorry.
For the most part, I found chapters 19 and 20 to be a review. You mention that you “learned more about the four different types of readers and how their needs are very different.” Personally, after reading these chapters, I don’t see much difference in the descriptions of the 4 types of readers here, as opposed to the descriptions of those same readers from previous chapters. Although these descriptions may be more specific to writing descriptions or instructions, the individual readers possess the same needs as before. I do agree with your closing argument, however, that “placing cautions in the instructions anywhere that the reader could by chance hurt themselves” is critical. As I’ve not written detailed instructions in the past, it was new to me to consider anticipating any and all areas where a user could potentially get hurt and to account for each in the instructions.
Indeed a Review
I agree that this felt like a review. The coverage of finding the perfect balance reminded a lot of our previous reading over finding the perfect balance for our cover letter's audiences. Also the four types of readers have been covered previously. I think the fact that these topics are being repeated, stresses their importance. By focusing on these topics, the effectiveness of our documents increases. Especially for people like me, who have had trouble targeting their audience. I would not be surprised if we run into these topics again as they seem to be very applicable to many areas.
Caution R7
When you say “Chapter 20 also made me realize the importance of placing cautions in the instructions anywhere that the reader could by chance hurt themselves…” it made me think of how that is an analogy of a technical document itself. You want to cover all possible angles of caution so the user does not hurt themselves, just as you need to cover all possible angles of instruction so the user does not get lost or do a certain step incorrectly. I find it interesting just how much of writing is trying to cover all possible cracks in the floor of your document.
Shane
Knowledge is king?
As you mention in your reading response it is important to create your document in a user-centered approach. The grey area that I’m trying to figure out is where the fine line of the “idiot” approach is and placing appropriate warning labels. In the instructors blog #4 I really found the batman cape example very interesting. If I was in charge of that product I would honestly never would of thought of putting “Warning: Cape does not allow wearer to fly.” Unfortunately, the “curse of knowledge” can made it a difficult process to write instructions from all perspectives since we already know the knowledge.
Instructor Feedback
Be sure to include concrete examples from your own experiences to really flesh out these reading responses.