GR1 - User & Task Analysis

User Analysis

User 1: Physics graduate student "Martha"

• Age/Gender: 24/Female
• Education: Two B.A.s at U.C. Berkeley, currently pursuing Ph.D. at Purdue U
• Culture: Chinese/American
• Language: English
• Physical limitations: -
• Computer experience: interacting with a terminal and using a smartphone, basic Windows experience
• Motivation: Plan errands and optimize daily routine
• Domain experience: -
• Application experience: uses a task list and google calendar on her phone
• Work environment: graduate student office, experimental physics lab
• Communication patterns: sends texts, emails and uses video skype.  Uses phone if these other mechanisms fail.

Martha is a 24 year old physics graduate student, pursuing a Ph.D. in the Midwest.  Like most graduate students, Martha spends most of her time in the lab, but completes her errands when she has enough of them built up.  We followed Martha around on a day of errands as she got ready to throw a weekend party at her apartment.

Martha uses a personal whiteboard to manage her TODO list.  When she decides to do errands, she copies the whiteboard to a post-it note and then goes down the post-it note in order.  Most of the time, Martha's roommate Rachael asks her to do some common area tasks, like buy paper towels, liquor, and such.  When this happens, Rachael will give Martha another TODO list, and Martha will use both of them for the errand run.

Lessons learned from Martha:

• Tasks are important, venue isn't necessarily important.  Moreover, sometimes where not to go is more important than where to do.  Martha had to buy a picture frame.  Martha didn't really care where we got the frame from, as long as it wasn't Walmart (we eventually went to Target).
• It would be very useful to have a smartphone say things like "start getting ready to leave now" and "you have 10 more minutes before you have to leave the supermarket"---especially if planning errands is done for you.
• Efficient grocery shopping is perhaps a more important problem than planning out a place-to-place schedule.  Most people fill a TODO list with groceries and look for the groceries in that order once they get to the store.  This usually wastes an hour for a large grocery run.  If users input their grocery list as a set of tasks, it seems that it would be very useful to sort the items by type.
• Specifying "do this errand first" and "do this errand last" is a very important constraint.  In the wintertime, Martha always stops at the Starbucks first so that the coffee keeps her warm.  In the summertime, she always does this step last as a reward for finishing her errands.  She usually incorporates lunch into her errands, and likes to get get lunch last so that she can eat it at home once she is done. 

Task Analysis

Traveler  -  

• Age/Gender: 21/Female
• Education: Two B.A.s at U.C. Berkeley, currently pursuing Ph.D. at Purdue U
• Culture: Chinese/American
• Language: English
• Physical limitations: -
• Computer experience: interacting with a terminal and using a smartphone, basic Windows experience
• Motivation: Plan errands and optimize daily routine
• Domain experience: -
• Application experience: uses a task list and google calendar on her phone
• Work environment: graduate student office, experimental physics lab
• Communication patterns: sends texts, emails and uses video skype.  Uses phone if these other mechanisms fail.

Martha is a 24 year old physics graduate student, pursuing a Ph.D. in the Midwest.  Like most graduate students, Martha spends most of her time in the lab, but completes her errands when she has enough of them built up.  We followed Martha around on a day of errands as she got ready to throw a weekend party at her apartment.

Martha uses a personal whiteboard to manage her TODO list.  When she decides to do errands, she copies the whiteboard to a post-it note and then goes down the post-it note in order.  Most of the time, Martha's roommate Rachael asks her to do some common area tasks, like buy paper towels, liquor, and such.  When this happens, Rachael will give Martha another TODO list, and Martha will use both of them for the errand run.

Lessons learned:

1. Input destinations
   • Goal: Allow the user to input destinations to visit
   • Preconditions:
     • Determined locations to visit
   • Subtasks:
     • auto-complete destination names
     • pre-load constraint information about destination like hours of operations (best hours to visit), average length of visit
2. Add/edit constraints for destinations
   • Goal: Modify constraints for destinations such as hours of operation, appointment times, duration of visit
   • Preconditions:
     • Know what time appointments are scheduled for
     • Have an estimate the amount of time that needs to be spent at each destination
   • Subtasks:
     • Add “global constraints” like between what times these destinations need to be visited or what type of transportation (car, public transit, walking) is preferred.
3. Auto-generate schedule
   • Goal: Using the destinations and constraints inputted by the user, our system will create a schedule to visit all the destinations that meets all the constraints. 
   • Preconditions:
   • Subtasks:
     • Display the generated schedule both on and a timeline.  
     • Display the optimal path between locations on a map
4. View and Adjust schedule
   • Goal: change and tweak any part of the schedule including the order of destinations, duration of visit, path to take between destinations...
   • Preconditions:
     •  
   • Subtasks:
     •