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.
This doesn't quite answer your question, because we don't really do much beta testing of documents here, but it does address the broader topic of how to get feedback from the field.
I have set up a "Technical Documentation" email address and listed it in all of our technical manuals. It is designed to be used for unstructured feedback (reporting of errors, omissions, and any suggestions). That seems to work pretty well in terms of getting some feedback. Customers don't use it much, but our internal field service engineers and system installers do.
I don't think people use paper and the mail for this kind of thing anymore. You might be more successful if you could get the names/phone numbers of the beta test customers, call them, and complete the survey over the phone. That way, they do not need to take the initiative or make much of an effort.
Susan Jelus
Senior Technical Writer
Thermo Fisher Scientific
Logan, Utah
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
