Versions Compared

Key

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

...

Ben comes to pickup his package a few hours later.  Alyssa hit "Package Pickup" under "Packages" on the left navigation bar.  She enter She enters Ben's name.  Once she hits search, it loads the next screen.  If she entered the name of someone who wasn't in the db, or someone who didn't have a package, a message  would flash telling her that that is the case.

...

This design was revised according to comments and feedback received in class.

The main feedback was that it may be confusing to know what exactly the onmi-bar will do and how to activate its features. E.g. typing "put a package for Ben in Bin A" would not be a valid input, but entering "Ben Bitdiddle" is. The exact wording for a better information scent is yet to be determined (perhaps a prompt in the text box or another word for "Go"), but multiple entry points to tasks have been added to reduce confusion.

Learnability: The design is learnable because all of the feature are consistent

Efficiency: This design is efficient, especially when dealing with a single student's entry. Every available action (add and remove guests, packages, and items) is present from one screen, making it easy to perform multiple actions at once. For example, when a student comes down to desk to return a movie she borrowed, pick up a package, and check in her friend as a guest, the worker must only enter her name once into the omni-bar and then can perform all these actions without any further navigation.

Learnability: The design is learnable because all of the actions can be found on the left.  It's also learnable because there are common affordances (querying information by names, text fields with hints in them), and the buttons have meaningful text, indicating the action that would occur.

Efficiency: The design is efficient because it allows for multiple package registration.  It's also fast because the actions are consistently on the left.

Safety: Because of auto complete, you'll know if a name isn't in the db.  There is a chance of registering a package for someone who doesn't have a package (for instance, if you enter the wrong Ben).  You can easily undo this by picking up the package.  There are definitely faster ways to take care of that scenario.  Because of the step involved in checking out a package (searching for some one by name, and seeing their name on the Pickup package page) it'd be hard to pickup a package for the wrong person.Safety: