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 thread raises an interesting line of thought. I'm sure
there are lots of us who are asked to do, or volunteer to
do, the odd bit of QA and/or Usability testing. Particularly
at smaller outfits, where authors are asked to do all sorts
of supplementary things.
We wouldn't doing our job as software authors if we
weren't providing feedback on areas of the application
that aren't functioning as expected or are functional but
clunky...>>
I find it's also possible to offer thoughts on usability if, as a
tech writer/user advocate, I am able to participate early in the product
development process, i.e., during requirements definition. At that point,
if I hear something being discussed that, based on my experience, seems
cumbersome to a user, I can raise the issue while the product is still
on the drawing board. It's much easier to change things sooner than later.
Of course, we're not always allowed in on things early enough, and that's
too bad.
--B
barb -dot- ostapina -at- metromail -dot- com
