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: Quality of source material from Development From:Michael Oboryshko <obie1121 -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 11 Dec 2001 13:08:18 -0800 (PST)
Andrew wrote:
> it should be mandatory for a technical writer to be an
> expert-level user/tester of the products/technologies
> he/she is documenting.
I'd insist on one tiny modification: it should be mandatory to
*become* an expert user/tester.
Managers who only recruit writers who are expert in technology
XYZ are skipping a whole lot of good writers, some of whom could
probably do a better job than the XYZ expert you actually hired.
Suppose you wanted to hire a biographer. Would you look for
someone who was already an expert on your life? Or would you
look for someone with a good track record developing biographies
of other people? My mom is an expert on my life, but she might
not be the best biographer. Also, there are things I'm not going
to tell her ;)
I'd hire the good biographer. Then I'd hand over every document
I had about my life. Then I'd introduce the biographer to
everybody I know. Then I'd give a long, long interview. Then I'd
make myself available for ad-hoc follow-up questions. At least,
that's what I'd do if I wanted an honest and accurate biography.
I'd understand the biographer was gathering info to become
expert on his subject. I wouldn't play head games with him,
trying to make him feel inadequate because he wasn't already an
expert.
A lot of tech writing time is (rightly) spent just figuring
stuff out, which is more formally known as "information
development." By "figuring stuff out" I mean
implementation-specific stuff. I don't mean wasting the client's
time learning basic technology.
So it doesn't matter whether developers give you documents or
not. If they do, great. It's more grist for the mill.
Regards,
Mike O.
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.