1. DAN, SONIT, ALLEGRA FOODCONNECT

2. BRIEF OVERVIEW …What are we doing, again? Our tasks The prototype in use Methods and results Changes made

3. WHAT ARE WE DOING, AGAIN? More fun, less waste! FoodConnect’s goals: Make volunteering more social Make food pick-ups more efficient for dining halls Make coordination easier for on-campus organizations like SPOON

4. REPRESENTATIVE TASKS 1. Enter weight of a pickup (simple)

5. REPRESENTATIVE TASKS 2. Change future weekly schedule (moderate) Current technology: Doodle poll and email! Schedule flexibility is minimal (determined at beginning of quarter)

6. REPRESENTATIVE TASKS 3. Accept a pickup request and invite another available volunteer (complex) Current technology: …email! Volunteers assigned to pairs for a quarter.

7. ALL THE LO-FI!

8. ENTERING WEIGHT

10. CHANGING SCHEDULE

13. ACCEPTING PICKUP/INVITING VOLUNTEER

15. EXPERIMENTAL METHOD SPOON volunteers are everybody and anybody, so we tested with… …a sophomore undergrad taking 22 units, living in the middle of campus (humbio and music major) …a second year grad student living on campus (cooks for himself) …a grad student majoring in stats and CS (software engineer intern)

16. EXPERIMENTAL METHOD Dan: notetaker Sonit: computer Allegra: taskmaster Main focus: Time taken to find features; number of errors; emotional cues. Location: Tresidder, grad housing lounge

17. RESULTS Tasks went smoothly except for changing the weekly schedule. In This Week’s Schedule: The “cancel” button was misleading; people thought that cancelling a pickup in This Week would change their future schedule.

18. CHANGES MADE

19. RESULTS Tasks went smoothly except for changing the weekly schedule. In Future Schedule: Drop-down menu for new available times was not obvious enough. Users wanted to be able to un-select their current time and reselect their new time, OR directly edit the time. After finishing the edit, users preferred that they be taken back to the main page.

20. CHANGES TO BE MADE

21. SUMMARY More fun, less waste! Some things we learned: Too many levels of indirection can be messy—ex. using a drop-down menu instead of editing a value directly We need to think carefully about the different paths a user can take to complete a task, and whether they are misleading—ex. one user thought cancelling one pickup would change his weekly schedule permanently.