Your SlideShare is downloading. ×
User experience Design<br />
Have you been here?<br />
And here?<br />
Have you been here?<br />
And here?<br />
Have you used these?<br />
And this?<br />‘96<br />‘09<br />
Why they succeed where others fail?<br />Domain brilliance ?<br />Innovation drive ?<br />Marketing strategy ?<br />User E...
Hard lessons learnt?<br />
So, what is User Experience?<br />n. the holistic experience and satisfaction aenduserhas when using a product or system<b...
User Experience is multi-dimensional<br />Can I trust what I see and what<br />I do on the interface?<br />Can I do the ta...
In SDLC however, User Experience is also multi-disciplinary<br />User Research ( type of users, their goals and needs )<br...
How do designers work?<br />UsbTest<br />UXD Prototype<br />Define and Design<br />Discover<br />Phase<br /><ul><li>Consol...
Present finding to stakeholders
Define Scope for design
Prepare Personas
Role Play
Card Sorting. Design IA & Navigation Concepts.
Paper Prototypes
Design sample wire frame / screen to depict the same
Sign Off on Design Concepts/approach
Develop key screen based on scenarios identified
Development team to prototype the scenarios
Design Visual Design and UI assets ( icons, etc) for ’to-be’ environment
Documents the approved design in the form of a UI Design Style Guide
Usability Testing
Incorporate Feedback
Iterate Test
Understand Application and the client environment.
Investigate the User-Tasks-Profile
Upcoming SlideShare
Loading in...5
×

The User Experience Designer

1,917

Published on

A brief look at UX Design and the Designer along with.

Published in: Design

