Simple is not Easy

1,682 views

Published on

This presentation is about 3 simple strategies to create software user interfaces easier to use by hiding complexity.

Published in: Technology, Self Improvement
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,682
On SlideShare
0
From Embeds
0
Number of Embeds
748
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Simple is not Easy

  1. 1. easysimple is not
  2. 2. my name is Robon3and I work at
  3. 3. we are overwhelmed withcomplexity
  4. 4. complex information
  5. 5. complex tasks
  6. 6. complex relationships
  7. 7. simplicity is rare
  8. 8. care?why should you
  9. 9. 41%software projects failed to delivervalue or ROI cio.com
  10. 10. UX is notrocket science
  11. 11. what issimplicity?
  12. 12. Simple just works intuitively
  13. 13. simple is not easy
  14. 14. The problem is thatsimple things are madeunnecessarily complex
  15. 15. youwhat can do about it?
  16. 16. simpletechniques that work
  17. 17. hidefeatures &drop downshidden panels
  18. 18. features mainstream users rarely use
  19. 19. show just what isnecessary
  20. 20. utilizecontext &right-click menus
  21. 21. location is very important
  22. 22. one-time keys to hiding settings precision contro ls don’t force cu s to mization reveal hidden items just in time
  23. 23. organize
  24. 24. shapecolor hierarchy positionsize
  25. 25. logicalgroupings of around 7memory sweet spot
  26. 26. arrange informationlogically format type alphabetically
  27. 27. we prefer toselect from choicesover searching
  28. 28. nice and neat
  29. 29. sizedoes matter
  30. 30. tune in our brains on colors
  31. 31. providedirect routes
  32. 32. innovationi s g r e a tchanging habits isdifficult
  33. 33. remove
  34. 34. more is not better
  35. 35. unnecessary
  36. 36. hard just because it’sdoesn’t get rid of it mean
  37. 37. users value features thatrelate to &everydayeliminatefrustrations
  38. 38. poorlyGet rid of implemented features why should we keep this?
  39. 39. what if? is notjustification
  40. 40. prioritize the user goals
  41. 41. does it completely meet the
  42. 42. does it alleviate stress effortlessly?
  43. 43. minimizeoptionsto eliminate paralysis
  44. 44. smart &defaults preferences
  45. 45. extra removewords
  46. 46. be careful to notover do it
  47. 47. hideorganizeremove
  48. 48. exceed do not maximum capacity
  49. 49. g o o d d e s i g n i s n o thow to makei t s i m p l e r but where to move complexity
  50. 50. thank you@robrusher on3solutions.com @on3solutions

×