Activity 01
Peer Review Rounds: Prototype Feedback
Students pair up to demo their software prototypes. Partners act as users, test for 5 minutes, and note 3 strengths and 3 improvements on a shared form. Pairs switch roles twice, then discuss top feedback items as a class.
Analyze user feedback to identify areas for improvement in a software prototype.
Facilitation TipFor Peer Review Rounds, provide a feedback form with specific prompts to guide students away from vague comments like 'it’s bad' and toward actionable insights.
What to look forStudents work in pairs to test each other's software prototypes. After testing, they complete a feedback form that asks: 'What is one thing that worked well?', 'What is one thing that was confusing or difficult to use?', and 'Suggest one specific change to improve this feature.' Partners must then discuss the feedback and agree on one change to implement.
ApplyAnalyzeEvaluateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 02
User Testing Stations: Role-Play Scenarios
Set up 3 stations with common user personas (e.g., novice, expert). Small groups rotate, testing prototypes and recording feedback via video or notes. Debrief identifies common themes for iteration plans.
Design a plan for incorporating user suggestions into the next iteration of a product.
Facilitation TipDuring User Testing Stations, circulate with a checklist to ensure students capture both positive feedback and critical issues from their testers.
What to look forProvide students with a short, synthesized list of user feedback comments for a hypothetical app. Ask them to categorize each comment as a 'bug report,' 'feature request,' or 'usability issue' and then identify the top two most critical issues to address in the next iteration.
ApplyAnalyzeEvaluateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 03
Iteration Sprint: Feedback to Prototype 2.0
In small groups, students review compiled feedback, vote on priorities, and code revisions in a 20-minute sprint. Groups present before/after demos, evaluating usability gains with a class rubric.
Evaluate the impact of user-centered iteration on product usability and satisfaction.
Facilitation TipIn the Iteration Sprint, set a visible timer and progress chart so groups can track how many changes they implement within the time limit.
What to look forStudents reflect on a recent iteration cycle. They should answer: 'What was the most valuable piece of user feedback you received or analyzed?' and 'How did you or would you incorporate this feedback into your software?'
ApplyAnalyzeEvaluateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 04
Survey and Analyze: Digital Feedback Loop
Individuals create a quick Google Form survey for their prototype, share with 5 peers, and analyze responses for patterns. They draft a one-page iteration plan and share in a whole-class gallery walk.
Analyze user feedback to identify areas for improvement in a software prototype.
Facilitation TipFor the Survey and Analyze activity, give students a template to organize feedback into themes before they decide which issues to address.
What to look forStudents work in pairs to test each other's software prototypes. After testing, they complete a feedback form that asks: 'What is one thing that worked well?', 'What is one thing that was confusing or difficult to use?', and 'Suggest one specific change to improve this feature.' Partners must then discuss the feedback and agree on one change to implement.
ApplyAnalyzeEvaluateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→A few notes on teaching this unit
Experienced teachers approach this topic by framing feedback as a gift, not criticism, and modeling how to receive it professionally. They avoid letting students dismiss conflicting feedback by requiring them to justify their design choices with user needs. Research shows that structured reflection after each iteration cycle deepens learning, so teachers build in time for students to articulate what they learned from each change.
Successful learning looks like students confidently analyzing feedback, prioritizing issues, and justifying design changes with evidence. They will demonstrate collaboration by incorporating multiple perspectives and tracking progress through visible iterations. Clear before-and-after comparisons of prototypes show measurable improvements.
Watch Out for These Misconceptions
During Peer Review Rounds, some students may assume feedback is mostly complaints with no value.
Use the provided feedback form to guide students to identify both strengths and specific improvements. Have them circle one positive comment and one actionable suggestion for each prototype they review.
During the Iteration Sprint, students might think one round of changes fully perfects their software.
Provide a simple progress tracker where groups mark each change they implement and note how it addresses a specific piece of feedback. After the sprint, groups present one improvement and explain the feedback that led to it.
During User Testing Stations, students may ignore feedback that conflicts with their original vision.
Ask testers to explain why a feature felt difficult to use, then have students defend their design choices in a 60-second debate before deciding whether to adjust it.
Methods used in this brief