In this weeks reading the author discussed many different types of editing techniques and highlighted the importance of each. The point made about computers making it very easy to forget to revise is something that I also believe happens a lot. The reading went on to discuss the different types of usability tests. There were several different tests mentioned and some were similar to others but each had their own specific target. For my Instructions Project the usability test that I believe will be most effective in telling me what I need to revise is the summary test. For my project I have chose to create a set of instructions for the track and field event of High Jumping. The target audience is high school aged athletes to advanced athletes that are refining their technique. The summary test requires the reader to give a short summary of what they feel was important from the document. By analyzing the responses it will give me an idea of what their vision of the technique is and if it matches mine. By having them right down what they believe the three key points are will relay to me if they grasping the concept. A summary test is a good understandability test for my circumstance.
Outside of the class another good way to test my project for usability will be to do some simple document cycling. A simple email containing an attached copy of the set of instructions will be quick and efficient. By passing it around to different coaches and teammates I will get some good input of sections that I should highlight more or areas that I have overlooked. Their suggestions will be most helpful to create a very thorough set of instructions for athletes. It will also insure that they will be a correct set of instructions and will maximize their potential for success.
Perspective
I like how you are approaching the usability testing, ck86. What you ultimately want is for the instruction set to allow the user to effectively approach and execute the high jump. What that very much seems to require is that the athlete see the high jump as you, the expert, do. By having the user write-up what they feel was important will, as you say, give you a good idea of whether you have effectively conveyed what it is important. Oftentimes, what the author feels is important is not what the reader reads as such. As teachers who have written instructor blogs, created handouts, and composed assignment prompts, Jeremy and I can attest to this fact.
Combining Tests
You’ve provided some good examples of how you will apply the summary test in obtaining end-user usability feedback. I’ve noticed a number of other individuals have referenced this test as well, but I feel yours is the most effective use thus far. The most common test amongst this class appears to be the document markup. Although I’ve seen it used in situations that it likely would not prove effective, I think yours would be very suiting. For example, since you are targeting high school student jumpers in Track and Field, I think you might consider providing each member of the team(s) a copy of your instructions and ask them to perform a document markup test. After you clarify what the test entails, the students will be able to annotate your instructions, in real time, and specifically denote where they encounter obstacles, get lost, or have difficulty proceeding. Knowing each of these issues will enable you to resolve preexisting “gaps” in your instructions and anticipate others based on the feedback provided.
Summary Test ¿=? Reading Response Prompt
I'm in agreement with the above reply...it is my thinking that the summary sort of test can often be used as an easy-out because it is simple to set up: "Summarize how you feel about this document". However, the summary test, if responded too completely or at least even half-heartedly, should offer the richest amount of information when compared to the other types of tests. The key, as you have implied here, is to process the responses in such a way that that you gain an understanding of their understanding. It is somewhat analogous to the reading response assignments-you could even formulate your summary test in this way. "Read this and comment on something specific/something that you could use in the future"