Best Practice for UX Deliverables

Download Best Practice for UX Deliverables

Post on 18-Oct-2014




10 download

Embed Size (px)




<p></p> <p>B!"# pr$%#&amp;%! for UX deliverablesby Anna Dahlstrm | @annadahlstrom</p> <p>My name is Anna and today were going to talk about:How to adapt and sell your UX deliverable to the reader (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 documentsSimple, low effort but big impact tools for improving the visual presentation of your UX deliverables</p> <p>O'() joking, thats not what this presentation will look like</p> <p></p> <p>If *&amp;*, I wouldnt blame you if you looked like this</p> <p></p> <p>W+$# is so bad with this?</p> <p></p> <p>,r"# -f $((, it makes youwant to do this</p> <p>I#" really hard to read</p> <p>N- br!$#+&amp;'. "p$%&amp;'.</p> <p>T-- /0%+ #1#</p> <p>L$%2 -f #1# &amp;'*!'# &amp; </p> <p>$(&amp;.'/!'#</p> <p>I# %-'#$&amp;'"unnecessary detail</p> <p>I#" #+! %($"" *!"%r&amp;p#&amp;-' w-r* f-r w-r*</p> <p>I#" /3# (&amp;2!() w+$# I(( "$) $')w$)</p> <p>I# 40"#doesnt sell it</p> <p>S!r&amp;-0"()?!</p> <p>L5)!6&amp;" ($*) 40"# *-!"'# %$r!</p> <p>6&amp;" w&amp;(( b! 3 +-0r" I(( '!v!r .!# b$%2 -f /) (&amp;f!</p> <p>I/ -0# -f +!r!</p> <p>B-r&amp;'.!</p> <p>T-*$) w!(( (--2 $#...1. A bit of background</p> <p>2. Adapting to the reader, project &amp; situation</p> <p>3. Guiding principles with DOs &amp; DONTs</p> <p>4. Good examples</p> <p>5. Practice x 4</p> <p>6. Surgery + Q &amp; A</p> <p>Br!$2</p> <p>2007 I started working agency side</p> <p></p> <p>M0%+ faster pace than what I was used to</p> <p></p> <p>Fr-/ -'! to many clients &amp; projects, at the same time</p> <p>Fr-/ #7 applications to campaigns &amp; large website redesigns</p> <p></p> <p>S#r$#!.&amp;% thinking &amp; communication </p> <p>S!((&amp;'. my work became very important</p> <p>+</p> <p>Cr!$#&amp;v! approach to UX deliverables</p> <p>Op!' with less set templates</p> <p>+</p> <p>M$') talented people </p> <p></p> <p>Cr!$#&amp;v!, communicative, &amp; visually pleasing documents were a breeze for them</p> <p></p> <p>6!) /$*! clients &amp; internal people smile</p> <p></p> <p>F-r /!... it took time</p> <p></p> <p>A*v$'%&amp;'. my wireframing skills was easy</p> <p></p> <p>L!"" "- with the strategic experience design documents</p> <p></p> <p>I +$* #- find my own style</p> <p>W!!2() one to ones </p> <p></p> <p>Cr&amp;q0!, w$(2-#+r-0.+" &amp; #&amp;p" was the best thing for my development</p> <p></p> <p>6$# &amp; 1p!r&amp;/!'#&amp;'.until I found my style</p> <p></p> <p>S&amp;'%! #+!' Ive made clients &amp; internal stakeholders &amp; team members smile</p> <p></p> <p>6-0.+ thats not what its about, it was &amp; continues to be one important aspect</p> <p></p> <p>C+$/p&amp;-'&amp;'. IA &amp; UX internally as well as with clients was a big part of my job</p> <p>I# "#&amp;(( &amp;": the value of UX, collaboratively working &amp; being involved from start to finish is not a given everywhere</p> <p></p> <p></p> <p>W+-!v!r our work is for, we always need to sell it</p> <p>H-w /0%+ we need to put into itH-w we need to sell it T- w+-/ we need to sell it</p> <p>this all varies</p> <p></p> <p>6$#" w+$# were going to be working on today</p> <p>2. A*$p#&amp;'. to the reader, project &amp; situation</p> <p>W+!r! we workW+- the deliverable is for W+) we do itH-w its going to be used</p> <p>impacts how to approach it</p> <p></p> <p>I $"2!* a few peoplein different roles what they considered key with good UX deliverables</p> <p></p> <p> Y-0 '!!* #- 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... </p> <p>- J-+' G&amp;bb$r*Associate Planning Director</p> <p>Dare</p> <p></p> <p> A .--* UX *!(&amp;v!r$b(! clearly communicates its purpose and what its trying to achieve. It anticipates any questions / scenarios which may be posed. </p> <p>- N&amp;%2 H$(!)Head of User Experience</p> <p>Guardian News and Media</p> <p></p> <p> I#" '-# "-/!#+&amp;'. 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. </p> <p>- N&amp;%2 H$(!)Head of User Experience</p> <p>Guardian News and Media</p> <p></p> <p>O'! immediate conclusion can be made</p> <p>C(&amp;!'# "&amp;*! is different from +$v&amp;'. %(&amp;!'#"</p> <p></p> <p> I' #+! p$"# 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. </p> <p>6!r! '!!*" #- b! 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. </p> <p>- A(1 M$##+!w"Head of Creative Technology</p> <p>BBH, London</p> <p></p> <p> I'"#!$* w! "+-0(* 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. </p> <p>- A(1 M$##+!w"Head of Creative Technology</p> <p>BBH, London</p> <p></p> <p>S!%-'* %-'%(0"&amp;-': approaches &amp; whats needed differ between companies</p> <p></p> <p>I $"2!* A(1: 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?</p> <p>Y!" totally agree</p> <p></p> <p>6&amp;r* %-'%(0"&amp;-': what inhouse developers need is different from if the build is outsourced</p> <p></p> <p> UX "+-0(* '-# be a hander over, it should be part of the full development cycle from product inception, through to the MVP and each iteration beyond. </p> <p>- S%-## B)r'!-Fr$"!rCreative Director</p> <p>BBC User Experience &amp; DesignSport &amp; Live</p> <p></p> <p>H-w!v!r, sometimes we do need to hand things over</p> <p></p> <p> R0(! f-r /) #!$/: I dont care what you create or how you create it, but it better be high quality.</p> <p>A deliverable which isnt used to move the project forward is a waste of time. </p> <p>- N&amp;%2 H$(!)Head of User Experience</p> <p>Guardian News and Media</p> <p></p> <p> UX &amp;" $b-0# *!(&amp;v!r), not deliverables. So the best design artefacts are the ones that take the least time to convey the most insight and meaning.</p> <p>Conversations are better than sketches, sketches are better than prototypes and prototypes are better than think specifications. </p> <p>S- &amp;f )-0'r! f-%0""&amp;'. -' making pretty deliverables, you're focussing on the wrong thing. </p> <p>- A'*) B0**Co-founder &amp; CEO</p> <p>Clearleft</p> <p></p> <p> 6$# b!&amp;'. "$&amp;*, 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. </p> <p>- A'*) B0**Co-founder &amp; CEO</p> <p>Clearleft</p> <p></p> <p>F-r#+ %-'%(0"&amp;-': its not about pretty documents, but about adding value</p> <p></p> <p> M$2! #+!/ f ****** $ppr-pr&amp;$#!Practitioners love to pretend that they only need to fart/cough near a client and they understand whats inferred, but that's nonsense. </p> <p>6! #r0#+ &amp;" 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. </p> <p>- J-'#) S+$rp(!"Design Director</p> <p>Albion</p> <p></p> <p>A" w! 2'-w, not every client is the same</p> <p></p> <p>Fr-/ #w- *!$r -'!", who have been both colleagues &amp; clients</p> <p></p> <p> 6! b!"# UX w-r2" collaboratively and considers the whole customer journey/experience as well as satisfying the business requirements in the context of the overall digital strategy.</p> <p>6!) pr-*0%! clear and annotated customer journeys, sitemaps and detailed wireframes with complete user and functionality notes and rationale behind the proposed solution. </p> <p>- S#!p+$'&amp;! W&amp;'-H$/!rProposition Manager</p> <p>Barclays</p> <p></p> <p> G--* 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.</p> <p>The deliverable "+-0(* '-# b! in the form of long winded manuals, which often remain unread, and become time-consuming to maintain. </p> <p>- S%-## B)r'!-Fr$"!rCreative Director</p> <p>BBC User Experience &amp; DesignSport &amp; Live</p> <p></p> <p>B0#, not every client is UX minded</p> <p></p> <p> UX &amp;" $ %r&amp;%$( p$r# 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. </p> <p>From my point of view therefore, &amp;" v$( 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. </p> <p>- H$''$+ H&amp;(b!r)Board Account Director</p> <p>Leo Burnett</p> <p></p> <p>O' #+! "0b4!%# -f keeping peoples attention - a bit on building skills, presentations &amp; showing work</p> <p></p> <p> I' b0&amp;(*&amp;'. #+! "2&amp;((" -f /) #!$/ 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. </p> <p>- J-+' G&amp;bb$r*Associate Planning Director</p> <p>Dare</p> <p></p> <p> Pr!"!'#$#&amp;-'" $r! f-r pr!"!'#&amp;'., not reading.R!$* $'* $*$p# #- #+! $0*&amp;!'%!. When you see people who have written a speech word-for-word read it out, it never connects with the audience.</p> <p>S$) (!"". 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. </p> <p>- N&amp;%2 E//!(Strategic Partner</p> <p>Mr. President</p> <p></p> <p> N$rr$#&amp;v! &amp;" #+! 2!) #+&amp;'.. 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).</p> <p>I#'" -'() r!$(() when people tell stories that people feel engaged and connected with how a UX practitioner practices.</p> <p>6! -'!" #+$# *-''# +$v! '$rr$#&amp;v! come across as samey, lumpy and can make you assume the practitioner lacks passion. </p> <p>- B! K$(!rDirector</p> <p>Futureheads Recruitment </p> <p></p> <p>Sp!$2&amp;'. -f storytelling, this is what visual design has to say</p> <p></p> <p> A .--* p&amp;!%! -f 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 '!!* #- 0'*!r"#$'* 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. </p> <p>- S#!v! W+#&amp;'.#-'Design Director </p> <p>Dare</p> <p></p> <p> J0"# $" *!"&amp;.' 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.</p> <p> I 8r/() b!(&amp;!v! 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. </p> <p>- S#!v! W+#&amp;'.#-'Design Director </p> <p>Dare</p> <p></p> <p>S- #r0!, &amp; so important</p> <p></p> <p>L$"# b0# '-# (!$"#, we wouldnt have anything without content</p> <p></p> <p> 6! b!"# *!(&amp;v!r$b(!" 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. </p> <p>6!r!'" '-#+&amp;'. w-r"! 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. </p> <p>- E//$ L$w"-'Freelance Senior Copywriter </p> <p>&amp; Former Head of Copy</p> <p>3. G0&amp;*&amp;'. principles with DOs &amp; DONTs</p> <p></p> <p>,r"# THE DOs</p> <p> make documents skimmable &amp; easy to read remove fluff &amp; get to the point pull out key points &amp; actions add some delight to keep the reader engaged</p> <p>01 Create something people want to read</p> <p></p> <p>Ev!r) r!$*!r has given you their time. Make the most of it &amp; dont waste it</p> <p></p> <p> always include page titles use visual cues for what you reference in annotations pull out or highlight what has changed from prior version</p> <p>02 Ensure the reader knows what they are looking at </p> <p></p> <p> a red thread is crucial &amp; makes your work more engaging consistency in numbering &amp; titles matters include page numbers, particularly if presenting over the </p> <p>phone</p> <p>03 Make it easy to follow &amp; understand </p> <p></p> <p>6-0.+ it (mostly) should be, it wont always be YOU presenting YOUR work</p>...