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.
<coarse bluntness>
No matter how well organized the project, no matter how well identified the
tasks, if the writing is crappy, the documentation will suck.
</coarse bluntness>
-----------------------------
I could not agree more. You can spend all the time you'd like on end-user
task analysis, documentation organizing, estimating, and verification, but
if the doc is poorly written and hard to read, it doesn't mean a thing. The
users won't read it. Their productivity suffers (not to mention your costs
increase as tech support is inundated with calls). Planning/evaluating are
important - don't get me wrong - but certainly not *more* important. There's
no way around it - if you want the docs to matter, writing skills matter.
