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.
>Look at Tech Writer projects. The ones that I have seen fail failed
because
>of poor end-user analysis and estimating. Yet, if you were to look at
>hundreds of on-line TW job listings (try www.dice.com) you will find that
>few ask for skills in either of these areas.
I've never seen a tech writing project fail for these reasons.
I've only seen them fail because information was missing or completely
inaccurate.
The user simply could not figure out how to use a particular tool, and the
documentation either did
not explain the procedures at all, or (worse) gave the wrong information.
Even if the information is hard to find, or could be presented better, as
long as it's there and its correct
your project doesn't fail.
