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.
Subject:Re: testing the documentation From:"Bill Sullivan" <bsullivan -at- powerware -dot- com> To:kim_portonova -at- hotmail -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 16 Feb 2000 16:55:49 -0500
Kim Forbes is going to do a documentation usability test with future users of the application she is documenting, and asks for pointers.
On Thursday, Friday or Monday, take one of your subjects (2 or 3 if your group is large), swear the person to secrecy, and do a dry run. You will learn a lot, not only about how the process works but also about your strengths and weaknesses as a tester.
You might pay particular attention to the tasks you have listed, and how long it takes your subject to complete them, and how well she holds up (stays focused, remains into the testing, etc.), especially if she is a novice user of the program and perhaps not too adrenolin-charged or sure of herself.
