Here is a link to the briefing and tasks we used in our user tests.
Design
Screenshots
Important Design Decisions
- consistency - we tried to make every page as similar as possible so once a desk worker learns how to use the packages page, they know how to use all the pages
- simplicity/minimalist design - we eliminated unnecessary information and text (in tables and on buttons). Only pertinent information is displayed on each page.
- lots of whitespace
Design Alternatives
- more informative tables - we considered including a lot more information for each package or item like the desk worker that added it/checked it in, the time it was checked in, the last person who checked out an item, etc. But we chose simplicity and whitespace over overly informative tables
- sticky notes - we considered making the notes page contain more realistic sticky notes (like the sticky note feature on Windows), but decided against this idea in favor of the ability to sort and filter notes
- sticky notes - we considered allowing users to add sticky notes to any page on the site instead of having a separate notes page. However, we decided against this idea because it's simpler for users to only have to look in one place to see all the notes
Describe the final design of your interface. Illustrate with screenshots. Point out important design decisions and discuss the design alternatives that you considered. Particularly, discuss design decisions that were motivated by the three evaluations you did (paper prototyping, heuristic evaluation, and user testing).
Important Design Decisions
Design Alternatives
Implementation
Describe the internals of your implementation, but keep the discussion on a high level. Discuss important design decisions you made in the implementation. Also discuss how implementation problems may have affected the usability of your interface.
...