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.
On 1/12/06, Tracy Taylor <ipsque -at- yahoo -dot- com> wrote:
> We are lucky in that we get some feedback on our
> documentation from customers, but I'm not always sure
> how to address the feedback.
> For example, we get feedback that we need "complete
> documentation." In your mind, what does that mean?
In my mind, that means I need to ask the customers what *they* mean -
what's missing, in *their* minds? What do they need that they're not
getting? Why are *they* characterizing the documentation as
One of the best things you can do as a writer, if you can swing it, is
to talk to representative members of your audience regularly and find
out how you're doing meeting their needs. Receiving feedback gives
you a golden opportunity to not only get clarification about what
their specific comments mean, but probe more deeply into what they
need and how they're using your docs.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l