...
Scenario Tasks
Observations
Wednesday:
User #1
We gave our first test user task #1 - to create a card. He tried to create an account from the home page (fig. 1) before creating a card but changed his mind halfway through and went back to the homepage to create a new card for Jeanette. He had trouble figuring out the “Name” field for the recipient form (fig. 3). After much hesitation, he typed in his own name instead of Jeanette’s name. Then, when it came to emailing the edit-card-link to friends (fig. 5), he was surprised that the “email” link opened up his mail client instead of his gmail. Immediately afterwards, he realized that he had typed Jeanette’s name as “Jeanete” and looked everywhere for an admin page to correct the mistake (There wasn’t an admin’s page).
User #2
We gave our second test user task #3 and #4. He entered his message and changed the styles correctly, but complained about not being able to see a preview/thumbnail of the picture he uploaded (fig. 3) because he suspected the picture wouldn’t look as good in the card anymore as an attachment. Once he hit the edit card page (fig. 6), our second test user tried to find who else had joined and written in the card, a collaborator’s list, but couldn’t find one (there wasn’t one). Once finished task #4 of editing, he clicked “send” by accident instead of “save” and sent the half-finished card out.
User #3
Finally, we gave our third test user task #2 of signing the card. He clicked on the invite link correctly and started typing his message. However, once halfway done with his message, he hit “save” instead of “write” and didn’t know how to view his message again once he clicked on another person’s name. He also complained about not being able to see a list of other people signing the same card. Towards the end, when it came time to create an account (fig. 8) so he can sign back in to finish his half-finished message, he gave up out of frustration and closed the whole page. He complained that he had to create an user account just so he can type in two sentences for birthday card. He preferred to have just called up Jeanette and wished her happy birthday over the phone.
Friday:
User #1
Our first test user was confused about the save and send button, and wasn’t sure what they did so he hit the save button instead of the write button. (Fig. 13) He wasn’t sure whether the message was automatically saved. We also noticed we should have some sort of error checking before the user is done writing the message into the card and clicking the send button. The Birthday only needs to have a month and day, no year required. (Fig. 11) And Finally, we noticed the order in which we presented the link that the user could use to send to his friends came too early on in the creation process. (Fig. 16)This caused the user to forget about the link when he was done writing his message of the card.
Some of the other minor observations that we noticed was that on the homepage, the user was not sure what the admin link did. (Fig. 13) It also wasn’t obvious how the user would be able to edit a message. And finally we realized we needed to change the name of ‘edit link’ because it didn’t convey the idea to the user of what he or she could use.
User #2
User #2 clicked on save button as opposed to write when he wasn’t to save the work that he had. (Fig. 14) We noticed the buttons were very confusing for our user, which could be caused by the fact that there were too many buttons on the UI. We felt this user did not have an intuition of what was going on during the card creation process. He also felt unsure about the collaborator’s list and why it existed. (Fig. 15) There was also no scroll bar on this list for the user to check on other users. Like the first user, this user was also confused about the link for friends and the admin link. And finally he had trouble figuring out how to edit messages.
User #3
The third user seemed to get everything that we wanted to happen and understood what was going on from the start of the card creation to the end of sending it out to friends.