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.
>There may be exaggerations of features, there
>may be promises of features that are only under development.
Are you describing technical writing or marketing writing here? My
own technical writing generally starts before the product actually exists;
when I only have a spec to work from. Some of the grand and glorious
features in the spec always get dropped in the end, or don't give the
My manuals typically descibe the product as it will be once it works
right -- which may not describe the first version shipped to customers,
which will go out under "waivers." Thus, I'm documenting our expectation
of the product.
The difference between technical writing and marketing writing is
really this: technical writing exists to allow the reader to use the
product; marketing writing exists to promote sales of the product.
The same document can do both (or neither).
And, of course, the perfect marketing document neither lies nor distorts,
but convinces you solely on the genuine merits of the product and the
uses the product can be put to.
Robert Plamondon * High-Tech Technical Writing
36475 Norton Creek Road * Blodgett * Oregon * 97326
robert -at- plamondon -dot- com * (503) 453-5841
"I regret that I have but one * for my country." -- Nathan Hale