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.
Can anyone provide me with any practical tips for how to do a "quick and
dirty" usability test that can help point out key problems with the
documentation.
Tony Markatos responds:
Your new to the organization (and I assume to the products domain), what
problems come to your mind?
Also, remember that the primary element of usability is effective
organization. Ideally, the product should be organized around end-user
tasks. Granted, you do not know the users yet, but as a "quick and dirty"
analysis, evaluate the extent to which you have to skip-around or jump-over
material to accomplish what seems to be a logical end-user task.
Tony Markatos
(tonymar -at- hotmail -dot- com)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
