Your SlideShare is downloading. ×
d.Maps: Discussion 3 Prototyping
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

d.Maps: Discussion 3 Prototyping

1,560
views

Published on

Published in: Design

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

No Downloads
Views
Total Views
1,560
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
3
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
  • Intro Names and 1 artistic or cultural thing you noticed on the way to this course?
  • The act of prototyping implies "building", testing, and iterating and is, itself, both a flaring and a narrowing process
  • Classic example NASA Challenger
  • separate early and mid stage prototypes a little more. include the differences of focusing on a specific feature/function (looks like/works like) building rough prototypes: brings questions to the surface (learn by doing) gets the idea out there without too much personal investment conversation piece--stand around talking about it.
  • there’s magic in the early stage prototypes. Expressing an idea in physical form is like giving it life. brings questions to the surface (learn by doing) gets the idea out there without too much personal investment conversation piece--stand around talking about it.
  • Asking a variety of users is not necessarily the same as asking a LOT of users. Pick your sample carefully. Give people space to play. Note what they notice first. How they use/misuse something. What comes naturally. Never say, “no, that’s not the way you do it.” (6” piston example). We have to get into the mentality that when someone uses a device in a way that’s incorrect, they’re not the ones that are wrong. It is the designer that is wrong. R.espect the user Give example of people
  • Asking a variety of users is not necessarily the same as asking a LOT of users. Pick your sample carefully. Give people space to play. Note what they notice first. How they use/misuse something. What comes naturally. Never say, “no, that’s not the way you do it.” (6” piston example). We have to get into the mentality that when someone uses a device in a way that’s incorrect, they’re not the ones that are wrong. It is the designer that is wrong. R.espect the user Give example of people
  • start at 10:30 isolate your variables: call waiting by standing in line at post office
  • isolate your variables: call waiting by standing in line at post office
  • Transcript

    • 1. d.Maps: Design Cultural Maps Discussion 3 [email_address]
    • 2. Agenda
    • 3. Project 1 Results
      • I tried…
      • I learned…
      • I felt
    • 4. Testing
          • Ask : What are you thinking? Why?
          • Reflect : What is their first impression? What’s working?
          • Ask : How would you do [x] task…? (repeat)
          • Reflect : What new errors, problems, questions have emerged?
          • Ask : How would you change [x] task…?(repeat)
          • Reflect : What unexpected things are happening?
    • 5. Transition: Inspiration
    • 6.  
    • 7. Prototype (n): an incomplete representation of an idea that helps answer a question
    • 8. Prototyping
      • "Prototyping is the iterative development of artifacts – digital, physical, or experiential – intended to elicit qualitative or quantitative feedback." (Geehr, 2008)
    • 9. Flaring & Narrowing
      • The flaring represents the proliferation of low-resolution prototypes developed as different aspects of the prototype are evaluated and the narrowing represents the refinement of the lower resolution models into increasingly complex and resolved models.
    • 10. Why Prototype?
      • Prototyping allows you to fully explore all of those concepts you want to evaluate
      • You prototype because you need to explore your options -- to try things and fail, further informing your design process
      • Prototyping is a way to do your due diligence on the concepts that came out of ideation
    • 11.
      • If a picture is worth a thousand words, a prototype is worth a thousand pictures
    • 12. Big idea 1 Prototype Early : Fail Early Big idea 2 Big idea 3 color
    • 13. Prototype Often
    • 14. Examples
    • 15. kinds of prototypes function look feel experience
    • 16. How are prototypes used? inspire · express · test · refine · validate early stage mid stage late stage
    • 17. express an idea without owning it create an opportunity for collaboration hold it, use it, talk about it bring questions to the surface early-stage prototypes anything more substantial than arm-waving
    • 18. mid-stage prototypes rough rapid right
    • 19. rough
      • build as crude as possible
      • crummy prototypes are ideal
      Prototypes aren’t precious. Learnings are.
    • 20. rapid don’t waste time building non-essentials use what’s available
    • 21. right create a menu of prototypes prototype one aspect at a time test the riskiest ideas first
    • 22. how to use prototypes
      • ask a variety of users
      • observe, don’t explain
      • expect unexpected insights
    • 23. Advice
      • celebrate failure
      create a workspace conducive to prototyping never enter a meeting without a prototype when in doubt, prototype
    • 24. Prototyping: Principles
      • Isolate your variables:
      • Call waiting by standing in line at post office
    • 25. Prototyping: Principles
      • Use what you have
      • Bias toward action
    • 26. Transition
      • Questions?
    • 27. House Keeping
      • Blogging, social media, and calendar
    • 28. Debrief
      • I like
      • I wish
      • How to
    • 29. Credits
      • Material adapted from dschool.stanford.edu
      • Special thanks to Carly Geehr and David Klaus (AMIO Engineering, July 2007) for allowing shamelessly stolen inspiration