Visualising the User Experience

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

2 comments

Comments 1 - 2 of 2 previous next Post a comment

  • + grantrobinson Grant Robinson 1 month ago
    Hi Ayush. The amount of documentation needed really depends on the complexities of the project and the needs of your team. Usually you’ll need to document your findings from paper prototyping in the form of wireframes (or screenflows) so you can flesh out detail, share them with your team and stakeholders, get sign-off and eventually hand over for dev.
  • + ayushsaran Ayush Saran 1 month ago
    How much written up documentation would you include with those paper prototypes?
    and would you say they need more or less documentation than html wireframes ?
Post a comment
Embed Video
Edit your comment Cancel

50 Favorites & 1 Group

Visualising the User Experience - Presentation Transcript

  1. Visualising the User Experience Grant Robinson Senior Interaction Designer at Xero grant@xero.com
  2. Let’s talk about... 1. Rapid prototyping 2. Visualising the UX with screenflows Movement and transitions
  3. Rapid prototyping
  4. Is this rapid prototyping?
  5. Is this rapid prototyping? Nope!
  6. What is rapid prototyping?
  7. What is rapid prototyping? • User-centered design methodology
  8. What is rapid prototyping? • User-centered design methodology • For designing, communicating and evaluating user interfaces
  9. What is rapid prototyping? • User-centered design methodology • For designing, communicating and evaluating user interfaces • Getting feedback as early as possible
  10. What is rapid prototyping? • User-centered design methodology • For designing, communicating and evaluating user interfaces • Getting feedback as early as possible • Fast
  11. Prototyping life-cycle
  12. Prototyping life-cycle The more cycles the better
  13. Agile development mantra: release early, release often
  14. Agile design mantra: fail early, fail often "If you’re not failing now and again, it’s a sure sign you’re not doing anything very innovative." Woody Allen
  15. No designer is an island 1. Fellow designers 2. Project team 3. Wider team 4. Users
  16. Common techniques • Paper prototyping • Wireframes and page schematics • HTML wireframes • Interactive prototypes
  17. Paper prototypes...
  18. Paper prototypes Love: • Quick & dirty • No software needed • Very inclusive Hate: • Not quick enough • Too dirty (lack context & scale) • Hard to share amongst team • Still needs a separate documentation step
  19. Wireframes & page schematics...
  20. http://gapingvoid.com/2007/05/15/random-thought/
  21. Wireframes Love: • Good for defining content • Good for documenting screens Hate: • Bad at showing interactivity / flow • Can’t really use them for testing • Slow. Too much time spent describing.
  22. HTML wireframes...
  23. • Better success rate • Much faster • Less confusion
  24. HTML wireframes Love: • Can show interactivity / flow • Good for simple interaction (links, buttons etc) • Experienced in the browser (correct context & scale) Hate: • HTML, CSS (and JS) knowledge necessary • Time wasted on hacking layout & advanced functionality
  25. Other interactive prototypes...
  26. Axure (www.axure.com)
  27. Axure (www.axure.com)
  28. SketchFlow (www.microsoft.com/expression)
  29. Other interactive prototypes Love: • Good for testing moderately complex interactions • Some support collecting feedback • Some can generate specs Hate: • Difficult to get custom interactions working • Can require expertise in proprietary languages • Often not cross-platform (no love for Mac users) • Often low-fidelity only
  30. Choosing a prototype technique What a dilemma!
  31. Visualising the UX with screenflows
  32. http://gapingvoid.com/2007/05/15/random-thought/
  33. So how do we describe what users do? Visualise the experience... • Show every step to complete a task • Show every click • Preview the experience - see and feel how everything flows together
  34. It’s like stop motion
  35. From low to high fidelity
  36. • 32 iterations • 5 released
  37. Using Flash as a design tool {eh, what?}
  38. Flash: Not just a development tool
  39. Flash: Not just for video
  40. Flash: History in drawing & animation
  41. FutureSplash Animator
  42. FutureSplash Animator
  43. Anatomy of a screenflow
  44. Screenflows
  45. Screenflows • Perfect fit for agile teams
  46. Screenflows • Perfect fit for agile teams • Very effective communication tool
  47. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate
  48. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time
  49. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser.
  50. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser. • Obvious focus & limits
  51. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser. • Obvious focus & limits • Significantly reduces documentation
  52. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser. • Obvious focus & limits • Significantly reduces documentation • Support low to high fidelity
  53. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser. • Obvious focus & limits • Significantly reduces documentation • Support low to high fidelity • No coding necessary
  54. Screenflows • Perfect fit for agile teams • Very effective communication tool • Easy to evaluate • Ideal for explaining changes over time • Easy to share. Experienced in the browser. • Obvious focus & limits • Significantly reduces documentation • Support low to high fidelity • No coding necessary
  55. Getting serious about movement & transitions
  56. How did this...
  57. ...become this?
  58. ...become this?
  59. How did this...
  60. ...become this?
  61. How did this...
  62. ...become this?
  63. "Unless you can show me where you've fleshed out the character and aspects of the transitions at the same level of thought, rational, exploration and fidelity as you have the states - you're fired." Bill Buxton HCI pioneer Currently Principal Researcher, Microsoft Research
  64. Movement: the new affordance • Use movement to orientate user and keep them in flow • Explain changes/transformations • Use physical metaphors to describe the action: zoom, slide, reveal • Not just for fun: Research on the importance
  65. Yahoo Design Pattern Library http://developer.yahoo.com/ypatterns/richinteraction/transition/
  66. Yahoo Design Pattern Library http://developer.yahoo.com/ypatterns/richinteraction/transition/
  67. Transitions decreased task completion times Reduced error rates for reading tasks 0.3 seconds - optimal transition speed
  68. Some takeaways... {nom nom nom}
  69. The timeline is your friend
  70. The timeline is your friend • Efficient digital sketching tool
  71. The timeline is your friend • Efficient digital sketching tool • Best way to manage changes over time
  72. The timeline is your friend • Efficient digital sketching tool • Best way to manage changes over time • Supports low to high fidelity
  73. The timeline is your friend • Efficient digital sketching tool • Best way to manage changes over time • Supports low to high fidelity • Natural starting point for exploring
  74. Visualising the experience makes you a better
  75. Visualising the experience makes you a better • Puts you in the user’s shoes
  76. Visualising the experience makes you a better • Puts you in the user’s shoes • Keeps you focussed on user flow
  77. Visualising the experience makes you a better • Puts you in the user’s shoes • Keeps you focussed on user flow • Best way to communicate your designs to team and stakeholders
  78. Visualising the experience makes you a better • Puts you in the user’s shoes • Keeps you focussed on user flow • Best way to communicate your designs to team and stakeholders • Cuts documentation in half. Less time describing = more time designing
  79. Any questions? Please feel free to flick me an email: grant@xero.com Photo credits: http://www.flickr.com/photos/editor/3370897686/ http://www.flickr.com/photos/fuyoh/748118128/ http://www.flickr.com/photos/celloc/3145987130/ 3777808203/ http://www.flickr.com/photos/eraphernalia_vintage/ http://www.flickr.com/photos/rcourtie/3500123702/ http://www.flickr.com/photos/rcourtie/3500124362/ 21218849@N03/3902295700/ http://www.flickr.com/photos/ http://www.flickr.com/photos/ 21218849@N03/3901459255/ 21218849@N03/3902296466/ http://www.flickr.com/photos/ 21218849@N03/3901509379/ http://www.flickr.com/photos/

+ Grant RobinsonGrant Robinson, 1 month ago

custom

1802 views, 50 favs, 3 embeds more stats

Slides from a talk I did at Web Directions South in more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 1802
    • 1677 on SlideShare
    • 125 from embeds
  • Comments 2
  • Favorites 50
  • Downloads 0
Most viewed embeds
  • 122 views on http://www.webdirections.org
  • 2 views on http://plasticabilinguegarrucha.blogspot.com
  • 1 views on http://www.slideshare.net

more

All embeds
  • 122 views on http://www.webdirections.org
  • 2 views on http://plasticabilinguegarrucha.blogspot.com
  • 1 views on http://www.slideshare.net

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Groups / Events