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.
Hutchings, Christa [cwhutchings -at- HOMEWIRELESS -dot- COM] wrote:
>Basically, Marketing thinks we should include a component checklist,
but
>Product Management thinks it's not needed <snip>
I guess the question is, why does Marketing think it's necessary to
include a checklist. The Product Management group has presented several
good reasons for not including it, but the only thing I hear in favor of
it in your post is a sort of vague "everyone else does it." If this is
the argument, not everyone includes a checklist (we don't).
From your return address, I'm making the assumption that your market is
the home consumer. Of the products, software, etc that I've purchased
for home use in the recent past, the only thing that included a
component checklist _and need to_ was the gas grill I bought. If there
is a series of assembly instructions with your product, maybe a
checklist would be helpful. If the parts are large, not easily lost in
the packaging, and distinct, maybe a checklist is redundant. IOW, your
products and market define the need, not some nebulous "we should have".
-Matthew Craver,
Technical Documentation
Open Solutions Inc.
Mcraver -at- opensolutions -dot- com
