I think that this weeks readings bring up a good point about Technical Communication/Writing. the first thing I want to talk about is the involved audience. I agree with Johnson in that the best way to know if something will be useful is to get the person who will be using it involved. It's like companies that have the pyramid organization where the people on top make the rules for those on the bottom without knowing what the 'bottom dewlers do.' Usually it results in unhappy employees and policies and procedures that don't work for the everyday transactions that occur. I think it works the same way for technical writers, designers, and audiences. I do feel that the users should be involved in the processes of course not every new technology can be collaboratorated on with hundreds of users, but even a few would be better than none. In the same sense technical writers are also possible users and are the ones that will eventually write the instructions and/or manual so I can agree that they should definitely be involved in the priliminaries and design phases. It just makes sense!
I can also agree that it is rediculous that technical writers are second to scientists, designers, etc. when it comes to new technology. The truth is they are all equally important and I think tech writers are really taken for granted. I must admit, I really never thought about who writes the manual, instructions, guidelines, how to's, etc. Now I see that most eveything we use and "build" or put together is based on a technical writer providing us that information. I supposed people figure that it can't be that hard to write the process of setting something up or putting something together because the idea is already laid out. But when the writer has to deal with edits and stipulations of someone who doesn't know the difference the results and difficulty show.
An example I found this week that just happened to go along with these articles was on target.com I was looking for a washer and dryer for the house I am trying to buy, and so I like to read reviews when I find a good price. I found a great price with a brand named Haier, but all the reviews were virtually the same. The manual for set-up was not user friendly, but the washer was a great buy.
Subscribe to:
Post Comments (Atom)
Posts
You would think it would be obvious to include technical writers and potential users in the early stages of product design. This is true in some places, although it is probably much more common for marketing to be involved early on.
ReplyDeleteOne thing your discussion of the texts created by technical writers and your search for a washer and dryer made me think of a few reasons technical writing is not valued:
1. At the least, someone has to write out the specifications for a product (height, width, etc.); this can be an engineer.
2. A manual can be useful, but is less necessary if the product is well-designed; technically writing can be obviated by good design.
3. Much of the information we seek about products (like in online reviews) can be provided by other users contributing to online databases; a web designer can create the database and the public can fill it with info.