Plug and Play Tech Center Startup Bootcamp Intro
•Download as PPTX, PDF•
0 likes•666 views
An introduction at the 2012 Plug and Play bootcamp to show how user experience (UX) can be applied to startups for little money but significant reward.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (9)
Similar to Plug and Play Tech Center Startup Bootcamp Intro
Similar to Plug and Play Tech Center Startup Bootcamp Intro (20)
Recently uploaded
Recently uploaded (20)
Plug and Play Tech Center Startup Bootcamp Intro
- 1. (boot) (camp)
- 2. UX & methods Turning UX into $$$ Expectations Conceptual models
- 6. Felix
- 12. What we do 360
- 13. Surveys Interviews Observation Diary Studies
- 14. Reviewing Patterns Sketching Wireframing Prototyping
- 15. Task Flows Affinity Diagramming Personas Storyboarding
- 16. Heuristic Analysis Remote Concept Testing Usability Testing Paper Prototyping
- 18. Let’s talk UX.
- 19. WTF?
- 20. A person’s interaction with any product, service, company or brand experience.
- 22. But what is UX for, anyway?
- 23. (good) UX leads to $$$
- 24. needs engagement = growt U deligh t h X sharin g …and more growth
- 25. =
- 26. U = = X
- 27. Let’s see UX at work.
- 28. Pandora for everything except music.
- 29. Good user base iPhone& BlackBerry apps Seed funding
- 30. Get investment ASAP. … by proving that their user experience ensures continued user growth.
- 31. But first…let’s talk curves.
- 32. Ideal Reality
- 33. Casual Habitual Churned
- 34. What makes someone a habitual user?
- 35. The “a ha! moment.”
- 36. Definition: The “a ha! moment” is what separates a casual, potentially churned user from a habitual one.
- 37. If an “a ha! moment” can prevent user churn… …understanding and creating more such moments can retain users over the long term.
- 38. New users and the Habitual users and the “out of the box” longer term experience experience
- 39. 360 Usability Diary study testing
- 40. Expectations all over the map. Also known as: “Is this like Pandora? Like regular radio? How should I use Stitcher?”
- 43. UX can be quick and dirty Investors like UX Expectations matter
- 46. Gustav Fechner, George A. Gescheider, Psychophysics Rockstar Modern day Fechner
- 53. Let’s talk conceptual models.
- 54. Product End users designers
- 55. Email Events Gifts Dating Money Universities Games Address book (your Trade life, onlin Photos e) IM/Chat Music Voyeurism Activism
- 56. But how do we know if our conceptual model is even making any sense to users?
- 57. An archetypal user designed to help focus product design and marketing efforts.
- 58. Marketing Behaviora l “Personas, as documents, should work for designers the way scent works for memories of your childhood.” - Andrew Hinton, Boxes and Arrows
- 59. Spectrum A Spectrum B Spectrum C Spectrum D
- 61. UX & methods (don’t be afraid to get your hands dirty) Turning UX into $$$ (UX is a gold mine) Expectations (they matter more than you think) Conceptual models (talk to real people)
- 62. Thanks! Ping me if you’d like some bootcamp help. jfdesroches@gmail.com @felixdesroches
Editor's Notes
- Surveys – good for quick quantitative dataInterviews – qualitative feedback – why? How? Examples?Contextual ObservationPhysically going to a relevant location and observing how people do thingsDiary Studies – primarily used for tracking behavior “in the moment”, “over time”providing participants with the materials and structure to record daily events, tasks and perceptions around a given subject in order to gain insight into their behavior and needs over time.StoryboardingCreating a series of sketches outlining the users’ experience in an environment and/or with a product
- Surveys InterviewsContextual ObservationPhysically going to a relevant location and observing how people do thingsDiary Studiesproviding participants with the materials and structure to record daily events, tasks and perceptions around a given subject in order to gain insight into their behavior and needs over time.StoryboardingCreating a series of sketches outlining the users’ experience in an environment and/or with a product
- Paper PrototypingLive, task-based testing using printed out wireframesRapid Iterative TestingTask-based testing with a clickable or paper prototype, followed by a quick round of changes, then more testing and changesRemote Concept TestingQuick feedback via a site like clueapp.comHeuristic Analysis An evaluation of the product based on design standards and best practices
- Context and environment = opportunities
- Stitcher was expected to be like radio, when the experience of discovering content was relying on new patterns of behavior. Harnessing these patterns in the right contexts was the key.
- Stitcher got its money, and went on to form partnerships with these 3 car companies – thus making Stitcher more radio-like than ever (and successful too). The right context, it turns out, was behind the wheel.
- Questions?
- Started with electric shock pain tests, weight perception, and sound/loudness perception
- Anyone remember this thing? People were SO amazed it worked, they didn’t care that they could barely use it. To them, WAP was magic and anything was WAY above their expectations.
- Switch. Really hard to use…which is fine because the users expect it. If it’s too easy, I’ve heard them say “but I must have missed something.”
- Thermostats (old)
- Thermostats (new/future). Behavior patterns CAN change, expectations can be pushed into the future.
- Segway: did it fail because it looks like it’ll just fall over (and very often did)?
- complementary