...
Tasks should be added/edited to focus on the usability of advanced features (distinction between note and issue, hash tags for search filtering). This may be easier in the computer prototype.
Round 1 Prototype Iteration
Browse messages (Left pane) | Read message (Top right pane)
| Create new message (Bottom right pane)
| Reply to message (Bottom right pane)
|
|---|
- Added “High priority” and/or “Alert desk captain” icons to quick view of messages.
| - Added “Edit” and “Delete” buttons. The “Delete” button does not permanently remove messages.
- Previously, we always showed “High priority” and “Alert desk captain” icons on each message, and highlighted them if they applied to the message. Changed it so they only appear when they have been selected.
| - Changed trashcan icon to a “Clear” button to make it more clear that clicking this clears all the fields in this panel.
- Removed “Close” icon, which had been an “X”.
- Changed “Minimize” icon from “-“ to double down carets.
- Changed panel heading from “New message from <Desk worker name>” to “Create New Message”.
- Created titles, tags, and skeleton messages for each template in the “Templates” drop-down menu.
- Increased font size of “Alert desk captain”, “High priority”, and “Note vs. Issues” choices.
- Added an example tag: #example, instead of showing just “#”.
- Changed “Title” to “Subject” to more closely follow Gmail analogy.
| - Filled in “Subject” line with “Re: Original Message Subject” as in Gmail. This field is editable.
|
Round 2 Observations
| Task 1: Read Messages | Task 2: Create New Message | Task 3: Search and Reply to a Message |
|---|
Critical Incidents | - Unsure where to find the unread messages at first
- Took 30 seconds of scanning the whole interface before found
- Thought there was only one unread message but there were two
- Assumed shading meant unread (though it indicates the currently selected message shown in the reading pane) and didn't seem to notice the bolding
| - Didn't see the "Alert Desk Captain" option immediately, but found after a little bit more searching
- Some users misinterpreted functionality of "alert desk captain" (sends DC an email as well as posting to message list; users thought only DC saw these messages)
- Some confusion about exactly where and to whom messages were sent
- After selecting the "Missing Package" template, didn't fill in any of the fields in the message body (description / recipient)
| - Took a while to find the "Reply" button
- Thought about using Create New Message to reply instead
- Before submitting the reply, weren't sure where the Reply would be visible afterwards
|
Usability Issues | Unread messages lack proper affordances.
Similar to Round 1, multiple users had trouble finding the unread messages and/or identifying which messages were unread. We thought this was a paper prototype issue before so we didn't change it, but now we know it is a serious issue to address, | Visibility of advanced features lacking.
No one overlooked the advanced features this time, but it took too long to find for some users.
Message Recipients Unclear:
To whom the messages are sent is not indicated anywhere in the interface, which confused some, though most assumed (correctly) that it would be sent to everyone.
Template
Since selecting a category filled in a template in the message body, one user assumed they didn't need to add anything to it. Needs to draw user's attention to it so they add relevant information. | Visibility of Reply
The Reply button needs more visibility, though not standing out could be a downfall of paper prototyping since we sketched everything in pencil. |
...