Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Storyboard 3 - Streamlined Preview

After Jane logs in, this is the main view. She quickly sees all of the log messages she hasn’t read yet in the “Unread” section at the top of the left pane. As she scrolls through messages with the up/down arrows, the selected message appears in the viewing area on the top right; once she reads a message, she marks it as read by pressing “Enter”, and it pops down to the bottom section that contains all of the log messages.


To write a new entry about the lost package, she just goes to the bottom right corner and starts typing. The date, time, and her name are filled in automatically, and a low default priority (indicated by the stars) is set for the message. She presses “Submit” and her log entry now appears in the left pane for all desk workers to see.

When Ben logs in, he reads his unread log messages and remembers he has seen an oddly placed package somewhere behind desk. He finishes reading all the new logs before looking for the package.


After finding the misplaced package, Ben uses the search bar to quickly find the log about the missing package. He then clicks “Reply”, and the “Create New Message” box is renamed “Reply to ‘Missing Package’”. He types up a response in the text box and presses Submit. His response now appears under the original entry.

...

Updates

...

To make this design more specific to desk workers' information and needs, we have added the below features.

  • Stronger classification of messages: 1) a message can either be an 'issue' (meaning that it is something that needs to be resolved) or a 'note' (meaning there is nothing to be resolved); 2) a message may fall into any of the following categories: lost/found (lost phone), desk supplies (ran out of red paper), repairs (elevator broken), requests (many residents requesting fans during spring), miscellaneous. 
  •  
Safety

To determine which messages the desk worker has read, instead of just basing it on whether they scrolled over it, we will instead mark it as read when the user presses "Enter" while the focus is on that log title in the left pane. This way, if a user accidentally over-scrolls, they don't lose track of the skipped messages. We anticipated potential issues if desk worker makes a typo in the log entry, or if she accidentally created an extra log entry. To handle this, we allow users to edit and delete only their own messages, so as to prevent malicious editing of other people's messages.

...