Third Grade · Science · week 34

Test & improve the design

Apply the design, test, and improve cycle to the week 33 weather-hazard design, identifying a specific weakness from a test and proposing an evidence-based improvement.

Engineers rarely get a design right on the first try. After building a first version, they TEST it, gather evidence of what worked and what did not, and then IMPROVE the design based on that evidence. This design, test, improve cycle can repeat several times before a solution is ready for real use.

A useful test is one that reveals a real weakness, not one where everything conveniently seems to work; finding a weakness is a successful test, not a failed one.

📋 For the teacher
Teach it (10–15 min):
  • If practical, build a rough, small-scale model of the week 33 design idea, even from paper or cardboard, and test it in some safe, small way, like a fan for wind or a cup of water for rain.
  • Push for a real weakness to be identified, rather than accepting "it worked great" without any evidence.
  • Connect the proposed improvement directly and specifically back to what the test actually revealed.
  • Reinforce that finding a flaw during testing is a sign of a good, informative test, not a failure.
Talk about it:
  • What did your test show about your first design?
  • What would you change for a second version, based on that test?
  • Why is finding a weakness during testing actually a good thing?

Mastery looks like: They identify a specific weakness revealed by a test and propose a specific, evidence-based improvement in response.

Common stumbles: Skipping straight to "it worked great" without identifying any real weakness, or proposing a random change unconnected to what the test actually showed.

Homework for this lessonType it, write it with a stylus, or print it for pencil & paper.open →
Records attendance + 15 min of Science for this learner.
← Back to todayAll coursesYear planner