...
Our scenario covers the basic usage of the application, including creating classes and assignments using the web interface and completing an assignment using the mobile interface. The tasks presented to the our users arewere:
- Go add 6.813 to your schedule. The assignments are: PS1 on the 11th, PS2 on the 16th, and GR1 on the 26th. Make it public so others can use your feed.
- Your 6.005 TA told you that he created a feed for all of the 6.005 assignments. Find and add his feed.
- You finished PS1 for 6.813---go and mark it as completed.
- You You decide to add a personal assignment, "Reading: Learning Java," to 6.813. Go add it to your schedule for the 13th.
- Later, when away from your computer, you finish the Java reading. Go on your phone and mark it as completed.
Observations
Summarized Observations - Iteration 1
...
- Having new calendars appear as-they-need-them on the "new class page" confuses people (they have to pause and understand what it is)
- Assignments on the phone are too small – even with the large prototype, users are mis-touching
- While there are multiple ways of adding new assignments (clicking on a date square or on the class list on the right) users don't know this – they just have to guess
- Consistency among the interfaces is good – the second time users see the calendar view, they understand how to use it
- We don't have any method of notifying users when they make an error (such as missing a section on the new class form)
- People seem to read the error messages (this might change with a computer prototype)
- Lack of enter can be confusing on auto-updating fields – this needs to be a quick change
- We definitely need to be crossing out assignments (not removing them)
- On your calendar, make a distinction between public and private events (user suggested color, icons would also work)
- We need to be consistent with our wording (Find vs. Search vs. Create)
- While color is useful, some users had trouble finding which "PS1" assignment they were supposed to remove.
Summarized Observations - Iteration 2
...
- Even though the mobile metaphor is slightly different now, users don't have any trouble using it
- Adding plus buttons on every element that can add new assignments might clutter it a bit, but it really helps the users learn the interface
- Making users explicitly add further assignments on the creation page is fine and less confusing
- All calendars need to have dates on them
- Some confusion between "Name" referring to assignments instead of class. On the creation page, name should be closer to the text box it represents
- One of the slowest tasks has consistently been the selection of 6.005 from the search list. We should make sure that the font for title of the class is larger than the rest of the search result.
- Having both a "search" and "add a class" buttons seems to be fine. Maybe search could also search through all of your assignments.
- Finding the correct assignment to complete is much faster with the addition of class name.
- Some would really like to be able to add it to an external calendar. (useful feature, but might hurt the push capabilities that make this useful)
- Plus button next to class works really well, communicates it's action.
- One user tried to add an assignment without adding any classes first. They didn't have a good grasp of our model, and we might want to highlight or bring notice to the "Add class" button if this happens.
Raw Observations - Iteration 1
...
| User 1 | User 2 | User3 |
Task 1 | -no confusion between find and search | -no confusion between find and search | -added right away |
Task 2 | -clicked add to do the search. search needed? | -clicked on the right feed quickly | -pause at find that class, then hit add new class |
Task 3 | -clicked on the task to complete it right away | -clicked on the wrong class (6.005 instead of 6.813) | -properly clicked on ps1 to mark it as completed |
Task 4 | -slightly confused on how to add an assignment / task to a class | -clicked on the date that he wanted the assignment due | -quickly clicked on 6813 to add an assignment |
Task 5 | -basically do the same thing as task 4 | -clicked on the right thing | -clicked on assignment to mark it as complete |
Feedback | n/a | -wouldn't want the assignment to go away, wanted a checkmark / cross out | -pretty intuitive |
Raw Observations - Iteration 2
...
| User 3 | User 4 | User 5 |
Task 1 | -found add button quickly | -got right button instantly | -searching for add button |
Task 2 | -hit search button instead of add button | -went to add a new class to find the new feed | -isn't really sure how to find an existing feed |
Task 3 | -clicked on the assignment right away | -selected task appropriately | -clicks on the assignment |
Task 4 | -hesitated, then selected the plus button to add a new assignment | -clicked on the plus button next to the name of the class instead of the plus buttons on the date | -pause on figuring out how to add the assignment |
Task 5 | -selected the assignment | -little slow, color would be useful | -pausing before hitting anything |
Feedback | -asked if old assignments will be removed or crossed out | -plus button on the date instead of the class | -confusion between search and add a class |
...