TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: More alternatives to 'Technical Writer' From:"Evans, Diane L (Rosetta)" <diane_evans -at- merck -dot- com> To:"Techwr-l" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 20 Nov 2007 11:08:35 -0800
>I can understand how solutions might be developed, but not information.
>Info can be stored, retrieved, gathered, enhanced, etc. But developed?
>What am I missing here?
I beg to differ with you, Craig. KNOWLEDGE can be stored and retrieved.
But, is this knowledge the same as information? Probably not.
According to the dictionary, information is the communication of
knowledge, where knowledge is understanding gained through experience or
study.
So, how does knowledge become information? Someone needs to retrieve
the knowledge, then organize it into a method where the information is
communicated to others.
For example, I know that a certain software product still needs work. I
know this from the number and content of bug reports (knowledge). But,
I need to communicate this knowledge to the project manager. I don't
just dump a pile of bug reports on his desk and say, "Look at this stack
of problems!" Instead, I will sort through the bug reports, organize it
into a cohesive report, and give him the document. It might say,
"Although 200 bugs still exist in the software, the following list of
ten bugs must be resolved before the product is shipped." The report
then justifies that position.
So, I took some knowledge and developed information that the project
manager can use to make further project decisions.
That's where the true talent of a technical writer lies -- being able to
present a mass of knowledge cohesively and in a manner that other people
will understand what I am saying. (Look at the two space shuttle
disasters for examples of knowledge that was not converted into
information.)
I really enjoyed my technical communication courses at Utah State. We
learned lots of neat stuff like this.
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
