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.
In a message dated 97-01-06 22:06:34 EST, Marlene J. Geary writes:
>>
Question - Is there anyone out there who issues "beta" documentation to
customers who are "beta-testing" software?
<<
I have a client that always tries to do at least a few beta releases with the
docs (online and printed). Since the documentation is typically written when
the software is nearing release, last-minute changes in the software are
often not included in the beta docs.
>>
1) Do you ever hear feedback on the beta docs from these beta customers?
<<
Some beta testers are pretty good. This client is pretty relaxed in its beta
testing, and leaves it to the testers to report whatever they want. There is
usually a list of general areas of the program that need testing, but not
strict controls. I don't know how many of the testers really pay attention to
the docs, much less go through them in an organized and thorough manner. One
or two have clearly worked at it and found some important things, but they
are the exception.
>>
Actually - do the people and companies that sub to this list get a lot of
feedback regarding the manuals produced by their respective departments?
<<
I often get little feedback even from the client, let alone the beta testers.
They pretty much leave the docs up to my discretion, without saying much
unless I ask for input on specific areas.
I did one project for another client with a disturbing habit of not reading
review drafts, and just OKing them. Two or three reviews later he'd see some
glaring issue and come all unglued, even though he'd already OK'd the text
more than once.
>>
Does anyone here survey their customers on the documentation they produce?
<<
I wish they would, but that's up to the client. Maybe I'll talk to them about
that.
Earl Morton
WorkgWords -at- aol -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
