$30 off During Our Annual Pro Sale. View Details »

Dean Schuster — Chips and Pickle Story — UX Y'all 2022

UX Y'all
September 27, 2022

Dean Schuster — Chips and Pickle Story — UX Y'all 2022

UX Y'all

September 27, 2022
Tweet

More Decks by UX Y'all

Other Decks in Design

Transcript

  1. UX Y’all 2022 @ExperienceDean

  2. @ExperienceDean

  3. @ExperienceDean

  4. What’s Really Behind Infamous, Historic UI Failures The Chips &

    Pickle Story: @ExperienceDean
  5. @ExperienceDean

  6. @ExperienceDean

  7. @ExperienceDean

  8. @ExperienceDean

  9. @ExperienceDean

  10. @ExperienceDean

  11. @ExperienceDean

  12. @ExperienceDean

  13. CHIPS + PICKLE @ExperienceDean

  14. @ExperienceDean

  15. PICKLE CHIPS @ExperienceDean

  16. CHIPS + PICKLE @ExperienceDean

  17. @ExperienceDean …

  18. @ExperienceDean

  19. @ExperienceDean

  20. @ExperienceDean

  21. @ExperienceDean

  22. @ExperienceDean

  23. @ExperienceDean

  24. @ExperienceDean

  25. @ExperienceDean

  26. Bad UI choices @ExperienceDean

  27. Bad UI choices have ruined my sandwich. @ExperienceDean

  28. Bad process @ExperienceDean

  29. Bad process made things worse @ExperienceDean

  30. 1st World Problem @ExperienceDean

  31. Real Problems @ExperienceDean

  32. @ExperienceDean

  33. 38 Minutes to Live @ExperienceDean

  34. @ExperienceDean

  35. @ExperienceDean

  36. 38 Minutes Later… @ExperienceDean

  37. @ExperienceDean

  38. Kenneth P. Vogel / Star Advertiser

  39. @ExperienceDean

  40. @ExperienceDean

  41. @ExperienceDean

  42. @ExperienceDean

  43. @ExperienceDean

  44. @ExperienceDean

  45. @ExperienceDean

  46. @ExperienceDean

  47. @ExperienceDean Are you sure you want to cause mass panic?

    OK Cancel
  48. Poor Computer Software design? @ExperienceDean

  49. Human Factors? @ExperienceDean

  50. “I did what I was trained to do.” “I can’t

    say that I would do anything differently based on what I saw and heard.” @ExperienceDean
  51. Self-Evident UI Quirks @ExperienceDean

  52. Appalling Content Strategy Poor Naming & Organization Multiple Confusing Choices

    @ExperienceDean
  53. Feature Failures Live and Test Alerts in Same Interface Can’t

    Review Sent Messages Allows Users Too Much Control @ExperienceDean
  54. Process Breakdown @ExperienceDean

  55. Poor Communication @ExperienceDean

  56. Poor Communication Faulty Procedures @ExperienceDean

  57. Poor Communication Faulty Procedures Inadequate Training @ExperienceDean

  58. Poor Communication Faulty Procedures Inadequate Training Bumbling Response @ExperienceDean

  59. Mutual Blame @ExperienceDean

  60. @ExperienceDean

  61. Meltdown (Almost) @ExperienceDean

  62. @ExperienceDean

  63. @ExperienceDean

  64. @ExperienceDean

  65. @ExperienceDean

  66. @ExperienceDean

  67. @ExperienceDean

  68. @ExperienceDean

  69. @ExperienceDean

  70. @ExperienceDean

  71. Function Foremost @ExperienceDean

  72. Works as Specified @ExperienceDean

  73. Works as Specified Human Behavior Interferes @ExperienceDean

  74. Works as Specified Human Behavior Interferes Usability is an Afterthought

    @ExperienceDean
  75. Process Failure @ExperienceDean

  76. Poor Communication @ExperienceDean

  77. Poor Communication Inefficient Problem Solving @ExperienceDean

  78. Poor Communication Inefficient Problem Solving Rigid Bureaucratic Systems @ExperienceDean

  79. Poor Communication Inefficient Problem Solving Rigid Bureaucratic Systems No One

    is Wrong @ExperienceDean
  80. None
  81. Butter fl y @ExperienceDean

  82. @ExperienceDean Bush 246 Gore 266 Undecided 25

  83. @ExperienceDean

  84. @ExperienceDean

  85. None
  86. None
  87. None
  88. None
  89. None
  90. None
  91. None
  92. None
  93. None
  94. @ExperienceDean

  95. Inept Design @ExperienceDean

  96. @ExperienceDean Awkward Experience

  97. Awkward Experience Design Fits the Machine @ExperienceDean

  98. Strategic Malpractice @ExperienceDean

  99. Best Case Scenario Only @ExperienceDean

  100. Best Case Scenario Only No Plan for Failure @ExperienceDean

  101. Best Case Scenario Only No Plan for Failure Implications Ignored

    @ExperienceDean
  102. @ExperienceDean

  103. Ye Briney Cucumber @ExperienceDean

  104. CHIPS + PICKLE @ExperienceDean

  105. UX/UI Offenses @ExperienceDean

  106. Function Fit @ExperienceDean

  107. Function Fit Internally Focused @ExperienceDean

  108. Function Fit Internally Focused Inconsistent @ExperienceDean

  109. Function Fit Internally Focused Inconsistent Icky for Dean @ExperienceDean

  110. CHIPS + PICKLE @ExperienceDean

  111. Slapdash Process @ExperienceDean

  112. Poor Edge-Case Testing @ExperienceDean

  113. Poor Edge-Case Testing Lost in Translation @ExperienceDean

  114. Poor Edge-Case Testing Lost in Translation No Controls @ExperienceDean

  115. Poor Edge-Case Testing Lost in Translation No Controls Dean Always

    Gets a Dang Pickle @ExperienceDean
  116. Signi fi cance @ExperienceDean

  117. None
  118. @ExperienceDean

  119. “I can’t do my job without the Intranet.” “When do

    I use the intranet? Only when I have to! ...Which is every day.” “It’s on LexLoop… somewhere.” “The employee search still lists my department from nine years ago.” “I need to show doctors correct care procedures quickly, to show them they’re wrong.” “The search doesn’t recognize the language we [nurses] use. If I search IVT, it doesn’t recognize that—it wants me to search ‘intravenous.’ Meanwhile, my patient could be bleeding out.” @ExperienceDean
  120. “I can’t do my job without the Intranet.” “When do

    I use the intranet? Only when I have to! ...Which is every day.” “It’s on LexLoop… somewhere.” “The employee search still lists my department from nine years ago.” “I need to show doctors correct care procedures quickly, to show them they’re wrong.” “The search doesn’t recognize the language we [nurses] use. If I search IVT, it doesn’t recognize that—it wants me to search ‘intravenous.’ Meanwhile, my patient could be bleeding out.”
  121. “I can’t do my job without the Intranet.” “When do

    I use the intranet? Only when I have to! ...Which is every day.” “It’s on LexLoop… somewhere.” “The employee search still lists my department from nine years ago.” “I need to show doctors correct care procedures quickly, to show them they’re wrong.” “The search doesn’t recognize the language we [nurses] use. If I search IVT, it doesn’t recognize that—it wants me to search ‘intravenous.’ Meanwhile, my patient could be bleeding out.”
  122. Musings @ExperienceDean

  123. Minor things have a major impact. @ExperienceDean

  124. Process is equally vital. @ExperienceDean

  125. A Broader Purpose @ExperienceDean

  126. Pickles are just terrible. @ExperienceDean

  127. @ExperienceDean

  128. @ExperienceDean dean.schuster@truematter.com @ExperienceDean truematter.com/DeanSchuster blog.truematter.com

  129. @ExperienceDean truematter.com/DeanSchuster Presentation Notes 
 The Chips and Pickle Story:

    What’s Really Behind Infamous, Historic UI Failures
  130. © copyright True Matter, LLC Every element in this slide

    deck (except where noted) is the property of or licensed to truematter. Content, images, design, or elements may be used only by express written permission.