Science · 2nd Grade · The Inventor's Workshop · Weeks 28-36

Improving and Redesigning

Students will use test results to identify areas for improvement and modify their prototypes to create a better solution.

• Common Core State Standards
• K-2-ETS1-3

About This Topic

Improving a design based on test evidence is the iteration stage of the engineering design process, and it is where students experience one of the most important lessons in engineering: good solutions rarely emerge fully formed on the first attempt. Using their test results as a guide, students identify specific changes to make, implement those changes in a revised prototype, and often test again to see whether the improvements worked. This topic continues to develop K-2-ETS1-3 competencies.

Students learn to distinguish between changing a design based on evidence ('the bridge sagged in the middle, so I added a support beam') versus changing it based on preference ('I just want to try something different'). Evidence-based iteration is a key disciplinary practice that carries through all future science and engineering work.

Active learning is fundamental to iteration because students must physically rebuild and retest. The cycle of build-test-analyze-improve is itself an active learning structure. Teachers who facilitate reflection between iterations , asking students to predict whether their change will help and then verify , maximize the conceptual yield from each physical modification.

Key Questions

1. Design modifications to a prototype based on test data.
2. Justify the changes made to a design to enhance its function.
3. Evaluate how iterative design leads to better solutions.

Learning Objectives

• Analyze test data to identify specific areas where a prototype failed to meet design criteria.
• Modify a prototype based on evidence from testing to improve its functionality.
• Justify design changes made to a prototype by explaining how they address specific test results.
• Compare the performance of an original prototype with a redesigned prototype using quantitative or qualitative data.
• Evaluate the effectiveness of iterative design in creating a more successful solution to an engineering problem.

Before You Start

Building and Testing Prototypes

Why: Students need experience building an initial version of a solution and testing its performance before they can analyze results and make improvements.

Identifying a Problem

Why: Understanding the initial problem the prototype is meant to solve is essential for students to recognize when and how their design needs modification.

Key Vocabulary

Prototype	An early model or sample of a product built to test a design or process. It is not the final version.
Iteration	The process of repeating a process or action, especially to improve a design or solution. It involves making changes and testing again.
Test Data	Information collected during testing that shows how well a prototype works or where it has problems.
Improvement	A change made to a design or prototype that makes it work better or solve the problem more effectively.

Watch Out for These Misconceptions

Common Misconception

Changing everything at once will fix the problem faster.

What to Teach Instead

Changing multiple things at once makes it impossible to know which change caused any improvement. Students discover this when they change two things and the design improves (or gets worse) , they cannot tell which change mattered. The 'change one thing at a time' constraint, while sometimes frustrating, directly teaches experimental logic.

Common Misconception

Once a design is improved, it is finished.

What to Teach Instead

Professional engineers iterate through many cycles of testing and improvement. After a successful redesign, students can still ask: could it be lighter, simpler, or more reliable? Introducing a stretch goal after the first successful iteration , 'Can you make it hold 2 more pennies?' , shows students that improvement is always possible.

Active Learning Ideas

Redesign Planning: Change One Thing

Before rebuilding, each student writes on an index card: (1) the specific problem they are fixing, (2) the change they plan to make, and (3) a prediction of what will be different in the next test. Groups discuss their cards with the teacher before beginning reconstruction. This structured pause prevents random changes and connects rebuilding to evidence-based reasoning.

15 min·Individual

Build and Retest: Version 2

Groups implement their planned change and rebuild their prototype. Once complete, they run the same test using the same procedure as the first trial and record results in a side-by-side comparison table (Version 1 results vs. Version 2 results). Groups circle the values that changed and note whether each change was an improvement.

35 min·Small Groups

Think-Pair-Share: Did It Work? Why?

After retesting, pairs discuss: did your change improve the design? How do you know? Each pair prepares one evidence-based claim to share with the class. During the whole-class share, the teacher charts improvements and unchanged areas to visualize which types of changes were most effective across all groups.

20 min·Pairs

Real-World Connections

• Toy designers at Mattel test many versions of a new toy car before deciding on the final design. They might change the wheels, the weight, or the material based on how well the car rolls or how durable it is.
• Automobile engineers test car parts, like brakes or engines, repeatedly. If a brake pad wears out too quickly during testing, they will redesign it with a stronger material to make it last longer.

Assessment Ideas

Quick Check

Present students with a simple scenario: 'Your bridge prototype fell down when you put 3 pennies on it.' Ask them to write or draw one specific change they could make to the bridge to make it stronger and explain why they chose that change.

Discussion Prompt

Ask students: 'Imagine you built a ramp for a toy car, and the car kept falling off. What kind of information from testing would help you decide how to fix the ramp? What are two specific changes you might make?'

Peer Assessment

Have students show their redesigned prototype to a partner. The partner asks: 'What was the problem with your first design?' and 'How does your new design fix that problem?' Students can use a simple checklist: Did the partner identify a problem? Did the partner explain how the new design fixes it?

Frequently Asked Questions

How do you teach iterative design to 2nd graders?

Frame each rebuild as 'Version 2' or 'Mark II' , language that signals improvement rather than starting over. Require students to write their planned change and a prediction before rebuilding, so the iteration is evidence-based rather than random experimentation. Comparing Version 1 and Version 2 test results side by side makes the improvement (or lack of it) concrete and visible.

Why is it important for 2nd graders to redesign their prototypes?

Iteration teaches students that failure and improvement are integral to the design process, not signs of inadequacy. When students experience firsthand that a revised design works better than the first, they internalize the value of persistence and evidence-based thinking. These dispositions transfer directly to academic resilience and problem-solving across subjects.

How do I prevent students from just randomly changing their design?

Require a written redesign plan before any rebuilding begins. The plan should identify the specific problem (from test data), the specific change to fix it, and a prediction. Reviewing these cards before students rebuild takes only a few minutes and transforms random tinkering into purposeful engineering. The evidence connection is what makes the activity educational rather than just enjoyable.

How does active learning support iterative design in 2nd grade?

Iteration is inherently active , students must physically rebuild, retest, and compare results. The critical active learning element is the structured reflection between iterations: requiring students to plan their change, predict the outcome, and then evaluate whether the prediction was correct. Without that reflective structure, iterating is just playing. With it, it is genuine engineering thinking.