Claims Analysis:Example ‘Hall of Fame/Shame’

Presentation

Chris North

CS 3724: Intro to HCI

Presentations(Hall of Fame/Shame)

• See course calendar on website • Teams of 2• 5% of grade• 5 minutes, 3-4 slides

• Practice

• Bring on CD, usb key, or laptop

• Pick UI of your choice (software or real-world)• UI critique

• Scenarios

• Claims analysis (include pictures)

• Redesign ideas

• Vote: UI Hall of Fame/Shame

UI: Fast Food Drive-Thru Menus

• Scenario:• College students (Bburg)

• Hungry

• Get food, get out. FAST!

• Often: sandwich, fries, drink

• Typically: Not sure what I want

• Sometimes: Know what I want

• Passengers want food too

• Budget is important, limited cash

Note: Tell the story of the users and their tasks, highlighting key requirements.

Claims 1• Design choice 1: Billboard menu – large visual

tabular layout of all food choices:• + all in one view enables fast decisions for the students

• + organized by categories supports quick browsing

• + tabular layout fast for visually scanning prices (supports the budget-minded students)

• - see menu too late, slows down ordering process or rushed

• - passengers can’t see menu well, not happy with order

Note: Identify important UI design choice in the system, then identify the +/- measurable effects of that choice on the users in the scenario.

Claim 1a: example of detailed choice

• Design choice 1a: Billboard menu uses pictures of meals instead of text

• + helps them visually decide what they are hungry for

• + pictures faster than reading textual descriptions

• - pictures take up a lot of space, big sign difficult for passengers to see

• - some pictures look similar,reducing order accuracy

Note: It is important to consider what the alternative design choices would have been (e.g. textual menu).

Claims 2

• Design choice 2: Microphone/Speaker voice-based interaction

• + easy access, fast and no learning

• + human in the loop, supports error recovery & questions

• - passengers must order thru driver: slow, errors

• - winter, Brrrrr! Low subjective satisfaction

• - can’t understand what they say, poor audio feedback: errors and limited cost feedback

• - they can’t hear me over my ’87 VW -- do students drive old cars?

Other potential good design choices

• Combo meals • +Make common tasks fast

• Separate Budget menu (e.g. Wendy’s $1 menu)• +Gives limited-cash students 1 place to look on menu

• Get price before proceeding• +Can get out cash while waiting, saves time

• Visual feedback on order (e.g. Wendy’s LCD screen)• +More order accuracy, price break-down

Re-Design Ideas

• Simple re-design ideas:• More billboard menus back in line

+ ready to order when reach microphone

- might be confusing where to order?

• Menu on both sides of car

• Microphone on both sides of car

• Radical re-design: cell phone, in-car UI+ solves audio problems

+ solves winter problems

+ solve passenger problem, can hand-off phone

+ could order before arriving if no menu needed, faster

- Possible Cell phone call costs

- Time to dial #

Note: Identify alternative design choices, how they would address -’s, and what new +/-’s are introduced.

Identifying Design Trade-offs

Microphone on 1 side• - Slow and mistakes on

passenger orders• + forces serial order

• + 1 window down in winter

• + standard, no learning

Microphone on 2 sides• +Fast and Accurate

passenger order• - confusion when both

talk at same time• - 2 windows down in

winter• - non-standard, some

initial learning req’d