The 21st Century Hunter-Gatherer

Usability for Foodies

Finding and selecting dinner used to be simpler

Dinner isn’t as easy as it used to be

No spear

(not Kosher

in post 911

America)

Robe gets in the way when

chasing mammoth

Modern TVAdversely affects eyesight

Comforts of

civilization

have softened

our primal

nature

Modern dinner selection can be a hassle

1,000’s of recipes, but you only need one.

You can even take them with you on your PDA as an App

Project Scope

• Develop an improved interface for recipe information delivery to users who are not proficient at cooking

Initial Goals

• Generate a prototype delivery system for a set of similar recipes from a single cuisine

• Distill prototype into a method for creating delivery systems for a variety of recipes from various cuisines

• Use various types of information gathering learned in INFO I561 and test the capabilities of each

• Get a good grade on the project for the INFO I561 class

So we set out in search of test subjects, data and to find out just how it is people forage for food in

modern society

Our Test Subjects = Young, inexperienced and definitely not chefs

• Teens, early 20’s

• Little cooking exp.

• Simple recipes

• Most use web

Subject Interview Data (Values)

• Simplicity • Ingredients on hand• Ratings• Clear instructions/Terminology• Ordering of instructions to workflow• They like pictures

Affinity Diagram

Workflow

Conceptual Prototype

So our subjects thought…

And they thought…

We worked

And We Worked

Results

Quick Plug for Balsamiq Mockups

http://www.balsamiq.com

Conceptual Prototype Demo

Click Here

Usability Study

• Asking:– Do the metaphors match the user?– Does the design intent match use case scenarios?– Are the barriers to cooking addressed?

• Not asking:– How well do the users perform?– Are the page layouts optimized?– Is the product complete?

Prototype Data User #1

• Did not understand purpose of prototype• Too elementary • Too many clicks – everything on one page• No home button if change mind• Too complicated for a simplistic idea

Prototype Data User #1 Cont.

• Generally understood direction• Clear idea of preparation• Video would be improvement

Prototype Data User #2

• Liked simplistic layout• Approved of the 3-options interface “I don’t

want too many options at a time.”• Wanted some way to look for recipes

previously seen, suggested a photo wall “I’m not even looking at the names.”

• Felt the need to input to every category “I’m a completionist.”

Prototype User Data Cont.

• Liked visual timeline, suggested a way to distinguish visually between “active” and “inactive” cooking time

• Disliked terminology and methods centered around choosing a recipe to make later, suggested a shopping cart metaphor

• Would not ever print shopping list “I might have some of the ingredients, and I’ll be shopping for other things, too.”

Prototype User Data Cont.

• Felt recipe instructions were complete when supplemented by pictures

• Wanted to be able to access instructions during the recipe browsing if interested in the recipe but not as part of the standard display

Suggested Next-steps

• Make overall product intent more obvious• Change recipe “choosing” metaphor to be less

fixed and more leisurely• Present browsing options in a way that do not

encourage “completion”• Make all recipe data available but keep initial

interface simple, maybe even simpler• Add supplemental, non-random browsing

Prototype User Data Cont.

• Generally understood direction• Clear idea of preparation• Video would be improvement

Questions?????