best practice for ux deliverables - 2014

Download Best Practice for UX Deliverables - 2014

Post on 27-Jan-2015




4 download

Embed Size (px)




  • 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 "prett