Activity 01
Peer Feedback Carousel: Prototype Testing
Students place prototypes at stations around the room. Groups of four rotate every five minutes to test each other's designs, noting one strength and one improvement on feedback sheets. After rotations, students select top feedback to iterate on their prototype.
Analyze user feedback to identify areas for design improvement.
Facilitation TipDuring Peer Feedback Carousel, set a timer for each station so students focus on one feedback prompt at a time and rotate efficiently.
What to look forStudents present their initial prototype to a small group. Each group member provides one specific suggestion for improvement on a sticky note. Students then collect these notes and identify at least two key pieces of feedback to address in their next version.
RememberUnderstandApplyRelationship SkillsSelf-Management
Generate Complete Lesson→· · ·
Activity 02
Iteration Relay: Design Dash
In pairs, students start with a basic sketch of a lunchbox organiser. One partner tests it with classmates, gathers verbal feedback, then passes to the other for a quick revision. Pairs repeat three times, presenting final versions to the class.
Justify the necessity of iterative design in product development.
Facilitation TipIn Iteration Relay, position the prototype and feedback form side by side so students revise immediately after receiving comments, reinforcing the connection between input and change.
What to look forAfter students have made revisions to their prototype, ask them to write down one change they made and explain why they made it, referencing specific feedback they received. For example: 'I added a handle to the box because Sarah said it was hard to carry.'
RememberUnderstandApplyRelationship SkillsSelf-Management
Generate Complete Lesson→· · ·
Activity 03
Whole Class Challenge: Toy Redesign Sprint
Present a flawed toy model to the class. Students vote on issues, form small groups to prototype fixes, test with peers, and iterate twice. Groups share before-and-after versions in a showcase.
Predict how a design modification will impact user experience.
Facilitation TipFor the Whole Class Challenge, assign clear roles like tester, recorder, or designer so every student contributes meaningfully during the sprint.
What to look forFacilitate a class discussion using the prompt: 'Imagine a product you use every day, like a pencil or a water bottle. How do you think it might have been changed and improved over time based on people using it?' Encourage students to think about comfort, durability, and ease of use.
RememberUnderstandApplyRelationship SkillsSelf-Management
Generate Complete Lesson→· · ·
Activity 04
Individual Log: Feedback Journal
Each student builds a simple tool like a bookmark holder, tests it alone first, then with a partner for feedback. They journal changes across three versions, drawing or writing predictions on user impact before final testing.
Analyze user feedback to identify areas for design improvement.
Facilitation TipKeep Individual Logs visible in a designated folder so students revisit their own feedback history and track progress across versions.
What to look forStudents present their initial prototype to a small group. Each group member provides one specific suggestion for improvement on a sticky note. Students then collect these notes and identify at least two key pieces of feedback to address in their next version.
RememberUnderstandApplyRelationship SkillsSelf-Management
Generate Complete Lesson→A few notes on teaching this unit
Teachers should model how to receive feedback without defensiveness, using phrases like ‘I noticed you mentioned…’ to validate input. Emphasise that iteration is not failure but a standard part of design, citing examples like LEGO or Band-Aids that evolved through user testing. Avoid rushing to ‘perfect’ prototypes; instead, celebrate the messy middle where most learning happens. Research shows students retain design thinking best when they experience the full cycle themselves, so resist the urge to step in too soon with solutions.
Successful learning looks like students confidently using feedback to justify design changes, comparing initial and revised prototypes with clear reasoning. They should articulate how their changes address specific user needs and discuss patterns they noticed during testing. Their journals should reflect a cycle of testing, reflecting, and improving rather than treating prototypes as final products.
Watch Out for These Misconceptions
During Peer Feedback Carousel, watch for students who assume one round of feedback is enough to finalise their design.
Use the feedback sheets to prompt students to circle the most common suggestions and star the most urgent issues. Then, ask them to list which changes they will test in their next prototype before moving on.
During Iteration Relay, watch for students who believe their first design should already be perfect.
Pause the relay after each round to hold up two prototypes side by side. Ask students to point out one improvement in the second version that came directly from feedback, making the link between input and change explicit.
During Whole Class Challenge, watch for students who dismiss feedback as mere opinions.
Provide a class tally sheet where students record feedback themes (e.g., ‘too heavy,’ ‘hard to grip’). After testing, tally the results together to show how patterns of comments reveal objective user needs rather than personal taste.
Methods used in this brief