| | Storyboard
Mary is in charge of approving Phyllis's trip. In order to do so, she has a visual queue where she can go from one person to the next and figure out who needs to be approved and who doesn't need to be approved. | Visibility
The approval interface is very visible, because key information appears before Mary. The important information she needs to be able to see is how much budget she has left over to use and who's trip she is approving. By having the person's total travel dollar amount and to be able to check that value against her total available budget, visibility allows her to be able to make the accept or deny decision very quickly. | Learnability
The interface is very visible, because the arrows clearly show that by clicking on the arrows you can click to the next person. Arrows are symbols used in many other applications, including in web browsers, so the interface should be very easy for Mary or anyone to learn how to use. | Efficiency
The interface is very efficient if the user's only purpose is to approve or deny people based on a queue. The interface can become very cumbersome for an employee base that is too large. It would be difficult to use this interface if you were trying to find someone's specific trip to approve. | Errors
Errors can result if the user does not know how to enter in data. Clients can be added and removed, so if a faulty client is entered, it can also be removed. However, because anyone can change this interface, it is very possible that clients that don't actually exist will appear in the client listby clicking approve or deny too quickly. However, with an interface that clearly defines who's trip you are looking at, it would be very easy to fix. |
|
