Page History

Storyboard
In this part of the story, Phyllis needs to plan a new trip.  In  She first logs in so that she can see her current screen, which shows all the trips she has ever planned.  She clicks in order to create a new trip, the trip she is planning on creating.  
In order to plan her new trip, she logs in and can drag and drop new clients into a calendar with preconfigured dates.  She clicks the Auto button so that her trip is automatically planned for her.  After she adjusts her automatically planned trip, she submits the trip to Mary who is slated to approve her trip expenses.

Visibility 
Visibility of this storyboard is very high.  It uses symbolism from Google calendar, and has a lot of the same features that people are used to seeing.  Programs such as Outlook and Google calendar all work this way where you can input new events and drag the event to the length you want the event to go for.

Learnability 
This interface is very learnable, because even after using the Auto function, the interface is still very modifiable.  Also, once you click the map, you can see another representation of the information entered in by the user.

Efficiency 
The efficiency of this interface is not as efficient as it could be.  Often it could be easier to enter in events without having to drag and drop and enter in events manually.

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 list.

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 approveddoesn't need to be approved.
She needs to do a quick check that the trip is valid and does not violate any company policies.  Doing a quick glance over the schedule of each person is enough to do this effectively.  Mary has a lot of other things to do, so she does not have time to closely analyze each person's trip.

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 by 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.

Storyboard
Juan is in charge of analytics.  The interface here allows him to visualize the data such that all financial data from the company can be analyzed.  This program will allow Juan to figure out which departments are spending the most money and look for irregularities.  This interface is closely modeled after mint.com.  Mint.com works very well as a web interface for analyzing financial data, which is what this part of the tool seeks to accomplish.
Juan is always looking to see if any particular traveler is over spending and where he is traveling to when he overspends.  During this stage, our tool will allow him to do that.  He can click on specific points on the graph in order to zoom into what piece of data he is looking to find.

Visibility 
This interface is very effective visibility wise.  Graphs can be easily configured to view data that Juan wants to see.  Juan wants to see which departments to contact that have been spending too much money on travel and the trends different departments are having with spending.  The tabs on the left allow Juan to easily customize which graphs he wants to see.

Learnability 
The interface is very easy to learn.  The graphs are clearly labeled, and the affordance of the date bar at the top of the page shows that it controls how many months of data to display on the graphs.

Efficiency 
The interface could be made to be more efficient.  Often times, people want to see the raw data and make calculations themselves.  In this interface, users are forced to create graphs and are unable to extract raw data.

Errors 
Errors can be made if the wrong tab is clicked.  What could happen is that a wrong department could be clicked on, and then the wrong graph would be displaying.  However, using this program, errors are prevented because graphs are clearly labeled and can be easily modified to a graph that the user intended on creating.