Hybrid User Interviews
•
11 likes•3,908 views
The document discusses lean UX practices for software development, including collaborative user interviews. It recommends that teams plan interviews together by discussing goals and preparing questions. Both provisional and revised personas should be created to represent different types of users. During interviews, multiple people take notes, insights are synthesized as a group, and findings are shared visually. Continuous user engagement is important through methods like weekly interviews and prototypes tests. The overall approach emphasizes collaboration, visualization, and frequent customer feedback to guide an iterative development process.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (16)
Similar to Hybrid User Interviews
Similar to Hybrid User Interviews (20)
More from Lane Goldstone
More from Lane Goldstone (18)
Recently uploaded
Recently uploaded (20)
Hybrid User Interviews
- 1. Hybrid* user interviews Balanced Team Conference September 25, 2011 *as in “something thatispoweredbymorethan one source of power”
- 2. 1 CC BY-NC-SA #LeanUX | @thinknow The origin of software development
- 3. 2 CC BY-NC-SA #LeanUX | @thinknow Old-skool software development process PLAN – BUILD – TEST – SHIP – T-SHIRT
- 4. 3 CC BY-NC-SA #LeanUX | @thinknow Design tried to fit in PLAN – BUILD – TEST – SHIP – T-SHIRT ^ RESEARCH – DESIGN
- 5. 4 CC BY-NC-SA #LeanUX | @thinknow And then, everything changed Technology is no longer the problem Product decisions are design decisions Continuous customer engagement matters
- 6. 5 CC BY-NC-SA #LeanUX | @thinknow Collaborative, multi-functional teams
- 7. 6 CC BY-NC-SA #LeanUX | @thinknow Lean UX feedback loop THINK MAKE CHECK
- 8. 7 CC BY-NC-SA #LeanUX | @thinknow Design is a core team competency, not a role Designer as coach/facilitator Designer as product steward Design studio/charrette Design patterns/style guides
- 9. Quick Visual Collaborative Continuous 8 CC BY-NC-SA #LeanUX | @thinknow Successful design methods are
- 10. 9 CC BY-NC-SA #LeanUX | @thinknow Collaborative interview planning Team discusses what they want to learn Prepare interview “guide” Practice asking questions, listening
- 11. 10 CC BY-NC-SA #LeanUX | @thinknow Collaborative interview planning
- 12. 11 CC BY-NC-SA #LeanUX | @thinknow Interview guides
- 13. 12 CC BY-NC-SA #LeanUX | @thinknow Provisional personas Declare who we think the “customer” is Shared visual artifact Evolve over time
- 14. 13 CC BY-NC-SA #LeanUX | @thinknow Provisional personas before interviews
- 15. 14 CC BY-NC-SA #LeanUX | @thinknow Provisional personas after some interviews
- 16. 15 CC BY-NC-SA #LeanUX | @thinknow Team interviewing Pair interviewing (lead/backup) Multiple note-takers Group synthesis Visual radiators and sketchboards
- 17. 16 CC BY-NC-SA #LeanUX | @thinknow Pair interviewing
- 18. 17 CC BY-NC-SA #LeanUX | @thinknow Multiple note-takers
- 19. 18 CC BY-NC-SA #LeanUX | @thinknow Group synthesis
- 20. 19 CC BY-NC-SA #LeanUX | @thinknow Visible shared interview findings
- 21. 20 CC BY-NC-SA #LeanUX | @thinknow Sketchboard
- 22. 21 CC BY-NC-SA #LeanUX | @thinknow Continuous customer engagement Five users every Friday (Three on Thursday) “Talk to us” button Just-in-time recruiting
- 23. 22 CC BY-NC-SA #LeanUX | @thinknow One session, multiple activities Collect context Do a collaborative activity Get feedback on product or prototype
- 24. 23 CC BY-NC-SA #LeanUX | @thinknow Results of collaborative design sessions
- 25. 24 CC BY-NC-SA #LeanUX | @thinknow Feedback on paper prototype
- 26. THANKS! Lane Halleytwitter: @thinknow
- 27. 26 CC BY-NC-SA #LeanUX | @thinknow Credits and appreciation Waterfall photo, www.flickr.com/photos/zoutedrop/2297190795 Innovation Games Online, Knowsy team (slide 5) Atomic Object (slides 10, 16, 17, 18) Interviewing for UX, General Assembly (Slide 11) SkillSlate (slides 13, 19, 23) Atomic Object, provisional persona posters by Jeff Patton (slide 14) DomainMatcher, Lean Startup Machine (slide 20, 24) All photos by Lane Halley unless otherwise credited
Editor's Notes
- 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”