The document discusses various topics related to user experience, including defining user experience, modeling users, evaluating usability, and visual design guidelines. It explains that user experience is made up of dependent layers including the surface, skeleton, structure, scope, and strategy. Methods for understanding users such as personas, profiles, and scenarios are presented. The importance of usability testing to evaluate a product is emphasized.

1. User Experience Distilled Jeff Patton Architect, Interaction Designer, & Agile User Experience Evangelist [email_address] www.AgileProductDesign.com

5. The Surface Layer Describes Finished Visual Design Aspects Surface Skeleton Structure Scope Strategy

6. The Skeleton Describes Screen Layout and Functional Compartments in the Screen Surface Skeleton Structure Scope Strategy

7. Structure Defines Navigation from Place to Place in the User Interface task panes modal dialogs modal wizards Surface Skeleton Structure Scope Strategy

10. Understanding the Relationship Between Goals, Tasks, & Tools is Critical Software Product Goals Tasks Tools Features one or more users engaged in many tasks in support of a common high level goal is often referred to as workpractice

14. Arranging tasks by affinity allows me to think about contexts that best support tasks. Contexts in a home have common names we all know. Surface Skeleton Structure Scope Strategy

15. When designing a particular interaction context such as a “kitchen,” I optimize layout and tool choices to support tasks I’ll do there Surface Skeleton Structure Scope Strategy

16. I’m going to spend a lot of time here, I want my experience to be as pleasant as possible… Surface Skeleton Structure Scope Strategy

25. For a given piece of software user experience is often considered more or less relevant often for economic reasons Internal use commercial sale users opt-in compelled use generates revenue reduce costs company portal online tools (google, yahoo) shrink-wrap consumer software (quicken, ms money) ecommerce software (amazon, expedia) enterprise class accounting (sap, oracle) crm applications (salesforce.com, siebel) call center software company time tracking user adoption purpose

26. For a given piece of software user experience is often considered more or less relevant often for economic reasons Internal use commercial sale users opt-in compelled use generates revenue reduce costs user adoption purpose

27. For a given piece of software user experience is often considered more or less relevant often for economic reasons Internal use commercial sale users opt-in compelled use generates revenue reduce costs company portal online tools (google, yahoo) shrink-wrap consumer software (quicken, ms money) ecommerce software (amazon, expedia) enterprise class accounting (sap, oracle) crm applications (salesforce.com, siebel) call center software company time tracking How relevant is user experience in your company? Does it vary for the different pieces of software in your company? user adoption purpose

40. Build a Componentized Paper Prototype

65. Jeff Patton [email_address] www.AgileProductDesign.com User Experience Distilled You can download the most current version of these slides at: http://www.agileproductdesign.com/presentations