Introduction to HCI CS 565

HW #1 and Design Principles T&T #4, #9 Visibility of user’s options/actions. Sometimes described as “visibility of system state” Feedback Constrain (making certain errors impossible) eg: menus vs typing to prevent syntax errors. (Internal) consistency Affordance: HOW to do things with an object

World’s Worst Feedback Example (Oregon Tax Dept) Is this spam?

T&T #1, #2 Invisible element, Effectively invisible element <doc cam>

Design Activities: Mapped to PRICPE Process Process activities Identify needs/requirements of the user experience. Develop alternative design ideas that meet the requirements. Build prototypes of the designs to communicate/assess. Evaluate iteratively throughout the process. Pre-dispositions Research Insights Concept Prototype Evaluate

In-Class Re-Design Activity You have until <time> to re-design: Walmart’s on-line grocery. Order from home, food arrives. Scenario: “Abby” wants to decide if she wants to use this. Goal: hands-on practice with the re-design process. How: Use PRICPE process. Use PAPER. Pick a population: should help narrow down the 1st P a bit. Write what you know & what you DON’T KNOW (1st P) on PAPER. (We’ll skip R, but you might get a few Insights from group discussion.) E: Find some problems for Abby (tools: T&Ts, design principles, Abby). When ready, SKETCH Concepts/Prototypes on PAPER to fix them. Why would your solution work for that population? We’ll look at a few with the doc scanner.