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.
Hello All:
I was talking with a colleague of mine yesterday and lamenting the fact that we do not get much feedback from customers when we send our technical documentation out for field testing with the product. We joked that our documents were just that good, but I cannot believe that, completely. We have been sending the documentation for field test (along with a short survey that is incorporated into the product's field test survey) and have received more input than in the past (which was none)....But not nearly enough. :)
My question for discussion: Do you send out your technical documents for Beta testing to actual customers or field technicians in a structured field test? If so, do you have any tricks or tips to get good feedback.
Best regards
Megan Bruce
Robert Bosch LLC
Product Management-Aviation (ST-CO/MKP3.2)
12000 Portland Ave. S.
Burnsville MN 55337 USA
USA
www.Bosch.us<http://www.Bosch.us>
Tel. +1(952)736-3910
Megan -dot- Bruce -at- us -dot- bosch -dot- com<mailto:Megan -dot- Bruce -at- us -dot- bosch -dot- com>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
