Slide 1

This is a focusing stage

Dishmaker by Ted Selker and Leonardo Bonanni from MITWhat is a prototype? Looks likeProduct

Works likeInteracts likeService/ExperienceSpaceStory

While many people think of a prototype as a rough version of a physical product, prototypes actually span a much wider range of artifacts and experiences, and serve a variety of purposes for designers. This slide demonstrates the range of possibilities for prototypesscope of what can be prototyped

Two points: prototypes arent just THINGS, and they serve a specific purpose.

Several pics from B. Moggridge Prototyping lecture from Transformative design. Product looks like: http://andrewmckinney.com/assets/2009/1/22/iphone-testing.JPG; movie script: http://i253.photobucket.com/albums/hh54/Arbiter2732/HaloMovieScript02.jpghttp://i253.photobucket.com/albums/hh54/Arbiter2732/HaloMovieScript02.jpg7What is a prototype? It is the iterative generation of artifacts intended to answer questions that get you closer to your final solution

It is creating a concrete embodiment of a concept which become a way to test your hypotheses

It is building to think

While many people think of a prototype as a rough version of a physical product, prototypes actually span a much wider range of artifacts and experiences, and serve a variety of purposes for designers. This slide demonstrates the range of possibilities for prototypesscope of what can be prototyped

Two points: prototypes arent just THINGS, and they serve a specific purpose.

Several pics from B. Moggridge Prototyping lecture from Transformative design. Product looks like: http://andrewmckinney.com/assets/2009/1/22/iphone-testing.JPG; movie script: http://i253.photobucket.com/albums/hh54/Arbiter2732/HaloMovieScript02.jpghttp://i253.photobucket.com/albums/hh54/Arbiter2732/HaloMovieScript02.jpg8It is an attitude

What is a prototype? 9

FAIL EARLY and OFTEN(risk and cost vs. iteration curve)(cost of failure vs. project time)

(if those three reasons werent enough!) we advocate what we call rapid prototyping because Prototyping reduces risk! Early failures are much cheaper than late failures!

H2 prototype: ID A VARIABLEPrototype with a purpose.

a prototype should be designed to answer a single question. The best way to do this is to ID a variable to test: Be explicit about the variable you are testing, and bring resolution to this variable. are you trying to determine how something feels? How it looks? How a mechanism works? How a person interacts with it? Bring resolution to the variable that you are testing.

The prototype you build will be very different depending on the question youre trying to answer/variable youre testing.

Best practice: bring multiple prototypes, only difference being a variation on the variable youre testing.

H2 prototype: ID A VARIABLEPrototype with a purpose.

a prototype should be designed to answer a single question. The best way to do this is to ID a variable to test: Be explicit about the variable you are testing, and bring resolution to this variable. are you trying to determine how something feels? How it looks? How a mechanism works? How a person interacts with it? Bring resolution to the variable that you are testing.

The prototype you build will be very different depending on the question youre trying to answer/variable youre testing.

Best practice: bring multiple prototypes, only difference being a variation on the variable youre testing.

H2 prototype: ID A VARIABLEPrototype with a purpose.

a prototype should be designed to answer a single question. The best way to do this is to ID a variable to test: Be explicit about the variable you are testing, and bring resolution to this variable. are you trying to determine how something feels? How it looks? How a mechanism works? How a person interacts with it? Bring resolution to the variable that you are testing.

The prototype you build will be very different depending on the question youre trying to answer/variable youre testing.

Best practice: bring multiple prototypes, only difference being a variation on the variable youre testing.H2 prototype: SCALE RESOLUTION

first passfinal designfor Gyrus ACMI, ENT DivisionThe resolution of your prototype should reflect where you are in the design process.

Early on, this means that all prototypes should be VERY rough!! This is important for several reasons: its highly unlikely that youve reached a point that deserves a significant investment of your time/resources rough prototypes are easier to iterate on the flyyou want to be able to update prototypes based on user feedback, and the more highly resolved, the more difficult that is to do in the fieldYoull get more candid feedback with a rough prototypeif you hand someone something nice, even if they dislike it, theyll feel obliged to give you positive feedback

You said you were reluctant to put something made of foam and duct tape into the hands of a surgeon, but IDEO did. The doctor was trying to convey what form the needed device should take, so a designer ran out of the room, threw this together, and went back and asked, is this what you meant? when the surgeon held it he was able to speak to what aspects of the design he liked, didnt, what worked and what was needed.

H2 prototype: CREATE EXPERIENCESDont just tell users about an idea that you havea prototype is an opportunity for you to create an experience for your user.

Consider how your prototype fits into the context of the users life, and seek to place it in its appropriate context.

Are there important psychological/emotional/physical constraints that impact a users experience of your prototype? Make sure you create an experience that includes these!H2 prototype: CREATE EXPERIENCES

Dont just tell users about an idea that you havea prototype is an opportunity for you to create an experience for your user.

Consider how your prototype fits into the context of the users life, and seek to place it in its appropriate context.

Are there important psychological/emotional/physical constraints that impact a users experience of your prototype? Make sure you create an experience that includes these!prototype resolution should match the progress of your development identify the variable you want to explorelet go of yourprototypescreateexperiences

H2 prototype:

This is a focusing stageuse your prototypes as a probe to continue to gain empathy for your userstest (or, OBSERVE again!)IN D.THINK WE WANT TO AMPLIFY YOUR EMPATHY...THIS IS A REFLECTION OF

not proving, selling, or evaluating feasiblity of your low-res proto, youre using it as a tool to have a conversation and DEEPEN what you know and understand about needs and your solution to meet those needs

a bit about checking your ego...the users are the experts in their experience of your proposed solution (even kids/ed policy makers!)what new information do you have about needs?what new information do you have about how your solution addresses the need?

why TEST?IN D.THINK WE WANT TO AMPLIFY YOUR EMPATHY...THIS IS A REFLECTION OF

let the user experience the prototype:set the scene surrounding your prototypegive a short explanation to set contextact like a guide (not a lead)HOW TO test: PLAN

observe the experience: capture what worked, and what didnt worksee how users use and mis-use your prototypelisten more than you talk to give users a chance to interpret H2 test: OBSERVE the experienceengage the user:

iterate on the fly to communicate learningsask specific, open-ended questionsremember: the user is the expert

H2 test: let the user EXPERIENCE

H2 test: gather feedback systematically

31PK/AK: Situation 1User overexplains exactly how the prototype worksUser defends prototypeUser defends prototype, saying that the user doesnt get it, isnt the right demographic anyway and has no idea what most people would think.Disregards users concern over safety or priceIgnores users confusion over where they could acquire this prototype

AF/Ako: Situation 2Minimal explanation of what prototype is and doesDesigner listens to feedbacks and asks for more explanation of one commentDesigner addresses a concern by saying would it help if to address that I did.?Designer nods and notes down the negative feedback, says thank youAsks how could I make this better?Asks do you have any concerns about this product/service?Designer comments on body language - excitement, quick to pick up/put down prototype, facial gestures