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:"If the docs are too good..." From:technical -at- theverbalist -dot- com To:techwr-l -at- lists -dot- raycomm -dot- com Date:Fri, 6 Feb 2004 14:27:14 -0700
Well, it's Friday and y'all are being too serious. Here's something to
have some fun with ...
So an SME I was talking to floated the ol' air biscuit that he "was told
by someone who'd been told that if the product docs were too good, that
clients wouldn't purchase the training." Any suggestions for snappy
come-backs to that one?
Having looked through the archives some, I'm coming up with the argument
that Training is intended to give the user an in-depth experience, which
can then be applied to the broader information available in the product
docs, so while training and documentation cover the same information, they
do so with different objectives and from different perspectives, and
therefore there's really no conflict of interest between good
documentation and good training. But that's long-winded; I'm hoping for
something nasty, brutish and short...