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[2]: Cost of Documentation From:Joyce Flaherty <flahertj -at- SMTPGW -dot- LIEBERT -dot- COM> Date:Wed, 22 May 1996 04:53:52 EST
Robert Plamondon (robert -at- PLAMONDON -dot- COM) wrote in response
to Michael Maloney RE ROI:
RP: <snip, good description of experiment on tracking lost sales,
support phone calls, and renewed support contracts>
RP: On a more immediate scale, you can do testing in a controlled
environment. When I was at Weitek, we did installation testing of our SPARC
upgrade processor. We just gave people the packaged upgrade product (with
documentation) and told them to install it while we watched. We changed
both the documentation and the installation tools on the basis of
these tests. <snip, observations>
JF: Usability testing and ROI are related, but strictly speaking,
not the same animal. A solid product will sell. Do you select
a VCR based on the quality of the doc? or do you select a VCR
based on the manufacturer? Careful, you might have to go VCRless.
If I selected a lawn mower based on the quality of the doc, my
wonderful Lawn-Boy would be sitting in someone else's garage.
JF: I might moan and groan and complain about documentation, but
poor doc does not influence my purchasing decision--hardware or
software.
JF: OTOH, ROI is most assuredly measurable in securing govt
contracts, which is a type of sale, and ROI is measurable in
support calls as well.
JF: Having refuted my own arguments, I support usability testing
whether or not I prepare the ROI. It's a necessary part of the
total process.
joyce flaherty
flahertj -at- liebert -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
