Your SlideShare is downloading. ×
0
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Hybrid User Interviews
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Hybrid User Interviews

5,496

Published on

Lane describes how some traditional user interview methods can be adapted to be more quick, visual, collaborative and continuous. …

Lane describes how some traditional user interview methods can be adapted to be more quick, visual, collaborative and continuous.

Presented at the Balanced Team Conference, San Francisco, September 25, 2011
See http://www.balancedteam.org/balconf-2011-resources/ for more information.

0 Comments
10 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,496
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
10
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Many of the methods we use have their origins in enterprise practicesMaking software products was HARDLong planning cycles, silos, heavy documentation, handoffs
  • We got a lot of our methods (and neuroses) from working in this way.Designers learned to work separately and communicate with deliverables
  • http://luxr.co/lean-ux/9-principles-for-lean-ux/This is the UX analog to Lean Startup’s “build-measure-learn” feedback loop. Designers prefer to start with “think” rather than “make”, but the process is the same. UX people start with research that’s equivalent to the customer development interview. The innovation with Lean UX is that we choose lightweight research methods, move on quickly to make a small prototype that will prove out the riskiest concepts, and then validate that through some sort of real-world test. The most important success metric for any startup is the time it takes to move through the think-make-check (or Build-Measure-Learn) cycle
  • Working with lean startups, I’ve learned to beQUICK – MINUTES or HOURS not days or weeksCOLLABORATIVE – working WITH other people, not just PRESENTING to themVISUAL – using pen and paper and tape and stickies, putting things on the wall and talking about them as a groupCONTINUOUS – done often, with continuous improvement
  • Working with lean startups, I’ve learned to beQUICK – MINUTES or HOURS not days or weeksCOLLABORATIVE – working WITH other people, not just PRESENTING to themVISUAL – using pen and paper and tape and stickies, putting things on the wall and talking about them as a groupCONTINUOUS – done often, with continuous improvement
  • Thank you very much!If you want to keep in touch, you can follow me on twitter as “thinknow”
  • Transcript

    1. Hybrid* user interviews<br />Balanced Team Conference<br />September 25, 2011<br />*as in “something thatispoweredbymorethan one source of power”<br />
    2. 1<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> The origin of software development<br />
    3. 2<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Old-skool software development process<br />PLAN – BUILD – TEST – SHIP – T-SHIRT <br />
    4. 3<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Design tried to fit in<br />PLAN – BUILD – TEST – SHIP – T-SHIRT <br />^<br />RESEARCH – DESIGN<br />
    5. 4<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> And then, everything changed<br />Technology is no longer the problem<br />Product decisions are design decisions<br />Continuous customer engagement matters<br />
    6. 5<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Collaborative, multi-functional teams<br />
    7. 6<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Lean UX feedback loop<br />THINK<br />MAKE<br />CHECK<br />
    8. 7<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Design is a core team competency, not a role<br />Designer as coach/facilitator<br />Designer as product steward<br />Design studio/charrette<br />Design patterns/style guides<br />
    9. Quick<br />Visual<br />Collaborative<br />Continuous<br />8<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Successful design methods are<br />
    10. 9<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Collaborative interview planning<br />Team discusses what they want to learn<br />Prepare interview “guide”<br />Practice asking questions, listening<br />
    11. 10<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Collaborative interview planning<br />
    12. 11<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Interview guides<br />
    13. 12<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Provisional personas<br />Declare who we think the “customer” is<br />Shared visual artifact<br />Evolve over time<br />
    14. 13<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Provisional personas before interviews<br />
    15. 14<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Provisional personas after some interviews<br />
    16. 15<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Team interviewing<br />Pair interviewing (lead/backup)<br />Multiple note-takers<br />Group synthesis<br />Visual radiators and sketchboards<br />
    17. 16<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Pair interviewing<br />
    18. 17<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Multiple note-takers<br />
    19. 18<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Group synthesis<br />
    20. 19<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Visible shared interview findings<br />
    21. 20<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br />Sketchboard<br />
    22. 21<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Continuous customer engagement<br />Five users every Friday (Three on Thursday)<br />“Talk to us” button<br />Just-in-time recruiting<br />
    23. 22<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> One session, multiple activities<br />Collect context<br />Do a collaborative activity<br />Get feedback on product or prototype<br />
    24. 23<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Results of collaborative design sessions<br />
    25. 24<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Feedback on paper prototype<br />
    26. THANKS!<br />Lane Halleytwitter: @thinknow<br />
    27. 26<br />CC BY-NC-SA <br />#LeanUX | @thinknow<br /> Credits and appreciation<br />Waterfall photo, www.flickr.com/photos/zoutedrop/2297190795<br />Innovation Games Online, Knowsy team (slide 5)<br />Atomic Object (slides 10, 16, 17, 18)<br />Interviewing for UX, General Assembly (Slide 11)<br />SkillSlate (slides 13, 19, 23)<br />Atomic Object, provisional persona posters by Jeff Patton (slide 14)<br />DomainMatcher, Lean Startup Machine (slide 20, 24)<br />All photos by Lane Halley unless otherwise credited<br />

    ×