McInterface SIMS 213 Spring 2001 Linda Harjono Saifon Obromsook John Yiu Chi Wai.
Embed Size (px)
Transcript of McInterface SIMS 213 Spring 2001 Linda Harjono Saifon Obromsook John Yiu Chi Wai.
SIMS 213 Spring 2001Linda Harjono
Saifon ObromsookJohn Yiu Chi Wai
What is McInterface?
• The interface for McDonald’s electronic ordering system
• Eliminates verbal communications between cashiers and customers
• Customers have more control in customizing their food
• “We are making your burger.”
• Joseph Jones - kid• Michael Cooper - teenager• Ming Zhou – graduate student• Julie Woods – housewife with kids• Loretta Sanchez – McDonald’s
• Ming Zhou – typical type of repeat customers, does not want to pay by a credit card, hesitates to communicate with the cashier
• Julie Woods – have kids who want toys (cover Joseph), different special requests, low computer skill (cover Mike)
• Loretta – edge-case
Testing Low-Fi Prototype
• “I want to use cash!”• “Why would I need a McCard?”• “What’s a MyFav?”• “Too many decisions to make!”• “Too many steps, I would just go
up to the cashier!”• “Where are the toys?”
• Hold off the McCard (the smart card) function for this prototype– MyFavorite – useful?– Adding value to McCard
• Allow cash, ATM & credit cards• Focus on the ordering process
• Ming buys a Big Mac Meal (Quickest version)
• Mike buys 2 McDoubles, 2 Cokes and 1 large fries for himself and his date
• Mrs. Woods buy a meal for herself and whichever meals that offer toys for her kids.
• Minimize number of required steps and decisions– Tabs (2-level) to a list (1-level) menu ->
hide order summary to make more space– Rearrange item details (associate sauce to
food item)– Language selection as starter
• Preview toys• Eliminate ‘tray’ concept
First Interactive Prototype
• Microsoft Access plus VBA• Not much of the graphics yet• Leave out…
– Error handling mechanism– Some food categories: New Tastes & Mini Meal
Deals– Certain Item Details: dressing, dessert flavor
• Not plan to implement– Touch-screen– Other languages– Interactive feedback in payment activities
• Don’t focus too much on the implementation!
• It’s easy to lose focus on the users. Don’t!
• Be bold in throwing away bad designs• User testing is a must.• Paper prototypes are extremely
useful• So, iterate, iterate, iterate!!!