Paper Prototype Design
Photos
Briefing
Tasks
Index Card |
Description |
|---|---|
|
This was our first task. There are two index cards because we updated the task part-way through our paper prototyping. This task is meant to prompt the user to explore our reading interface so we can see how easy/intuitive it is to read information. |
|
This was (sometimes) our second task. This is a form of organizing/saving information (our third high-level task in GR1) that we wanted to test. We learned later on in our paper prototype testing that the behavior of this feature confused some users. It is not consistent with how users prepare items for reading later in emails/twitter/etc, and it was unclear what was supposed to happen when the users hit the "read later" button (does the item go away? etc.). |
|
This was our second/third task. It is also a form of organizing/saving information like the previous task. Our paper prototyping users told us that the tag menu/general functionality was more straightforward than the "read later" functionality. |
|
This was our last task, testing our implementation of the filter task (second high-level task from GR1). It was our most complex task, and was changed the most in our iterations for our paper prototype. |
Analysis
Observations
User |
Tom's Notes |
Rahul's Notes |
Leilani's Notes |
|---|---|---|---|
User 1 |
|
|
- user wants email marked unread when hit “read later”
* user wanted to scroll early in the test - “silly link” != “silly pics”, need to fix task index card (but scrolled in the task list to find it, is this intuitive?)
* need to show somehow that items are tagged - filter - toggle or include** user tried looking for “href” in search bar** user wants to see results before saving filter
- user wants to rename filter to “links” (how would a user do this?)
** we forgot to print out sharing material for paper prototype - we forgot the add “shrink” button option for when users are reading stuff
** user thought reset button resets filter options only (resets the form, not the filter) - user wants views and easy access to the original state of the feed
** user wants an “x” button to kill the filter (to get to original state) - user wants a preview button
** user thought saved filters section = advanced section in filter menu (paper prototype issue only?) |User 2
User 3
I was the computer for this test
User 4
User 5
User 6
- user wants to rename filter to “links” (how would a user do this?)