Search the courses, subjects, tracks, games and features, or jump straight to a page.
Learn it your way
A short class with Sarah and her students. The other ways are under More.
Sign up free to listen. Transcripts are free to read.
Today, we’ll focus on the testing phase of prototyping! Why do we need to gather feedback? Can someone share their thoughts?
I think feedback helps us improve our designs based on other people's opinions.
Yeah! It can show if we've missed something important.
Exactly! Gathering feedback ensures we address any usability issues. Remember, constructive feedback is crucial. Let's use the acronym GATHER: Gather, Analyze, Test, Hear, Evaluate, Respond. This process emphasizes what feedback should accomplish!
What kinds of questions should we ask during testing?
Great question! You should ask open-ended questions, like 'What works well?' and 'What confuses you?' This encourages detailed responses.
And observing their reactions is important too, right?
Absolutely! Nonverbal cues also help understand user experiences. Let's summarize: feedback is essential for improvement and should focus on user experiences!
Let’s dive deeper into the types of feedback we might gather. What do you think are some effective ways to collect this feedback?
We could use sticky notes to write down what we think each prototype needs!
Maybe we could do some peer reviews together, like sharing our prototypes and then discussing them.
Excellent ideas! Using sticky notes allows for anonymous feedback, and peer reviews foster collaborative discussion. Remember to keep the feedback structured; positive comments should be coupled with constructive criticism.
How can we make sure everyone shares their thoughts during feedback?
You can create a feedback protocol where each person speaks in turn or uses a feedback round where everyone writes down their thoughts before discussing them. This ensures no voice goes unheard.
This sounds like a solid plan! I feel more prepared to conduct a thorough testing phase.
Let’s talk about the significance of observing reactions during testing. Why do you think this is important?
I think it helps us notice things that people don't say out loud.
Right! Their body language can show if they understand the prototype or find it confusing.
Exactly! Non-verbal feedback can be just as informative as verbal feedback. Students should look for expressions of confusion or frustration and then ask tailored follow-up questions to explore these reactions further.
What should we do if someone looks confused?
You can ask them directly what they find confusing. Understanding these cues allows for better iterations in your design process.
So, combining verbal and non-verbal feedback can really give us a full picture?
Absolutely! Ultimately, this holistic approach enhances our understanding and helps refine our prototypes effectively.
Feedback we seek, both strong and meek, to help our designs go from weak to peak.
Imagine a builder who shows their new house to friends; they notice confusion and smiles, which guides the builder on how to shape the final outcome.
Use the acronym FACE: Feedback, Analyze, Communicate, Evolve. This reminds us of the steps for effective feedback collection.
Remember GATHER for the testing stage: Gather feedback, Analyze it, Test responses, Hear users, Evaluate findings, Respond with changes.
Term
What is feedback?
Click to flip
Term
Why observe non-verbal cues?
Click to flip
Term
What is constructive criticism?
Click to flip
Information received from others regarding the effectiveness and usability of a prototype.
Physical signals, such as body language and facial expressions, that convey user reactions.
Helpful, specific feedback that is intended to improve a design or prototype.
The testing phase of prototyping involves gathering feedback from peers and users to assess the usability and effectiveness of the prototype.
Testing is a crucial step in the prototyping process where feedback is collected from classmates, teachers, and potential users. This feedback helps identify what works well, what needs improvement, and ensures that the prototype is user-centric before moving forward with further refinements.
The testing phase is integral to the iterative prototyping cycle, occurring after the initial build. In this stage, feedback is gathered systematically. Students engage classmates, teachers, or representatives of target users to critique their prototypes. Here are the key elements:
The insights from this testing guide the improvement of the prototype in the following phase.