The reading responses this week were about how to use what we have already learned about knowing your audience, and how to apply that to writing technical instructions. The readings focuses on how you can make sure you instructions are "user-centered" instead of them being "system-centered." Making the mistake of having your instructions "system-centered" will only frustrate the user and probably cause the instructions to be ignored.
I usually try avoiding instructions as long as I can and only look at them if I have some problem with the product that I can't figure out. However when I do look at the instructions I scan them really quickly looking for a solution about my problem. If I cannot find that solution quickly, or do not understand what the instructions say, it will probably be the last time I bother looking in the instructions for that product. So making your instructions easy to read, and easy to find things in is very important.
Just recently I had to try taking the door panel off my car in order to try and fix a problem with my window. After looking through the car manual for any mention of the door or windows, I quickly gave up without finding any answers. Instead I just went into the next room and had my dad show me how to do it.
Along with making instructions clear and easy to understand, its also very important with a "user-centered" approach to not overestimate your users knowledge level with the product as well as not treat them like they are an idiot for not knowing whats in the instructions. I am guilty of this when helping my family try and fix their computer problems over the phone. I often tell them to do things like make sure you have "switch x" turned on and then try it, only to have them respond, "whats that switch look like? and where is it on the computer?"
Bad instructions.
Like you said, making sure to gear your writing to the people reading it, and not the systems itself, is one of the most important parts to technical writing. When it comes to reading instructions I tend to be rather stubborn. I would rather take twice as long trying to figure it out than if I would just follow the instructions. I guess that’s one of those typical guy things. I feel the same way as you when it comes to bad instructions, which are typically what you get when you are trying to do something. If the documents don’t help me like they are supposed to I end up crumpling them up and throwing them somewhere.
Instructions: A Last Resort at Best
I think you speak for everyone when you say “I usually try avoiding instructions as long as I can and only look at them if I have some problem with the product that I can't figure out.” Much like you, I hate having to refer to the instructions for a product or process and when I hit the packet, I’m at best scanning; I refuse to read them as they're too frequently a disappointment. If I don’t come across that which I desire quickly, then the instructions will find the nearest trash can. Furthermore, I too am guilty of demeaning instructions when assisting family with computer problems, but in my defense, too often is it a repeat problem that I thoroughly explained a number of times before.