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: Definition of Tech Writer, was STC is broken From:Ned Bedinger <doc -at- edwordsmith -dot- com> To:Sam Beard <sbeard -at- oico -dot- com> Date:Tue, 06 May 2008 08:31:20 -0700
Sam Beard wrote:
> An apt analogy, in many respects. I agree that you shouldn't stop
> researching until, at the very least, you get the answers you need. What
> I'm wondering about is the difference Lauren was trying to make between
> outside research and (presumably) "inside" research. Does this refer to
> research outside of the normal parameters of the job and the information
> "necessary" to do the job? What exactly constitutes such a thing? How
> does one know which is which?
I don't want to assume the risk of defining business writing to this group!
About outside research:
Suppose the boss told me to write a presentation for the budget makers,
laying out the 'lease or buy' option for a fleet of corporate jets.
I would go to the Business library to look for published analysis of
costs, cost benefits, non-monetary considerations, and the entire range
of appropriate considerations. I'd also look for references to limited
distribution subscription reports, and other data I could use.
The cost of acquiring such information and keeping it up to date makes
it less likely to be something every business keeps available, but when
they need it, nothing else will do, and research is indicated. I'd
probably allow that to be called outside research.
I haven't set foot in the business library since I became a technical
writer. What I've offered is my best understanding, but I may not have
covered everything relevant to the topic.
Discusrsively or not,
Ned Bedinger
doc -at- edwordsmith -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-