Best Practice for UX Deliverables - 2014

Download Best Practice for UX Deliverables - 2014

Post on 27-Jan-2015




4 download




  • 1. Best practice for UX deliverables! !by Anna Dahlstrm |

2. My name is Anna and today were going to talk about: !How to adapt and sell your UX deliverable to thereader (from clients, your team, in house and outsourced developers) Guiding principles for creating good UX deliverables (both low and high fidelity) Best practice for presentations, personas, user journeys, flows, sitemaps, wireframes and other documents Simple, low effort but big impact tools for improving the visual presentation of your UX deliverables 3. Only joking. Thats not what this presentation will look likeHappy clown via Shutterstock 4. If it did, I wouldnt blame you if you looked like 5. What is so bad with this? 6. First of all, it makes you want to do 7. Its really hard to reado breathing spacing Lack of text indent & alignment Too much text 8. It contains unnecessary detailIts the class description word for wordIts most likely what Ill say anyway 9. It just doesnt sell itSeriously?! This will be 3 hours Ill never get back of my lifeBoring! This lady just doesnt careLazy!Im out of here 10. Today well look at... 1. A bit of background 2. Adapting to the reader, project & situation 3. Guiding principles with DOs & DONTs 4. Good examples 5. Practice x 4 6. Surgery + Q & ABreak 11. 2007 I started working agency side 12. Much faster pace than what I was used 13. From one to many clients & projects, at the same 14. From tax applications to campaigns & large website 15. Strategic thinking & communication +Selling my work became very important 16. Creative approach to UX deliverables +Open with less set templates 17. Many talented people 18. Creative, communicative, & visually pleasing documents were a breeze for 19. They made clients & internal people 20. For me... it took 21. Advancing my wireframing skills was 22. Less so with the strategic experience design 23. I had to find my own 24. Weekly one to ones 25. Critique, walk-throughs & tips was the best thing for my 26. That & experimenting until I found my 27. Since then Ive made clients & internal stakeholders & team members 28. Though thats not what its about, it was & continues to be one important 29. Championing IA & UX internally as well as with clients was a big part of my 30. It still is: the value of UX, collaboratively working & being involved from start to finish is not a given 31. Whoever our work is for, we always need to sell 32. How much we need to put into it How we need to sell it To whom we need to sell it !this all varies 33. Thats what were going to be working on 34. 2. Adapting to the reader, project & situation 35. Where we work Who the deliverable is for Why we do it How its going to be used !impacts how to approach it 36. I asked a few people in different roles what they considered key with good UX 37. You need to produce a deliverable that meets the needs of the audience it's intended for: wireframes that communicate to designers, copy writers and technical architects... Experience strategy documents that matter to digital marketeers... - John Gibbard Associate Planning Director 38. A good UX deliverable clearly communicates its purpose and what its trying to achieve. It anticipates any questions / scenarios which may be posed. ! - Nick Haley Head of User Experience Guardian News and 39. Its not something created for the sake of it. One of the reasons we dont do wireframes anymore is because of this. Instead my team creates html prototypes which live in a browser. I see developers refer to them all the time, without consulting the team. ! - Nick Haley Head of User Experience Guardian News and 40. One immediate conclusion can be 41. Client side is different from having clients 42. In the past Id look for reams of documents going into great detail, but as a result of the proliferation in devices creating documentation is becoming too cumbersome. There needs to be some initial though into journeys, personas and use cases for sure, but the need for wireframes I think is reduced to identify the priority of content/functionality. ! - Alex Matthews Head of Creative Technology BBH, London 43. Instead we should be wireframing in code using a responsive framework so that we can immediately see how everything looks on all devices, and rapidly change how an element and its associated behaviours looks across all these devices. ! - Alex Matthews Head of Creative Technology BBH, 44. Second conclusion: approaches & whats needed differ between 45. I asked Alex: Would you agree though that the above works a lot better if the teams are located together and work collaboratively, and that the need for actual wireframes with annotations increase, if the development happens elsewhere? 46. Yes totally agree 47. Third conclusion: what inhouse developers need is different from if the build is 48. UX should not be a hander over, it should be part of the full development cycle from product inception, through to the MVP and each iteration beyond. ! - Scott Byrne-Fraser Creative Director BBC User Experience & Design Sport & 49. However, sometimes we do need to hand things 50. Rule for my team: I dont care what you create or how you create it, but it better be high quality. !A deliverable which isnt used to move the project forward is a waste of time. ! - Nick Haley Head of User Experience Guardian News and 51. UX is about delivery, not deliverables. So the best design artefacts are the ones that take the least time to convey the most insight and meaning. Conversations are better than sketches, sketches are better than prototypes and prototypes are better than think specifications. So if you're focussing on making pretty deliverables, youre focussing on the wrong thing. ! - Andy Budd Co-founder & CEO Clearleft 52. That being said, there are VERY RARE occasions when creating a nice looking deliverable like a concept mapto explain a difficult concept around a large organisationcan pay dividends. But this is the exception rather than the rule. ! - Andy Budd Co-founder & CEO 53. Forth conclusion: its not about pretty documents, but about adding 54. Make them f ****** appropriate Practitioners love to pretend that they only need to fart/cough near a client and they understand whats inferred, but that's nonsense. The truth is you need to communicate to lots of different people at lots of different levels. Make sure your deliverables (at whatever fidelity) are appropriate for your audience. ! - Jonty Sharples Design Director Albion 55. As we know, not every client is the 56. From two dear ones, who have been both colleagues & 57. The best UX works collaboratively and considers the whole customer journey/experience as well as satisfying the business requirements in the context of the overall digital strategy. They produce clear and annotated customer journeys, sitemaps and detailed wireframes with complete user and functionality notes and rationale behind the proposed solution. ! - Stephanie Win-Hamer Proposition Manager Barclays 58. Good UX should demonstrate enough for stakeholders to understand the essential details, for developers to be able to build with minimum questions, and for other UX designers to pick up the project. The deliverable should not be in the form of long winded manuals, which often remain unread, and become time-consuming to maintain. ! - Scott Byrne-Fraser Creative Director BBC User Experience & Design Sport & Live 59. But, not every client is UX 60. UX is a critical part of any project but you'll often find that clients sometimes don't understand what they are looking at and/or are just itching to get to the "pretty pictures" bit. From my point of view therefore, it is vital that the UX is super clear, with detailed annotations and notes written in laymen's terms - and if it can be visually engaging to keep their attention, all the better. Personally I am a big fan of sketches, particularly in the early stages. - Hannah Hilbery Board Account Director Leo Burnett 61. On the subject of keeping peoples attention - a bit on building skills, presentations & showing 62. In building the skills of my team I'm looking for them to produce beautiful, usable deliverables that communicate their content appropriately in context. In practical terms I 'd also hope that they're editable and adaptable enough to evolve within and without the project. - John Gibbard Associate Planning Director 63. Presentations are for presenting, not reading. Read and adapt to the audience. When you see people who have written a speech word-for-word read it out, it never connects with the audience. Say less. People can take away (at best) 3 things from an hour long presentation. Make sure you focus so that the three things you want to be taken away are taken away. - Nick Emmel Strategic Partner Mr. President 64. Narrative is the key thing. A person needs to be able to tell a good story about their deliverables and why they made decisions, who they worked with along the way and how they were produced (and for whom). It's only really when people tell stories that people feel engaged and connected with how a UX practitioner practices. The ones that don't have narrative come across as samey, lumpy and can make you assume the practitioner lacks passion. Be Kaler Director Futureheads Recruitment 65. Speaking of storytelling, this is what visual design has to 66. A good piece of UX has a narrative and clearly tells a story, or at least part of a story on a particular journey. As a designer - everything I do and make is communicating something to someone. Therefore a critical deliverable to establish that principle are good personas. I need to understand who has to get what out of the thing I'm designing and I'm only satisfied a visual has been executed well once I'm confident it's telling the right story to the right person in the right way. - Steve Whittington Design Director Dare 67. Just as design shouldn't be paint by numbers, UX shouldn't be build by boxes. The boundaries between good content creation, well considered user experience and effective design and layout are blurred. I rmly believe that for one to be successful - all the disciplines need to sing together. Hence, the single most important deliverable isn't a physical one, rather a common understanding - a pool of knowledge developed when these key disciplines work together. - Steve Whittington Design Director Dare 68. So true, & so 69. Last but not least, we wouldnt have anything without 70. The best deliverables for a writer evidence a really close understanding of our content so that there's flexibility in wireframes for example, to fit more or less words. Components can be useful in this respect. There's nothing worse than having to fill space when there's nothing to say. I also find personas helpful for adjusting the copy in places, but only if they're sufficiently different from each other. - Emma Lawson Freelance Senior Copywriter & Former Head of Copy 71. 3. Guiding principles with DOs & DONTs 72. First THE 73. 01 Create something people want to readmake documents skimmable & easy to read remove fluff & get to the point pull out key points & actions add some delight to keep the reader engaged 74. Every reader has given you their time. Make the most of it & dont waste 75. 02Ensure the reader knows what they are looking at always include page titles use visual cues for what you reference in annotations pull out or highlight what has changed from prior 76. 03Make it easy to follow & understand a red thread is crucial & makes your work more engaging consistency in numbering & titles matters include page numbers, particularly if presenting over the 77. Though it (mostly) should be, it wont always be YOU presenting YOUR 78. 04 Make things reusable between projectsuse stencils & avoid continuously creating from scratch keep assets organised (icons, visual elements, assets for devices, social media etc.) spend some time setting up elements properly helps avoid having to go back & adjust every instance later set up document templates that can be reused all of the above saves time & ensures you spend yours 79. 05 Avoid unnecessary updates & maintenanceset up & automate document info (logos, page numbers, titles, version, file location, etc) if software allows, place them on a shared canvas/ layer ensures they are on every page & no manual update is needed use layers/ shared canvases for consistent elements & for keeping your document organised (great if someone else needs to pick it up) 80. 06Adapt to the reader, project & situation applies to verbal presentation & walkthrough as well as visual presentation & polish adjust your focus & detail - whats most important to 81. 07 Use a mixture of colours, white space, fonts & stylinghelps draw the users eye & guide the reader to what matters useful for grouping information adds delight & makes your documents a pleasure to the eye really simple & not takes very little 82. And THE 83. 01 Dont be lazycheck spelling ensure things are aligned include spacing always proof 84. 02Dont create unrealistic wireframes images tend to come in certain ratios typography needs to be big enough to read be true - making your wireframes bigger, or modules smaller wont make the content fit in real 85. 03Dont spend unnecessary time polishing work with simple tools to improve your documents spend your time where it adds the most value practice & re-use to save 86. 4. Good examples 87. Persona 88. Persona 89. Persona 90. Pen portrait 91. Pen portrait 92. More personas & pen portraits portada-DIY-personas.jpg 2012/12/involver_personas5.jpg 2013/05/OBC-personas.png 2013/03/personas-4.jpg 2012/06/social-media-personas-600x2223.jpg screen_02.jpg 93. Customer Experience Map 94. Customer Experience Map 95. Customer Experience Map 96. Customer Experience Map 97. More customer experience maps RailEurope_AdaptivePath_CXMap_FINAL.pdf time-line-exp-map-2.jpg saywomenjourneychart.jpg 98. Sketches 99. for sketching 100. User 101. User 102. Flow 103. Flow diagram 104. Flow diagram 105. More user journeys, flows & flow diagrams user-flow.jpg ! ! 106. Sitemaps 107. Sitemaps 108. Sitemaps 109. Sitemaps 110. More sitemaps attachments/121386 list=popular&offset=141 ! 111. Sketches + screen 112. Sketches & screen 113. Sketches & screen ow 114. More visual flows & story boards 2011/09/mobile-storyboard.jpg darwin/images/full232.jpg ! 115. Wireframes 116. Wireframes 117. Wireframes 118. 119. Wireframes 120. Wireframes 121. More wireframes list=popular&offset=180 evanswireframing/ 122. Practice time, but 123. 5 mins break 124. 5. Time to practice 125. Four exercises to work through individually (or in pairs if preferred)xxx 126. The BRIEF For summer a client has asked you to design & build an app around whats happening in London. Theyve shared target audience insight & requirements on what to include: About information Map of summer events Offers from stores List of events Latest news Login & registration Ability to share 127. 01 SKETCHING As a first draft to the client, sketch a few of the sections of the app & include key points on interactions, flow between screens & main points around your thinking. About information Map of summer events Offers from stores List of events Latest news Login & registration Ability to share 128. for sketching 129. 02 PEN PORTRAIT Congrats! The client loved it. The next task is to create a pen portrait summarising who this is for & what we need to know about them, as well as what captures who they are. Tourist, German, [xx] years old, [gender] Interested in markets, concerts, likes Uses iPhone, also has a tablet First time in London Novice iPhone user Skeptical to sharing information 130. Persona 131. Pen portrait 132. Pen portrait 133. 5 mins break 134. 03 WIREFRAME Bad news. An external company will build the app. Based on your sketches do a wireframe on your computer of the home screen. Make sure the following is clear to the reader: Which screen they are looking at What this view does - purpose, goals Whats the content on the screen Where does interactions take the !How do interactions work Any key considerations...and that it looks somewhat decent 135. Wireframes 136. Wireframes 137. 04 PRESENTATION This is the big one, selling it to the stakeholders. The client wants you to do an executive summary that you will be presenting, but can also be passed around. It should include: The Brief The process Who the target audience is The consider... It needs to sell Be clear & concise Focus on key take aways 138. 3things 139. 01 Presentations are for presenting, not reading. If the information that you want to put across requires detailed paragraphs or chunky tables for analysis, or swirly complex user journeys - deliver the information in a different way. - Nick Emmel Strategic Partner Mr. 140. 02 ! ! Read and adapt to the audience. When you see people who have written a speech word-for-word read it out, it never connects with the audience. That's not because the material is bad, it is because it is not being constantly adapted to the ever-changing context, mood, or understanding. Stand-up comedians are great presenters as they adapt and draw in their audience. Nick Emmel Strategic Partner 141. 03 ! ! Say less. When you are given a stage to show-off your knowledge, the temptation is to waffle, digress or delve far too deep into topics. People can take away (at best) 3 things from an hour long presentation. Make sure you focus so that the three things you want to be taken away are taken away. - Nick Emmel Strategic Partner Mr. 142. 6. Surgery + Q&A 143. Any questions? 144. Any work you would like to get feedback on? 145. If so this applies, please 146. A few final 147. Approach, tools & delity depends on your project, budget and time 148. BrandHigh levelLess formal UX deliverables but more creatively ledSource: Mark Bell, DareAim of experienceInfo or taskIA & UX deliverablesDetailedUX led with more formal & extensive IA & UX deliverables 149. It also depends on the skills & experiences of your 150. High levelIA & UX deliverablesLess formal UX deliverables but more creatively ledExtensiveSource: Mark Bell, DareDetailedUX led with more formal & extensive IA & UX deliverablesExperience in visual design teamLimited 151. And if its being built externally or 152. BrandHigh levelAim of experienceInfo or taskIA & UX deliverablesDetailedLess formal UX deliverables but more creatively ledExtensiveSource: Mark Bell, DareUX led with more formal & extensive IA & UX deliverablesExperience in visual design teamLimited 153. If clients (or someone else) dont get it, there is generally something to be improved in how we work with them & present our 154. No right way. No wrong way. 155. As long as you add 156. Remember, this is how I started 157. Learn from others & stick to the DOs & 158. Fonts & colours go a long way. 159. And have fun, it will come acrossHappy clown via Shutterstock 160. Thank you @annadahlstrom |