Science · 1st Grade · Engineering and Design Solutions · Weeks 10-18

Improving and Redesigning

Students use test results to identify areas for improvement and redesign their solutions.

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

About This Topic

Engineers rarely get a design right on the first attempt. The value of testing is not just to confirm success but to identify exactly what needs to change and why. Standard K-2-ETS1-3 asks students to use test data to make design decisions, and this topic focuses on that improvement cycle. Students learn to look at their test results as a map that points toward specific revisions rather than as a verdict on their work.

Redesigning requires students to connect evidence to action. If a bridge collapsed in the middle, the fix is different than if it crumpled at the ends. Reading the test data carefully enough to diagnose where the design failed and then making a targeted change, rather than rebuilding everything from scratch, is a disciplined form of thinking that develops over time with practice.

Active learning supports this topic by putting students in genuine revision cycles where they test, analyze, change one thing, and test again. Peer discussion during this process is especially valuable: a partner who was not emotionally invested in the original design often spots the weak point more easily. Learning to receive and use specific, constructive feedback is a skill that active learning environments develop naturally and repeatedly.

Key Questions

1. Construct a revised design based on testing feedback.
2. Justify changes made to a design based on its performance.
3. Explain why engineers often go through multiple cycles of design and testing.

Learning Objectives

• Analyze test results to identify specific weaknesses in a designed solution.
• Revise a design by making targeted changes based on performance data.
• Justify design modifications by explaining how they address identified problems.
• Explain the iterative nature of the engineering design process, including multiple cycles of testing and redesign.

Before You Start

Designing and Building a Solution

Why: Students need prior experience creating an initial design before they can improve and redesign it.

Testing a Solution

Why: Students must have experience testing their designs to gather the data needed for improvement.

Key Vocabulary

Test Data	Information gathered from testing a design, showing how well it performed and where it had problems.
Redesign	To change or improve a design based on what was learned during testing.
Revision	A specific change made to a design to make it work better.
Performance	How well a design works or functions when it is tested.

Watch Out for These Misconceptions

Common Misconception

If a design failed, the best fix is to start completely over.

What to Teach Instead

Students often want to scrap everything after a failed test. Pointing to specific data from the test, such as 'the bottom folded but the sides stayed strong,' helps them see that parts of the design worked and those parts should be kept. Targeted revision is faster and teaches more than starting over.

Common Misconception

Adding more materials always makes a better redesign.

What to Teach Instead

Students frequently add more tape, paper, or layers when a design fails, assuming 'more' equals 'stronger.' Testing shows that weight or bulk can actually hurt performance. Keeping the testing fair, with the same amount of materials available for each version, helps students focus on strategy rather than quantity.

Common Misconception

Once a redesign is tested, the engineering process is finished.

What to Teach Instead

First graders sometimes treat the second test as final. Explaining that professional engineers may cycle through dozens of iterations and that each test generates new questions helps them see the design process as ongoing. Setting a class record for most productive iterations in a session can motivate students to embrace continuous improvement.

Active Learning Ideas

Inquiry Circle: Targeted Fix Lab

After a prior testing session, each pair identifies the single weakest point in their design from their recorded data. They make exactly one change to address it, document the change with a sketch, retest using the same procedure, and compare the before-and-after results. Pairs share whether their targeted fix worked and what they learned.

35 min·Pairs

Think-Pair-Share: What Changed and Why?

Show a 'before' sketch and an 'after' sketch of the same student design that was revised between two tests. Students identify what changed between the two versions, predict whether the change would help or hurt performance based on what they know, then pair to compare predictions before the teacher reveals the actual test results.

20 min·Pairs

Gallery Walk: Redesign Stories

Post paired display boards around the room showing a design's first test result alongside the revised design and its second test result. Students walk the gallery and for each display write what changed, why they think it changed, and one more change they might try. The class discusses patterns in successful redesigns.

25 min·Individual

Simulation Game: The Revision Round

The teacher sets up a design challenge such as building a cup holder from a single sheet of paper, lets students build and test a first version, then stops the class for a structured group analysis. Students share what went wrong at each table, the teacher collects observations on the board, and students redesign using the collective data before testing a second time.

45 min·Small Groups

Real-World Connections

• Car designers test crash test dummies to see how cars perform in accidents. They then use this data to redesign safety features like airbags and seatbelts to better protect passengers.
• Toy engineers test prototypes of new toys to see if they are fun and safe for children. If a toy breaks easily during testing, they will redesign it to be more durable before mass production.

Assessment Ideas

Quick Check

Show students a simple drawing of a failed design (e.g., a tower that fell over). Ask: 'What part of the tower do you think failed? What is one change you could make to fix it?'

Exit Ticket

Provide students with a simple data sheet from a test (e.g., 'Bridge held 2 pennies, then broke'). Ask them to write one sentence explaining what the data tells them about their bridge and one change they would make to improve it.

Peer Assessment

Have students show their redesigned solution to a partner. Ask: 'Tell your partner one change you made and why you made it. Did your partner's change help their design?'

Frequently Asked Questions

How do engineers decide what to change when a design fails?

Engineers read their test data carefully to find where the failure started. If a bridge collapsed in the center, they focus on making the center stronger. If a shelter kept rain out but was too heavy to carry, they look at reducing weight without losing coverage. Good engineers change one thing at a time so they know exactly which change caused any improvement.

Is it OK to copy a design improvement from a classmate?

Looking at what works in another design and adapting it for your own is not copying; it is exactly how real engineering works. Engineers share findings, read each other's research, and build on earlier designs all the time. The goal is to solve the problem, and using every available source of good ideas is part of the process.

How can active learning help students improve their designs?

The test-revise-retest cycle gives students repeated, low-stakes practice at using evidence to make decisions. Each iteration builds their ability to read data, form a hypothesis about what change will help, and verify it through testing. Active peer review during the redesign phase introduces students to the collaborative nature of real engineering and exposes them to perspectives that improve their own solutions.

What does it mean to iterate in engineering?

Iterating means going through the design-build-test-improve cycle more than once. Each time through the cycle, the design gets a little better because it is based on actual test results rather than just ideas. Engineers expect to iterate; the first prototype is almost never the best version, and each round of testing brings the design closer to solving the original problem.