Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Eliminating UX Debt in the Enterprise

665 views

Published on

You'll learn:

- How to identify and classify design debt
- How to solve product quality issues in fast-paced teams.
- How to address, avoid, and manage design debt.

Published in: Design
  • Be the first to comment

Eliminating UX Debt in the Enterprise

  1. 1. I’ll gladly pay you Tuesday for a hamburger today. Managing UX Debt Jack Moffett Manager App Development – GUI Inmedius, a Boeing Company @jackmoffett jackmoffett@mac.com designaday.tumblr.com
  2. 2. UX debt is the accumulation of decisions made during design and development that negatively impact the users of a product or service. Photo by Trey Guinn
  3. 3. Photo by Benjamin Balázs
  4. 4. The Big 3
  5. 5. The Big 3 Acquisition Outsourcing Neglect
  6. 6. Acquisition
  7. 7. Acquisition
  8. 8. Acquisition
  9. 9. Acquisition
  10. 10. Acquisition
  11. 11. Acquisition
  12. 12. Acquisition UX should be involved in evaluation of products considered for acquisition.
  13. 13. Acquisition UX should be involved in evaluation of products considered for acquisition. Document the debt as soon as acquisition occurs, and track it.
  14. 14. Outsourcing
  15. 15. Outsourcing UX should collaborate closely with contractors.
  16. 16. Outsourcing UX should collaborate closely with contractors. Set clear expectations at the outset.
  17. 17. Outsourcing UX should collaborate closely with contractors. Set clear expectations at the outset. Schedule regular quality checks and involvement from all parts or your team: design, development, testing, and management.
  18. 18. Photo by Julie Mac
  19. 19. Neglect
  20. 20. Neglect Put processes in place that assure awareness of development efforts.
  21. 21. Neglect Put processes in place that assure awareness of development efforts. Team dynamics are hugely important.
  22. 22. Neglect Put processes in place that assure awareness of development efforts. Team dynamics are hugely important. Resist the urge to turn a blind eye to things you don’t feel like working on.
  23. 23. Photo by y____
  24. 24. Intentional Debt
  25. 25. Intentional Debt Resistance to change
  26. 26. Intentional Debt Resistance to change Incremental enhancement
  27. 27. Intentional Debt Resistance to change Incremental enhancement Product management strategy
  28. 28. Intentional Debt Product management strategy
  29. 29. Intentional Debt Product management strategy Focusing on new features
  30. 30. Intentional Debt Product management strategy Focusing on new features customer requests
  31. 31. Intentional Debt Product management strategy Focusing on new features customer requests time to market
  32. 32. Intentional Debt Product management strategy Focusing on new features customer requests time to market backwards compatibility
  33. 33. Photo by nicodemo.valerio
  34. 34. unIntentional Debt Mistakes and laziness
  35. 35. unIntentional Debt Mistakes and laziness Lack of design
  36. 36. unIntentional Debt Mistakes and laziness Lack of design Lack of empowerment
  37. 37. unIntentional Debt Mistakes and laziness Lack of design Lack of empowerment Separation of design & dev
  38. 38. unIntentional Debt Mistakes and laziness Lack of design Lack of empowerment Separation of design & dev Too many cooks
  39. 39. unIntentional Debt Mistakes and laziness Lack of design Lack of empowerment Separation of design & dev Too many cooks Customer inefficiencies
  40. 40. Identifying UX Debt
  41. 41. Identifying UX Debt Active Peripheral Awareness UX Debt Inventory User Exposure
  42. 42. Photo by Emilio Labrador
  43. 43. Practice Active Peripheral Awareness
  44. 44. Practice Active Peripheral Awareness Awareness of technology
  45. 45. Practice Active Peripheral Awareness Awareness of technology Awareness of design practice
  46. 46. Perform A UX Debt Inventory
  47. 47. Perform A UX Debt Inventory Use the product. Take notes.
  48. 48. Perform A UX Debt Inventory Use the product. Take notes. Better yet, have a teammate take notes. Then switch.
  49. 49. Perform A UX Debt Inventory Use the product. Take notes. Better yet, have a teammate take notes. Then switch. Validate it by observing and talking with users.
  50. 50. Perform A UX Debt Inventory Use the product. Take notes. Better yet, have a teammate take notes. Then switch. Validate it by observing and talking with users.
  51. 51. Expose Your Team
  52. 52. Expose Your Team “It seems that six weeks was the bare minimum for a two-hour exposure dose. The teams with members who spent the minimum of two hours every six weeks saw far greater improvements to their design’s user experience than teams who didn’t meet the minimum.” – Jared Spool
  53. 53. Expose Your Team “It seems that six weeks was the bare minimum for a two-hour exposure dose. The teams with members who spent the minimum of two hours every six weeks saw far greater improvements to their design’s user experience than teams who didn’t meet the minimum. And teams with more frequent exposure, say two- hours every three weeks, saw even better results.” – Jared Spool
  54. 54. Classifying UX Debt Photo by Squiggle
  55. 55. 4 UX Debt Categories Technical Functional Behavioral Visual
  56. 56. 4 UX Debt Categories Technical
  57. 57. 4 UX Debt Categories Technical Back End Performance, Database, Security
  58. 58. 4 UX Debt Categories Technical Back End Front End Performance, Database, Security Browser Version Support Outdated HTML/Frameworks Poor Coding Practices
  59. 59. 4 UX Debt Categories Technical Functional
  60. 60. 4 UX Debt Categories Technical Functional Scale
  61. 61. 4 UX Debt Categories Technical Functional Scale Information Architecture
  62. 62. 4 UX Debt Categories Technical Functional Scale Information Architecture Priority of Functions
  63. 63. 4 UX Debt Categories Technical Functional Behavioral
  64. 64. 4 UX Debt Categories Technical Functional Behavioral Tool Time
  65. 65. 4 UX Debt Categories Technical Functional Behavioral Tool Time Consistency
  66. 66. 4 UX Debt Categories Technical Functional Behavioral Tool Time Consistency Conventions
  67. 67. 4 UX Debt Categories Technical Functional Behavioral Visual
  68. 68. 4 UX Debt Categories Technical Functional Behavioral Visual UI Chrome Iconography Consistency Fashion Branding Copywriting
  69. 69. 4 Technical Functional Behavioral Visual UX Debt Categories
  70. 70. Technical Functional Behavioral Visual UX Debt Categories 5
  71. 71. Technical Functional Behavioral Visual Documentation UX Debt Categories 5
  72. 72. Technical Functional Behavioral Visual Documentation UX Debt Categories 5
  73. 73. Addressing UX Debt
  74. 74. Addressing UX Debt Declare bankruptcy
  75. 75. Addressing UX Debt Declare bankruptcy People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying “no” to 1,000 things. Steve Jobs
  76. 76. Addressing UX Debt Declare bankruptcy Call a do-over
  77. 77. Addressing UX Debt Declare bankruptcy Call a do-over Skunkwork it
  78. 78. Addressing UX Debt Declare bankruptcy Call a do-over Skunkwork it Phased approach
  79. 79. Step 1: Photo by Captain Eric Willis
  80. 80. Step 1: Prioritization
  81. 81. Step 1: a. Severity & Impact Prioritization
  82. 82. Step 1: a. Severity & Impact b. Estimated Time to Address Prioritization
  83. 83. Step 1: a. Severity & Impact b. Estimated Time to Address c. Responsible Party Prioritization
  84. 84. Step 1: a. Severity & Impact b. Estimated Time to Address c. Responsible Party Prioritization
  85. 85. Step 2: Photo by John Biehler
  86. 86. Step 2:Schedule
  87. 87. Step 2:Schedule Not Agile
  88. 88. Step 2: Agile Schedule
  89. 89. Step 3: Photo by John Biehler
  90. 90. Step 3:Collaboration
  91. 91. Step 3:Collaboration UX debt is the responsibility of your entire organization.
  92. 92. Avoiding UX Debt Photo by Alex Berger
  93. 93. Avoiding UX Debt Usability Research & Testing
  94. 94. Avoiding UX Debt Usability Research & Testing Pay Attention to Details
  95. 95. Avoiding UX Debt Usability Research & Testing Pay Attention to Details Modularity
  96. 96. Avoiding UX Debt Usability Research & Testing Pay Attention to Details Modularity Documentation
  97. 97. Manage your UX Debt Photo by Dave 77459
  98. 98. Thank you! Jack Moffett Manager App Development – GUI Inmedius, a Boeing Company @jackmoffett jackmoffett@mac.com designaday.tumblr.com

×