Your SlideShare is downloading. ×
Rapid Product Design in the Wild
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

Rapid Product Design in the Wild


Published on

A version of my talk 'Rapid Product Design in the Wild' that I gave at GOTO Zurich (#GOTOzrh) on 10th April 2013 in the UX track.

A version of my talk 'Rapid Product Design in the Wild' that I gave at GOTO Zurich (#GOTOzrh) on 10th April 2013 in the UX track.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Rapid product design in the wildMichele Ide-Smith @micheleidesmith
  • 2. How do people use your application?
  • 3. Who are they with?
  • 4. “To make excellent products that truly understand ourusers’ contexts, we must look further, and investigatecontext first-hand” Cennydd Bowles
  • 5. Red Gate makes database and .NET tooling
  • 6.
  • 7. What makes you visit an exhibition standat a conference?
  • 8.
  • 9. “By the time the product is “Marketing that itselfready, it will already have improves peoples lives.”established customers.” Bob GilbreathEric Ries
  • 10. “We wanted to make sure we were getting customerfeedback as we worked so that we were never workingon anything that wasn’t valued by the customer.”Nordstrom Innovation Lab: Sunglasses iPad App
  • 11. Some principles: • Continuous discovery • Shared understanding • GOOB (Get Out Of the Building) • Externalising your work“if you’ve struggled to figure out how UX design canwork in an Agile environment, Lean UX can help.”Jeff Gothelf, author of Lean UX
  • 12. Hypothesis:Oracle Developers & DBAs need a better way tosource control their database schemas>70% interest – develop a tool a.s.a.p.
  • 13. Let’s watch a short video about the case study
  • 14. 9 (mini) sprints, 3 days, 1 prototype
  • 15. Making our processes transparent
  • 16. 25 feedback sessions with users
  • 17. Paper prototypingLo-fi prototypes are feedback and easytoto change Easy to get quick and quick changebefore you commit to code
  • 18. People returned to see personas and a talking point! Helped build the feedback we hadgathered throughout the conference
  • 19. The Empathy Map helped us understandcustomer needs
  • 20. Creating an ‘affinity map’ helped to quicklyanalyse feedback about features
  • 21. Sketching out processes and environmentsidentified real-world scenarios and pain points
  • 22. It’s all about communication…
  • 23. …and collaboration
  • 24. Feedback went directly into the HTML/CSSprototype, using Twitter Bootstrap
  • 25. Keep the conversation going
  • 26. Surveys to test hypotheses
  • 27. Interviews and remote usability testing on prototype
  • 28. Releasing functionality early and getting feedback
  • 29. Testing the prototype“The live lab was a wonderful idea. I enjoyedparticipating in it and cant wait to see the finishedproduct. Let me know if you need a beta tester.”Christoph Ruepprich, Oracle Developer
  • 30. Michele Ide-SmithUser Experience SpecialistRed Gate Softwaree: @micheleidesmithb:
  • 31. Thank you for listeningMore With Context: Startup: http://theleanstartup.comNordstrum Innovation Lab video: Next Evolution of Marketing: UX Book: http://www.leanuxbook.comAffinity Map: Map:
  • 32. Image CreditsDesert: Kevin.Cochran texting: Oso with Grandpa’s iPad: Jo Shlabotnik Developers working at Magenic in San Francisco: Wonderlane
  • 33. Image CreditsQuadrupedal ipad stand: building: Prayitno tubes: Paigggeyy