Transcript of "The User Experience Designer"

  1. 1. User experience Design<br />
  2. 2. Have you been here?<br />
  3. 3. And here?<br />
  4. 4. Have you been here?<br />
  5. 5. And here?<br />
  6. 6. Have you used these?<br />
  7. 7. And this?<br />‘96<br />‘09<br />
  8. 8. Why they succeed where others fail?<br />Domain brilliance ?<br />Innovation drive ?<br />Marketing strategy ?<br />User Experience<br />Define the primary goal of the user-<br />The user is here to search, let him do that first! Excellent page ranking for the most <br />Relevant search results no matter what profile is searching it <br />or<br />The user is hungry, feed his fast, feed him good & smile!<br />Put marketing and technology gimmicks/limitations way over users needs<br />Google continuously refuses to place banner ads or introduce pop-ups on its<br />Interfaces<br />or<br />We may not have the best seating arrangement, but we do serve fast and we<br />Do serve it hot!<br />A satisfied customer always returns!<br />
  9. 9. Hard lessons learnt?<br />
  10. 10. So, what is User Experience?<br />n. the holistic experience and satisfaction aenduserhas when using a product or system<br />...driven by consideration of the ‘moments’ of engagement between people and brands, and the memories these moments create.<br />
  11. 11. User Experience is multi-dimensional<br />Can I trust what I see and what<br />I do on the interface?<br />Can I do the task <br />I intend to complete?<br /> Trust<br /> Useful<br /> Value<br /> Desire<br /> Usability<br />Can I do the task <br />Easily ?<br />Is it accessible?<br />Is it findable?<br />Value of image, brand & <br />identity?<br />Value: Contribute to the overall user’s satisfaction on functional and emotional needs<br />
  12. 12. In SDLC however, User Experience is also multi-disciplinary<br />User Research ( type of users, their goals and needs )<br />Usability Testing ( test when possible, test frequent)<br />Information Architecture ( detailed site map of the system )<br />Interaction Design (follow all good usability principles | Innovate!)<br />Information Design ( accurate, contextual and effective information )<br />Accessibility( usable by the physically challenged-sight, sound, speech, muscle )<br />Visual Design ( font type, layout, color, trust & desire, brand appeal )<br />Server logs/web analytics ( technical analysis, check results )<br />
  13. 13. How do designers work?<br />UsbTest<br />UXD Prototype<br />Define and Design<br />Discover<br />Phase<br /><ul><li>Consolidate findings through interviews and questionnaire
  14. 14. Present finding to stakeholders
  15. 15. Define Scope for design
  16. 16. Prepare Personas
  17. 17. Role Play
  18. 18. Card Sorting. Design IA & Navigation Concepts.
  19. 19. Paper Prototypes
  20. 20. Design sample wire frame / screen to depict the same
  21. 21. Sign Off on Design Concepts/approach
  22. 22. Develop key screen based on scenarios identified
  23. 23. Development team to prototype the scenarios
  24. 24. Design Visual Design and UI assets ( icons, etc) for ’to-be’ environment
  25. 25. Documents the approved design in the form of a UI Design Style Guide
  26. 26. Usability Testing
  27. 27. Incorporate Feedback
  28. 28. Iterate Test
  29. 29. Understand Application and the client environment.
  30. 30. Investigate the User-Tasks-Profile
  31. 31. Identify preliminary User Experience Issues through heuristics evaluation
  32. 32. Interview Users in their own environment</li></ul>Activities<br />Quick Start/Project Inception<br />Iteration Cycles<br />
  33. 33. The UX team at your company should be<br />Or a combination of <br />These profiles:<br /><ul><li>User Researcher
  34. 34. UI Designer
  35. 35. Visual Designer
  36. 36. UI Developer
  37. 37. Usability Tester</li></li></ul><li>Having the designer on board<br />
  38. 38. The UXD<br /><ul><li>We need some “Wireframes” done. </li></ul> Can you join our team?<br /><ul><li>We need you to make this look good?</li></ul> Can you join our team?<br /><ul><li>At release: </li></ul> Can you test our application?<br />Right needs; wrong approach<br />
  39. 39. The reason you need an UXD<br />You are NOT designing for your client!<br />
  40. 40. The reason you need an UXD<br />Happy End Users!<br />=<br />(Who have finished their tasks with ease)<br />More Sales: More Profits<br />Less Time lost: More Productivity<br />More Utilization<br />Better Competition: Better Brand Value<br />=<br />Happy Customer <br />=<br />More Business opportunities<br />More satisfaction at delivering value &<br />Not just software: It’s a relationship<br />
  41. 41. The reason you need an UXD<br />Involve designers right from the START!<br />
  42. 42. The reason you need an UXD<br />Pre-Sales<br /><ul><li>Designer to help you understand the</li></ul> Client’s competition better.<br /><ul><li>Do COMPETITIVE BENCHMARKING on UX!</li></ul>The better you understand the business & the competition <br />for the client, the more they will trust you to deliver what <br />your recommend & is required.<br />
  43. 43. The reason you need an UXD<br />Pre-Sales<br /><ul><li>Designer to help you review what’s wrong </li></ul> with the client’s application<br /><ul><li>Arm your sales pitch with a </li></ul>USABILITY REPORT!<br />The better you understand the application and what’s wrong<br />with it, the more the client will trust you to deliver what’s right.<br />
  44. 44. The reason you need an UXD<br />Project Inceptions<br /><ul><li>Designer to help you realize a broader </li></ul> vision, a digital strategy for your product<br /><ul><li>CONCEPTUALIZE! A unique User Experience</li></ul>Work WITH and NOT FOR the client as a team. Make the <br />Product your own. Be responsible for the value you bring.<br />
  45. 45. The reason you need an UXD<br />Project In progress<br /><ul><li>Designer to help you mock the vision </li></ul> on paper or board or prototype<br /><ul><li>VIEW and take FEEDBACK on the screens</li></ul> you design for the End User!<br />Involve the End Users of the application in the process. <br />Theyare the ones you are doing this all for.<br />
  46. 46. The reason you need an UXD<br />Project In progress<br /><ul><li>Designer to help you put the vision on paper
  47. 47. ITERATE! Chart the flows! ESTIMATE!</li></ul>Iterate on feedback. Understand what the screens mean <br />from a technical point of view. <br />
  48. 48. The reason you need an UXD<br />Project In progress<br /><ul><li>Designer to help you find alternatives
  49. 49. PAIR PROGRAM with a designer on the</li></ul> table!<br />Seek alternatives to difficult and laborious UI designs. <br />Collaborate and Brainstorm to find quick alternatives.<br />
  50. 50. The reason you need an UXD<br />Project In progress<br /><ul><li>Designer to help you Test & Ok quickly
  51. 51. QA through a designer when your story is</li></ul> complete<br />Catch issues before even the clients test out the story/build.<br />
  52. 52. The reason you need an UXD<br />Project Release ‘n’<br /><ul><li>Designer to help you Test for Usability
  53. 53. USABILITY TEST your release with the </li></ul> end users<br />Make sure you put that feedback back into the story loop<br />based on priority.<br />
  54. 54. The reason you need an UXD<br />Final Release<br /><ul><li>Designer to help you Capture Metrics
  55. 55. ROI analysis </li></ul>Capture the value add to the business. Capture the ROI on<br />Usability. Translate that to money invested and return gained.<br />Know YOUR value.<br />
  56. 56. Questions ?<br />
  57. 57. Manish Govind Pillewar<br />Sr. Consultant | User Experience Design<br />San Francisco, CA-94104<br />manishpi@gmail.com<br />Skype: manishpi<br /># Images picked up from Google Search and need due credit<br />

×