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.

UX Terror. Know your rights. (Front Trends 2015)

2,369 views

Published on

UPDATE: A reference that I missed to place in the presentation - Mr. T diagram comes from Neil Turner's article "What makes a good UX designer?" http://www.uxforthemasses.com/what-makes-good-ux-designer/

Do you miss the times when Front-End devs were called Web MASTERS? When you did not have to wait for ages for someone else to design a simple form? When there was nobody stalking you to move a button 2px to the left? When there was no philosophy behind the placement of a search field?
Anyway… these days are gone, baby. UX is here to stay, at least for some time, so let’s figure out ways to work together. In the end we all want to make things we are proud of.
We’ll learn what you can actually request from your UX team (guess what, it’s not just prototypes!), when to speak up and how to communicate with UX folks to be effective.

Published in: Internet
  • Be the first to comment

UX Terror. Know your rights. (Front Trends 2015)

  1. 1. UX Terror. Know your rights. Front Trends 2015, Natalia Rózycka .
  2. 2. Prototype
  3. 3. Spot 10 differences Prototype What I get from the dev team
  4. 4. Are UX people #$%^!?
  5. 5. No.
  6. 6. The end
  7. 7. Myth 1: UX = prototyping
  8. 8. BUSINESS TEAM WORKING GRAPHIC DESIGN Depth of experience DESIGN TECHNICALRESEARCH Mr. T from the “A- Team”
  9. 9. Myth 2: Lo-fi prototypes are sufficient
  10. 10. Myth 3: UX folks are stubborn
  11. 11. ★ Consistency of the entire solution
  12. 12. ★ Consistency of the entire solution ★ Known UI patterns
  13. 13. ★ Consistency of the entire solution ★ Known UI patterns ★ Already tested on users
  14. 14. Smooth FE / UX collaboration in 3 easy steps
  15. 15. Step 1: Lean in
  16. 16. Step 2: Set it up like a pro
  17. 17. UX Deliverables
  18. 18. UX Deliverables Business context and users’ insights
  19. 19. UX Deliverables Business context and users’ insights Styleguide
  20. 20. UX Deliverables Business context and users’ insights Styleguide Prototypes
  21. 21. UX Deliverables Business context and users’ insights Styleguide Prototypes Supplementary documentation: e.g. workflows links to examples
  22. 22. UX Deliverables Business context and users’ insights Styleguide Prototypes Graphic design (as a proxy) Supplementary documentation: e.g. workflows links to examples
  23. 23. Prototypes (make) Planning & managing tasks Documentation (share & comment) Designs (share & comment) Other files (share)
  24. 24. Axure JIRA gDocs InVision Prototypes (make) Planning & managing tasks Documentation (share & comment) Designs (share & comment) Other files (share) gDrive
  25. 25. Prototypes (make) Planning & managing tasks Documentation (share & comment) Designs (share & comment) Other files (share) JIRA Axure gDocs InVision gDrive source of truth
  26. 26. Step 3: Learn the design critique
  27. 27. Seeing UX deliverable
  28. 28. Seeing UX deliverable Got comments?
  29. 29. Seeing UX deliverable Got comments? No Think again
  30. 30. Seeing UX deliverable Got comments? Is the timing right? No Think again
  31. 31. Seeing UX deliverable Got comments? Is the timing right? Design comment Refer to: consistency, flow, proportions, colors, UI patterns … or just say it looks weird No Think again
  32. 32. Seeing UX deliverable Got comments? Is the timing right? Design comment Implementation comment Use numbers: effort to implement, load time etc. Refer to: consistency, flow, proportions, colors, UI patterns … or just say it looks weird No Think again
  33. 33. P.S. A weird thing
  34. 34. Design enthusiast Hardcore developer
  35. 35. Design enthusiast Hardcore developer Beautiful code feed with raw meat requires detailed designs technology -centric
  36. 36. Design enthusiast Hardcore developer Beautiful code Beautiful UI feed with raw meat requires detailed designs technology -centric does not implement 1:1 wants to know users & business interested in design
  37. 37. Beautiful code Beautiful UI feed with raw meat requires detailed designs technology -centric does not implement 1:1 wants to know users & business interested in design Bad Good
  38. 38. GoodBad Beautiful code Beautiful UI does not implement 1:1 requires detailed designs technology -centric does not implement 1:1 wants to know users & business interested in design
  39. 39. Thank you! slideshare.net/nrozycka

×