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.
> From: Sharon Burton-Hardin [mailto:sharonburton -at- email -dot- msn -dot- com]
> But, as a consultant and a teacher of tech writing, there is the point of
> view that if it is really hard to write about, maybe it is badly designed.
> And if it is badly designed, then it will be hard for the user to use.
> Frequently, the writer is the place where it is first noticed
> that something is badly designed and I do think we have an obligation to
> point it out and offer to help where possible.
That pointing out and offering to help is an ongoing negotiation.
It seems to me that there is a rather significant product
differentiation between what you sell and what Andrew sells. His
service is more focused, yours more comprehensive. My guess is
that you both provide exactly what your clients want.
mike -dot- huber -at- software -dot- rockwell -dot- com
nax -at- execpc -dot- com