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.
----- Original Message -----
From: "Ned Bedinger" <doc -at- edwordsmith -dot- com>
> What began as an insufficiently-specified writing
> task was treated as a design task (because it was not well specified),
> which some respondents developed into secretarial work and on into a
> tech writing task, primarily IMHO because it was sent to this list, but
> also because it needed more information ("research") and some writing,
> which was identified more or less as our process.
Produce a document ("letter") that relates technical information
to a customer and satisfies certain specific company and customer
requirements...sounded exactly like "our process" to me.
> I've studied law, and I've worked in tech writing for nearly twenty
> years, and if my understanding of the task was as thin and uncertain as
> Deborah's, I could end up looking like I sacrificed the client's
> interests to forward my own ambition. I hate it when I look like that,
> it is just so bad for business.
>
> I wonder if *anyone* refrained from designing a solution because they
> didn't have enough info? No? I thought not. We are good designers.
With due modesty, I would say yes, "someone" did. Deborah
said "I've been asked to write a letter" and then asked what
others suggested to satisfy a short list of goals. Some of us
just answered her question as best we could, with the
presumption that she would take all our suggestions (not
solutions), sit down with her client and together devise a
plan that suited their needs.
If I ever thought for one moment that anyone in this forum
would take one of my suggestions and blindly implement it
as a one-size-fits-all "solution," I'd be loathe to express
my opinion on anything. Remember that, and the next time
you want to shut me up just tell me you're waiting with baited
breath to go back to the office and do whatever I suggest.
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-