Design for humans not robots - WCUS

Iteration on the talk given at WordCamp US in Philadelphia.

Transcript

1. Design for humans not robots Tammie Lister
3. www.intertech.com/Blog/funny-computer-error-messages/ Server said: OOPS: child died
8. x
12. medium.freecodecamp.com/5-mistakes-to-avoid-when-designing-micro-interactions-a6f638ee6a86#.b8ha632v5 Because Medium is sad when you tweet without a header image
13. Calling something an edge case is literally saying, “this is not important enough to care about.” - Sara Wachter-Boettcher DESIGN FOR REAL LIFE
 by ERIC MEYER & SARA WACHTER-BOETTCHER abookapart.com/products/design-for-real-life
15. i-remember.fr
16. www.nyan.cat
18. https://ifttt.com/wtf
19. Cueva de las Manos
20. BOB 104 105 106 107 101 102 103
26. Optional fields denoted by *
27. thenextweb.com/dd/2015/09/29/6-examples-of-awful-ux-design
28. medium.freecodecamp.com/5-mistakes-to-avoid-when-designing-micro-interactions-a6f638ee6a86#.b8ha632v5 “Are these animation details keeping the micro-interaction clean, or are they hosing the user experience, muddying the waters and adding to cognitive load?”
 
 - Issara Willenskomer
29. xkcd.com/1579
30. codepen.io/vineethtr/pen/MwrPgK
31. medium.com/@thomasfuchs/how-to-write-an-error-message-883718173322#.n75owf21y
33. Three laws of human design: based on Issac Asimov’s Three Laws of Robots en.wikipedia.org/wiki/Three_Laws_of_Robotics
34. An interface may not injure a human being or, through inaction, allow a human being to come to harm – harm is emotional. RULE 1
35. An interface must obey orders given to it by human beings 
 except where such orders would conflict with the first law – 
 it should just work. RULE 2
36. An interface must protect its own existence as long as such a protection doesn’t conflict with the first or second law – it shouldn’t just vanish or disappear. RULE 3
38. Tammie Lister @karmatosed Thanks speakerdeck.com/tammielis/design-for-humans-not-robots-wcus