Versions Compared

Key

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

...

User

Create a Trip

Approve a Trip

Analyze trips

User 1

  • Pressed "add" before entering address
  • Typed in address of Microsoft, rather than using "saved locations" bar
  • Very confused about what to do in general
  • No idea what to do about time
  • Pressed "save trip" after entering every leg
  • Unclear about what "underlined things" are (i.e. name of trip)
  • Noted consistency problem between "approve" and "accept" in the two different panels
  • Derided "add trendline" feature as unnecessary
  • Confusion about current state/mode ("am I in department, year, overview??")
  • Confusion about what can be clicked and what can't be ("sometimes its the graph, sometimes its the buttons?"). Tended to click on buttons only
  • To access individual department, clicks on the name in the legend, rather than the piece of the pie.
  • Quotes of note: "Where am I?" "What am I doing?" "Is everything clickable?" "Stack is not clear!" "How do I get back?"

User 2

  • Confused about how to use "end date"
  • Confused about how to use address bar versus saved locations
  • Didn't know the map of the trip was below the scroll
  • Pressed "save trip" after entering every leg
  • Thought "balance" was how much the checked trips added up to.
  • Confusion around "accept" and "approve" just like first user
  • Delight: "Oh, the total changes!" (after they approve Phyllis' trip)
  • Doubt: "I'm assuming the math is good"

(Note: didn't have much time for this one as it occurred towards the end of class)

  • Expressed mode/state confusion
  • Clicked only on buttons

User 3

  • Goes to the address first (doesn't used saved location at all)
    • Suggested putting the most common clients on a map with a tag that says "add me" rather than use the text box interface.
  • 3 buttons at the bottom was confusing to them
  • Was looking for more detail on the trip to New Jersey (what hotel did she stay in for example)
  • Was looking for other expenses besides mileage
  • Pointed out that trip was not consistent (one leg ended in New Jersey, the next leg started in New York - where did she go in between?) - note: trip consistency may need to be enforced in the back-end??
  • Clicks on "department" to navigate to department, rather than clicking on graph.
    • Upon click, expected to see a list of departments, rather than a pie chart of the distribution
  • Didn't know how to get down to the employee level - there was no button on the side
  • Would like to see how much each approver approved
  • Would like to see buttons with pictures of the graph type (trend line and pie chart), rather than a drop down
  • Registered surprise that some people didn't have the analyze tab, but acknowledged that it might make sense in the context of a business.

...

Create a Trip

Approve a Trip

Analyze Trips

  • Changed web-form input required from user to be just three boxes: "address", "arrival time" and "date". These boxes are now aligned horizontally all on the same line at the top of the tab
  • Only allow user to click on "add" when they have filled in all three boxes
  • Changed "Added Locations" label to "Added Destinations" label (functionality remains the same)
  • Shrunk map and calendar so that they are next to each other with the intent to keep everything on the same screen (without scrolling)
  • Eliminated "cancel" button (now just "save trip" and "submit trip"

On overview view:

  • Consolidated ")Your Budget" and "Your Balance" to just "Remaining Budget" (still updated dynamically)
  • Added labels to columns: "Name", "Departure Date" , "Trip Name" and "Cost"
  • Changed label of button to "approve selected" from "accept selected"
    On detailed view:
  • Changed label from "Details" to "Mileage Detail"
  • Added mileage to information in addition to costNote: both changes in detailed view meant to emphasize to the user that this is a mileage tool module only - how this works within the overall reimbursement system is beyond the scope of this project for now.

TBD