Dashboard > Fluid > ... > Inline Edit User Testing - Round 1 > Inline Edit User Testing - Round 1 Protocol
Inline Edit User Testing - Round 1 Protocol
Added by Gary Thompson, last edited by Daphne Ogle on Oct 15, 2008  (view change)
Labels: 


Reference:  User Testing Protocol

Supporting Materials:

Greeting script

User Testing Greeting Script
Hi [user's name]. I'm [your name] with the Fluid Project. The Fluid Project is an open, collaborative project to improve the user experience of community source software. Today we are looking for ways to improve the user experience of a Fluid component. This is a test of the component; we are not testing you. If you find something difficult to use, chances are that others will as well. This test of the component is simply a means of evaluating the component's design and to discover any issues we need to address.

If you feel uncomfortable you can stop at any time during the study.

Please speak all your thoughts aloud as you go through the tasks. This helps us better understand why you are making certain choices. The study will take about XX minutes. We will answer any questions you have at the end of the study.

Do you have any questions?

First we'll need you to sign this Consent Form.

Let's get started!

Scenarios

Student

You are a Teaching Assistant for Astronomy 7A. Your instructor has asked you to review the Sections in the Section Info Tool to make sure they are correct.  The course consists of one lecture section which all the students attend, and 3 discussion sections. Each student in the class attends only one of the discussion sections. All the lecture and discussion sections have their own entry in the bSpace Learning Management System. At the request of the instructor, you are reviewing the information on all the sections of the course in bSpace in preparation for the beginning of the semester.

Task

1) You realize there is an extra discussion section listed for your course for Graduate Student Instructor Ray Davis. It's also in the wrong room, Lecture Hall B, and you decide to delete it.

2) As you are reviewing the titles of your sections, you notice that all the sections are labeled with "LEC," which indicates that they lecture sections. You know the last three sections should actually be labeled with "DISC" for discussion sections, so you decide to fix them.

3) Next, looking at the section titles you believe that the title for the lecture section should contain an "L" for lecture instead of a "P" (as you're not sure what that's for), so you decide to change it.

4) You realize the numbering is off in the discussion sections now. Change Ray Davis' discussion section to have "104" in the title instead of "105."

5) After thinking about the "L" you added previously to the lecture section title, you're not absolutely sure it's right and are afraid you may be changing something you shouldn't, so you decide to change the lecture section title back to what it was before.

6) When you see the "P" back in the lecture section title, you are positive it's wrong, and decide to put the "L" back again.

Instructor

You are an instructor for Astronomy 7A. Your course consists of one lecture section which all the students attend, and 3 discussion sections. Each student in the class attends only one of the discussion sections. All the lecture and discussion sections have their own entry in the bSpace Learning Management System. You are reviewing the information on all your sections in bSpace in preparation for the beginning of the semester.

Task

1) You realize there is an extra discussion section listed for your course for Graduate Student Instructor Ray Davis. It's also in the wrong room, Lecture Hall B, and you decide to delete it.

2) As you are reviewing the titles of your sections, you notice that all the sections are labeled with "LEC," which indicates that they lecture sections. You know the last three sections should actually be labeled with "DISC" for discussion sections, so you decide to fix them.

3) Next, looking at the section titles you believe that the title for the lecture section should contain an "L" for lecture instead of a "P" (as you're not sure what that's for), so you decide to change it.

4) You realize the numbering is off in the discussion sections now. Change Ray Davis' discussion section to have "104" in the title instead of "105."

5) After thinking about the "L" you added previously to the lecture section title, you're not absolutely sure it's right and are afraid you may be changing something you shouldn't, so you decide to change the lecture section title back to what it was before.

6) When you see the "P" back in the lecture section title, you are positive it's wrong, and decide to put the "L" back again.

Notes for Test Coordinator

Offering help during the test

Try not to offer help too soon. Let the user attempt to move the box a few times. If they ask for help reply with:

  • "What do you think you/that would do?"

You want to observe whether the user has trouble:

  • recognizing they can edit inline
  • successfully editing text
  • discovering how to "save and exit" inline edit
  • recognizing that an edit was successfully made
  • using, or even notices, the "undo" link
  • using, or even notices, the "redo" link

Post-test Questionnaire (have the user fill this out themselves)

Simple Text Inline Edit Post Questionnaire.doc 

Post-test questions (ask these verbally after the user has filled out the questionnaire)

  1. Did you see anything that told you you could edit the text directly on this page? How helpful was it to you?
  2. Did you expect that clicking the highlighted area would allow you to edit the text directly on this page? If not, what did you expect?
  3. Did you notice any indication that your edit was successful?
  4. Did you think there was a way to "undo" your edit? Did you think there was a way to "redo" an edit that you'd undone?
  5. Did you notice an "undo" or "redo" link?
  6. Did you enjoy using inline edit? Is there anything you would improve?

Site running on a free Atlassian Confluence Open Source Project License granted to The FLUID Project. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5 Build:#805 Apr 26, 2007) - Bug/feature request - Contact Administrators