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.
But did you then document those "custom" functions?
What you're talking about is a business decision not to support specific
functionality even though it's actually built into the product. What I'm
talking about are functions that are supported but not documented...
features that are fully functional and exposed to the users. To me, it's a
shabby business practice to incorporate features into a product with the
intention that some segment of the user community will use them and then not
provide documentation of those features.
Mike
--
Mike Starr WriteStarr Information Services
Technical Writer - Online Help Developer - Website developer
Graphic Designer - Desktop Publisher - MS Office Expert
Phone: (262) 694-1028 - Tollfree: (877) 892-1028 - Fax:(262) 697-6334
Email: mike -at- writestarr -dot- com - Web: http://www.writestarr.com
----- Original Message -----
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Saturday, August 18, 2007 1:36 AM
Subject: Re: Guess what: we suck!
>I don't consider that a problem at all, as long as *someone*
> is doing it. Perhaps it's the manager in me talking rather
> than the "technical communicator," but what information
> should be provided to the user is whatever information
> best supports the company's business plan for the product.
> In some cases, that might mean every possible feature
> and function, in others it might mean the 10 most
> commonly performed functions and nothing else.
>
> One of the most successful products I ever worked on
> could perform about 50 different functions. Marketing
> determined that 90% of our potential customers would
> be using about dozen of these functions, so we fully
> documented those and nothing else. Anyone who
> looked at the product and deduced that there were
> additional capabilites would call in to ask about them
> and be told that the undocumented functions were "not
> supported," then would be referred to Product Support
> for a quotation on a custom option. In the end we made
> as much on the customs as we did on the initial sales
> of the base product.
>
> Gene Kim-Eng
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-