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 my case, I work with usability specialists. I develop scenarios and I'm
one of the people behind the one-way mirror. I don't run the tests, for the
reasons Carol gives.
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
> -----Original Message-----
> From: Carol Gasser [SMTP:carol_gasser_at_usinin31 -at- boehringer-mannheim -dot- com]
>
> The recent discussion about proving to managers/programmers that better
> documentation is necessary has included several suggestions that
> technical writers perform usability tests, which makes me more than a
> little nervous.
>
...
> Is this the kind of thing that is being referred to on the list, or are
> technical writers out there being asked to perform actual usability
> tests? It really seems like a leap out of the tech writer job
> description.
>
