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.
We're not all expert users/beta testers who can quickly
gauge the failure or success [in terms of usability] of software on first or
second or even third encounter.
Tony Markatos responds:
I'll go one step further: For complex software, unless the TW has a clear
understanding of the goals the end-user is trying to achieve with the
product and how all of those goals interrelate, he/she can play with the
software until the cows come home and never be able to judge the success or
failure of the software.
TWs rarely achieve this level of understanding; but hey, the same can be
said of the testers (and developers and systems analysts).