📚Unit Plans → 🌿Sustainable Technology → 9Testing & Iteration
Years 9–10 Hangarau / Technology

Sustainable Design Studio · Lesson 9: Testing and Iteration

Year 9–10 Technology. Students execute two rounds of structured user testing, refine their prototype based on real feedback, and complete Design Journal Section 9.

Sustainable Design Studio · Lesson 9

Studio build: test it and change one thing

Ākonga run their own success test, record what it showed, and make one change the evidence justifies.

  • Design Studio move: Test result, then a single evidence-led revision
  • Evidence it produces: Before/after data plus the reason for the change
Other teaching approach: Applied Sustainable Systems Survey →

Lesson at a Glance | He Tirohanga Whakamua

Do NowWhy user testing hurts your ego but saves your design10 min
Testing Round 1Structured 5-minute user testing protocol with peer15 min
Targeted IterationModify ONE functional & ONE environmental feature15 min
Design JournalWrite Section 9: Test & Iterate Record10 min
Exit ReflectionState the single biggest change made between iterations5 min

Ngā Whāinga Ako | Learning Intentions

Students will know

  • That testing is an evidence-gathering process to validate or refute design hypotheses against brief specifications.
  • How to conduct an unbiased 3-question user testing protocol without leading the user.
  • How iteration converts user criticism into improved technological fitness-for-purpose.

Students will demonstrate

  • By executing Round 1 testing, recording user observations, and making at least ONE concrete design modification.
  • By completing Design Journal Section 9: Test & Iterate Record in preparation for Lesson 10's Showcase.

Do Now | Tīmatanga Whakaaro (10 min)

Testing Mindset Prompt:

"If a user gets confused while using your prototype, whose fault is it — the user's or the designer's?"

Unpack: It is 100% the designer's fault. In technology design, if a user struggles to disassemble, operate, or understand your prototype, your design has failed its usability specification. Testing is not defending your product — it is watching someone else attempt to use it without your help.

Structured 5-Minute User Testing Protocol (15 min)

Testing Rules:

  1. No Explaining: Hand the prototype to your tester. Do NOT tell them how it works or how to disassemble it. Let them try.
  2. Ask 3 Standard Questions:
    • 1. "What do you think this object is designed to do?"
    • 2. "How would you open or disassemble this for repair?"
    • 3. "Which part of this design feels fragile or wasteful?"
  3. Record Observations: Note where the tester hesitates, gets stuck, or expresses confusion.

Activity: Rapid Iteration Pass (15 min)

Based on Round 1 feedback, make ONE immediate design modification to your prototype or specifications:

🔧 Usability / Functional Fix

e.g. Added clear disassembly icons, strengthened a fragile latch, or smoothed an ergonomic handle.

🌱 Sustainability Fix

e.g. Swapped a plastic snap-fit for a reusable metal pin to prevent clip breakage during repair.

📓 Design Journal — Section 9: Test & Iterate Record

Students open their Design Journal and write Section 9 (the final prep section before Lesson 10's Showcase):

Section 9 Structure:

1. User Feedback Summary: What did your tester struggle with or suggest?

2. Iteration 1 → Iteration 2 Change: Describe the specific modification you made after testing.

3. Brief Verification: How does your final iterated design satisfy your Lesson 7 Design Brief and Lesson 6 Kaitiakitanga Constraint?

Exit Reflection | Ka Mutu Hoki (5 min)

Exit Ticket Statement:

"The thing I changed between Iteration 1 and 2 was [Specific change] because user testing showed [Tester feedback/observation]."

Teacher Planning & Curriculum Alignment

NZ Curriculum Alignment (Technology — Phase 3 / Years 9–10):

  • Outcome Development & Evaluation: Test functional models with stakeholders to inform decision making, evaluating outcomes against brief specifications.
  • Technological Practice: Iterate designs based on empirical user feedback to improve fitness for purpose.

Vocabulary: User testing, iteration, feedback protocol, stakeholder evaluation, fitness-for-purpose verification.