Class 10_Homework_February 22nd

Hello all,
Great work today! For homework this weekend, your group will transform your feedback into one idea and one prototype. In addition, your group will create a story or a script that will be used to explain your idea via your prototype during our final presentation. On Tuesday we will conduct another internal user-testing session. The expectation is that you will have your prototype and script as finished as possible so that you can use audience feedback to strengthen the visual and verbal components of what you will be sharing with stakeholders. In other words, we will edit, refine, and revise your work so that your work comes across in the most interesting and innovative way as possible!
Best,
Team IPC

c10_a1
Complete Prototype(s) for User-Testing

Due: Tuesday, February 27th

Format: Physical artifact(s) in class

Now that you have locked into refining one amazing and innovative idea, improve and strengthen said idea's corresponding prototype using the feedback you received in class. This will entail remaking the prototype entirely [in most cases] and, most likely, adding and creating more elements to account for:

• context 
• functionality
• navigation of space
• scale

Remember that what you create will serve as a tool(s) for getting your stakeholders invested in what you are proposing to make for solving their problem. Prototypes of functional objects and the contexts and processes connected to said functional objects are very important in regard to drawing in your audience. As you develop these prototypes for homework, be sure to show your work to people outside of your team and the IPC class. Do they understand what you have made and it's purpose? Do they understand how it works and where it exists? Does it solve for the POV you developed? Does it connect to the larger original problem? You may still use rudimentary and inexpensive [found] materials to create your prototypes as long as these are finished in a neat and clean manner. To do this well anticipate needing to paint over surfaces so that nothing but what you intend your audience to see is in view. Please speak to your professor if you have questions about this. 

Bring your completed and refined prototype(s) back with you to class for another in-depth discussion.

c10_a2
Complete a Script for User-Testing

Due: Tuesday, February 27th

Format: save a file to Google Docs group folder AND bring a printed copy with you to class

Each team will prepare a script that corresponds to their prototype using Google Docs. This team document will be named in the following way: c10_a2PresentationScript_TeamNumber_version1
It will be saved in the Google group folder AND a printed copy will be brought with you to class.

Keep your script to about 8-10 minutes (which is usually around 600-1000 words). Try starting with a 'hook' that is compelling to your audience and captures their attention. Attention spans are short. How can you introduce what you are doing in a way that makes people eager to know more?

Remember, people like stories. The more you can think about how to convey your project concept in a way that tells a story, the better. Consider your stakeholder and the pain points that you heard directly from their particular interviews. Make sure that their need and insight are understood by the audience. Your story should walk the audience through the context, functionality, and navigation of space in a way that unfolds as a user might experience using what you have developed on their own. Be thorough!

Make sure these components are in your script:

1. Intro / Hook (this should include some background of the project based on your research to set the stage for your concept).
2. Defining your POV (make sure you clearly address who your stakeholder is, their needs, based on insights you discovered). 
3. Introduce your design concept. Make sure to highlight all of the great features of your concept. This is the meat of your presentation. Discuss the concept as a whole and describe all the working components of it. 
4. The benefits / Rationale of all the features. Why are these features good for your user?
5. Some conclusions on why this project solution is the best concept for your user/POV.