Re: Writer vs Author (was Techwriting after the boom)

Subject: Re: Writer vs Author (was Techwriting after the boom)
From: Gene Kim-Eng <gene -at- genek -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Sun, 08 Jun 2003 22:45:10 -0700


Actually, I think it would be more accurate to say that the consensus is "we want
writers who can produce documents about our products without taking up our
engineers' time." "Technical" for most company executives would be someone
who can come into the office and engineers' bedrooms at night, absorb product
knowledge from locked file cabinets, powered-down computers and sleeping
R&D personnel by a process akin to the Vulcan mind meld, then disappear for
a few weeks and return with completed documents ready to insert into product
packaging. Whether these writers are people with sufficient engineering, product
and technology skills to be able to take over for the developers except that they
just prefer to write or shaman priests sacrificing chickens to pagan gods in the
night they couldn't care less, as long as the prospective "communications
specialist" has an established track record of getting the job done with virtually
no contribution from them. Fortunately, if you can actually do something remotely
resembling the above, they're still willing to pay pretty good money despite the
current state of the economy.

As for the rest of your questions, they want docs that satisfy all legal and other
regulatory requirements for pushing product out the door, by their deadlines.
The rest they usually couldn't care less about.

Gene Kim-Eng



At 11:04 AM 6/9/2003 +1000, Michael West wrote:

> From the conversations I have
> with CIOs and other executives, the consensus is - we want tech writers
that
> are technical.

If this were true, I would be asking the following questions:

1. Define "technical".
2. How close is the CIO to the audience for whom
the publications are designed?
3. What are the users saying about the publications,
and how does the CIO know? Are there other
people in the organization who might have a different
perspective on what the end-users are asking for?
4. What analysis has been done to assess end-user
needs and skills?
5. What publication design strategies have been tried,
and how effective were they, and how does the CIO
know that?

But then, I'm a communications specialist.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Robohelp X3, from eHelp, lets you quickly and easily create professional Help systems for all your Windows and Web-based applications, including Net.

Buy RoboHelp Office X4 by June 13th and receive
$100 mail-in rebate, Plus FREE RoboHelp Plus Pack.

Order RoboHelp today: http://www.ehelp.com/techwr-l

---
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.



References:
Re: Writer vs Author (was Techwriting after the boom): From: Andrew Plato
Re: Writer vs Author (was Techwriting after the boom): From: Michael West

Previous by Author: Re: Techwriting after the boom
Next by Author: Re: templates [hellfire & brimstone]
Previous by Thread: Re: Writer vs Author (was Techwriting after the boom)
Next by Thread: Re: Writer vs Author (was Techwriting after the boom)


What this post helpful? Share it with friends and colleagues:


Sponsored Ads