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.
Subject:Re: complete documentation From:Stuart Burnfield <sburnf -at- au1 -dot- ibm -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 13 Jan 2006 14:22:41 +0800
Barry Campbell <barry -dot- campbell -at- gmail -dot- com> said:
> ... 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 incomplete?
To put it another way, imagine your product is a 1000-piece jigsaw and some
customers are saying it's not complete. Does this mean they really want a
1500-piece jigsaw? Or that all the pieces are there but the picture isn't
quite the same as the picture on the box? Or are a few of the pieces
In my TW experience it's usually the missing pieces, but management usually
assumes the customer wants a bigger jigsaw.
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