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.
Only thing I've seen work is formal testing of the design, but it's hard to drive that from the tech writer position. One might suggest that it costs at least two orders of magnitude less to solve a design deficiency at the design stage than at the beta stage. But it takes a lot of effort not to be ignored when trying to sell the idea that maybe $20,000 worth of testing is needed. After all, tech writing is merely a clerical function.
> I have since learned that "Yeah, sure" is Clientese for "actually, we
> only kind of leafed through it, so there's a few score minor bugs and
> at least two major functional deficiencies that you aren't gonna find
> out about until beta-testing starts, and these will force a redesign
> of substantial portions of the system."
>
> If anybody has a solution for that particular sticky wicket, I'd love
> to hear it. And "make 'em sign it in blood" has already been tried.
>
> --
> Huey
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-