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.
I'd like to see the answers compared to "The product produced by your
company/department undergoes formal usability testing..."
My beef isn't that the documentation doesn't get the usability testing it
needs, but that the *product* itself doesn't get the testing. I don't know
that any of the companies I've worked with over the last three years know
that there is even such a concept as usability testing. Obviously, if your
product isn't tested, your documentation isn't tested, either. In my current
workplace, at least the company is letting me "act" as if I am a user and
make usability suggestions--they actually implement them, too. I would bet
that most of you are in the same position: as the documentation person, you
are the only "usability tester" the product sees before release.
PO Box 920, Kfar Saba 44109
rebecca -at- commercemind -dot- com
>> The documentation produced in your group undergoes formal
>> usability testing
>> * Always
>> * Frequently
>> * Occasionally
>> * Rarely
>> * Never
>> * Not applicable/None of the above
>I hope the responses to this poll are honest. So far, they
>show that we are a
>long way from where many of us say we want to be on usability
>course, you have to take things as you are able to, and in my
>place we're still
>teaching TW 101. Usability testing is somewhere in the 500s, I fear.