The teams usability test for integrating google maps into a personal web page looks great. I like how there is an introductoryt paragraph that explains what is going on. There were a couple things that you could change. One is the test is a little long. If people see a long test they tend to shy away from it. Also some of your questions are just yes or no. I would maybe ask the user to expalin why they said yes or no. The purpose of the test is gahther as much info as possbile to make the instructions that much better.
Your usability test looks excellent. You start out with a
good intro to instruct the reader what to do to perform the test as well as
some background information. The one part I have some suggestions on is the
layout. I think question or item numbers go a long way to helping people keep
track of where they are in the document. Also, I am not sure if you are
expecting people to fill this out by hand and return it, but if not, I think
the lines could go. If you intend to keep the response lines, the last two are
not as long as the others (minor formatting). Great work.
Your usability report looks great, with a very strong intro and instructions on what to do for filling it out. You also have a lot of questions, all of which seem relative, but I would shorten it down a bit. Your client may not want to spend the time to fill out a lengthy "test." So I would pick maybe the 10 most important questions that would be beneficial feedback for your group and go with that. I did like how you split up the sections using the bold font. Lastly, I would get rid of the lines below each question. It makes the report look tacky and may not provide sufficient space for the client to answer your questions. Otherwise, good job on the usability report.
Usabilty Comment 4-21
The teams usability test for integrating google maps into a personal web page looks great. I like how there is an introductoryt paragraph that explains what is going on. There were a couple things that you could change. One is the test is a little long. If people see a long test they tend to shy away from it. Also some of your questions are just yes or no. I would maybe ask the user to expalin why they said yes or no. The purpose of the test is gahther as much info as possbile to make the instructions that much better.
16-PR: Peer Review
Your usability test looks excellent. You start out with a good intro to instruct the reader what to do to perform the test as well as some background information. The one part I have some suggestions on is the layout. I think question or item numbers go a long way to helping people keep track of where they are in the document. Also, I am not sure if you are expecting people to fill this out by hand and return it, but if not, I think the lines could go. If you intend to keep the response lines, the last two are not as long as the others (minor formatting). Great work.
Usability Report Peer Review
Your usability report looks great, with a very strong intro and instructions on what to do for filling it out. You also have a lot of questions, all of which seem relative, but I would shorten it down a bit. Your client may not want to spend the time to fill out a lengthy "test." So I would pick maybe the 10 most important questions that would be beneficial feedback for your group and go with that. I did like how you split up the sections using the bold font. Lastly, I would get rid of the lines below each question. It makes the report look tacky and may not provide sufficient space for the client to answer your questions. Otherwise, good job on the usability report.