1. Design for Strangers: Effective User Experience Design When Your Users are on Another Continent Rashmi Sinha Jonathan Boutelle Uzanto Consulting

16. Heuristic 1: Visibility of system status The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. searching database for matches

66. Understanding User Needs Afternoon Session

82. Development of Scenarios Joe needs to input his location into his palm. Input what kind of food he wants or the program can use defaults The information returned: list of possible restaurants along with their relevant details, kinds of food etc. More details about each on request: details such as the availability of beer, if they take credit cards, links to reviews etc.

83. Development of Scenarios The information returned to Joe needs to be broad (offer a number of options) and deep (offer more details upon request) Location Information is another concern of Joe’s. Ideally he wants exact distance & directions to restaurant. Not possible, not live website

84. Development of Scenarios What else does Joe need? To mark restaurants that he liked. Lets think more… Compromise : Tag restaurants in terms of neighborhoods. Joe can give current neighborhood. Can be shown map with neighborhoods marked out & approximate distances.

85. Our secondary Persona Does this design make Dan happy? Designing for one specific user often makes other users happy as well.

99. Free-listing methods for understanding scope and boundary of domain

101. Free-listing menu for Mc Donald’s User No 1 French fries Cheese burger Shake Hamburger French fries Chicken sandwich Chicken Mcnuggets Fish sandwich Shake Hamburger User No 2 French fries Chicken Cheese burger Shake User No 4 Chicken Mcnuggets Cheese burger Bacon cheese burger French fries User No 5 Hamburger Quarter pounder Big mac Chicken fajita French fries Apple pie User No 3 Hamburger Cheese burger French fries Mc rib Chicken sandwich

105. Card-sorting and other methods for designing information architecture

114. Swimming with Sharks: The Business of Usability

116. Stakeholder Analysis

122. Recording your understanding

125. Building a Business Case for Usability

134. Revised technology life-cycle chasm main street tornado Early Adaptors Innovators Early Majority Late Majority Laggards bowling alley

138. Thank you [email_address] [email_address] slides and other material will be posted at www.uzanto.com/papers/indiamar04