Below is a list of requirements for testing the sidebar design.

Usability questions

1. Do users get the faceted structure of the sidebar?
2. Do users need to have the icon and the name change for the all collection?
3. Would users rather have colletions grey out or disappear when they click between app areas?

Feature requirements

• Visual divider between
• Remove all non-appbar buttons from the toolbar
• Turn off and remove checkbox functionality for now
• Visual divider or space between OOTB collections and user-defined collections

Design 1

• Toolbar All | Mail Tasks Calendar
• Sidebar
  • Library
  • In
  • Out
  • Trash

• Name of Library collection doesn't change between different app areas
• Collection items grey out between different app areas
• Selection DO persist across app areas

Design 2

• Toolbar All | Mail Tasks Calendar
• Sidebar
  • My items / mail / tasks / calendar
  • In
  • Out
  • Trash

• Icon for the "My" collection changes as the user
• Name of "All" collection changes between different app areas
• Collection items grey out in different app areas
• Selections do NOT persist across app areas

Design 3

• Toolbar All | Mail Tasks Events
• Sidebar
  • All my items / mail / tasks / events
  • In
  • Out
  • Trash

• Icon for the "All" collection changes between different app areas
• Name of "All" collection changes between different app areas
• Collection items disappear in different app areas
• Selections do NOT persist across app areas

Test plan structure

• Ask user to create 10 new items, making sure that they cover a wide range of kinds and kind-combinations and encompass both In and Outbound email. [This will most likely be done with a paper prototype.]
• Ask user to create 3-5 user-defined collections
• Ask user to file some of their items in these user-defined collections
• Ask the user to retrieve a number of items using the faceted sidebar