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

Testing and Evaluating Solutions

Students test their models or prototypes and evaluate their effectiveness in solving the problem.

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

About This Topic

Building a prototype is only useful if students then test it against the problem it was supposed to solve. Standard K-2-ETS1-3 asks students to analyze data from tests of two objects designed to solve the same problem and compare the strengths and weaknesses of how each performs. For first graders, testing means setting up a fair comparison, observing what happens, and recording results in a way that can be discussed and compared with others.

Testing reveals whether a design solved the problem it was intended to address. A paper bridge that holds five blocks but collapses under a sixth provides specific data: how much weight it can support. Comparing that result to a competing design's performance gives students the analytical framework they need to make evidence-based claims about which design worked better and why.

Active learning is the engine of this topic. Students who build and test their own designs have a genuine stake in the results. When a structure fails, they want to know why. When they compare their test data with a partner's data, they are engaged in real scientific discourse. This authentic investment in the outcome drives deeper engagement with the evaluation process than any teacher-directed assessment could produce.

Key Questions

1. Evaluate how well a design solves the identified problem.
2. Analyze data collected during testing to identify strengths and weaknesses.
3. Differentiate between a successful test and a failed test.

Learning Objectives

• Compare the performance of two different designs for solving the same problem based on test data.
• Analyze data collected during testing to identify specific strengths and weaknesses of a design.
• Explain why a particular test result indicates success or failure in solving the identified problem.
• Identify criteria for evaluating the effectiveness of a prototype in meeting design requirements.

Before You Start

Designing Solutions

Why: Students need to have previously designed a solution to a problem before they can test and evaluate it.

Building Prototypes

Why: Students must be able to construct a model or prototype of their design to be able to test it.

Key Vocabulary

Prototype	A first model of something, built to test a design or idea before making the final version.
Test	An action or procedure to see how well something works or performs.
Data	Facts and information collected during testing, such as measurements or observations.
Evaluate	To judge or determine the value or worth of something based on specific criteria.
Criteria	Standards or rules used to judge or make a decision about something.

Watch Out for These Misconceptions

Common Misconception

A design that failed the test is a bad design that cannot be improved.

What to Teach Instead

First graders often equate a failed test with personal failure. Reframing test results as 'information we collected' rather than grades helps students see failure as a diagnostic tool. Asking 'what did the test tell us went wrong?' shifts the conversation from judgment to analysis, which is where the learning happens.

Common Misconception

You only need to test something one time to know if it works.

What to Teach Instead

One test can produce a result due to chance rather than design quality. Having students run two or three trials and compare results across trials teaches them that consistent performance, not a single lucky outcome, is what engineers look for. This is a developmentally appropriate introduction to reproducibility in science.

Common Misconception

The strongest or biggest design always wins the test.

What to Teach Instead

Students sometimes assume larger or heavier structures will always outperform smaller ones. Tests regularly produce counterintuitive results where a simpler, lighter design outperforms a heavy one. These surprises are productive learning moments that challenge assumptions and show students that evidence, not prediction, determines what works.

Active Learning Ideas

Simulation Game: The Bridge Load Test

Pairs build a paper bridge spanning two books. They add pennies one at a time, recording how many the bridge holds before collapsing. After testing, two pairs compare their results, describe which design held more weight, and identify one specific structural difference that might explain the difference in performance.

40 min·Pairs

Inquiry Circle: Two-Design Comparison

Small groups receive two different teacher-built prototypes of the same solution, such as two different windbreaks for a model house using different materials. They test both against the same wind source and record which prototype blocked more air, then analyze their data to identify the strength and one weakness of each design.

35 min·Small Groups

Think-Pair-Share: What Counts as a Fair Test?

The teacher presents a scenario in which two students tested their bridges by adding rocks of different sizes. Students think about why this is not a fair comparison, pair to generate a better testing rule, and share their proposed standard with the class to establish a class testing protocol.

15 min·Pairs

Gallery Walk: Test Data Boards

After a class testing session, student pairs post their results on a data board using a simple recording sheet. The class does a gallery walk to read each pair's data, identify the three highest-performing designs, and write one observation on a sticky note about what those top designs had in common.

25 min·Individual

Real-World Connections

• Toy designers test many prototypes of a new game before deciding which version is the most fun and easy to play. They collect feedback from children to see if the game meets their expectations.
• Engineers test different materials for building bridges to see which ones can hold the most weight. They analyze the results to choose the safest and strongest material for construction.

Assessment Ideas

Exit Ticket

Give students a simple chart showing test results for two ramps designed to roll a ball. Ask them to circle the ramp that rolled the farthest and write one sentence explaining why they chose it.

Discussion Prompt

Present students with a scenario: 'We designed a bird feeder to keep squirrels out. During testing, we saw squirrels could still reach the seeds. What does this test result tell us about our design?' Facilitate a brief class discussion.

Quick Check

Show students two different paper airplanes. Ask them to hold up one finger if the plane met the goal of flying straight and two fingers if it did not. Then, ask them to share one observation about why it flew or didn't fly straight.

Frequently Asked Questions

How do you make a test fair in 1st grade science?

A fair test changes only one thing at a time while keeping everything else the same. If testing which paper bridge design holds more weight, both bridges should be the same width, span the same gap, and be tested with the same weights added in the same way. Changing multiple things at once makes it impossible to know which change caused the result.

What should students record during a test?

Students should record what they did, what happened, and how much or how many, using numbers where possible. For a bridge test, this means recording the number of pennies the bridge held and whether it collapsed suddenly or gradually. Specific, observable details give students real data to compare and discuss rather than vague impressions.

How can active learning help students evaluate their designs?

When students build and test their own designs, they care about the results in a personal way that drives real analysis. A student whose bridge held five pennies more than a partner's wants to understand why. That curiosity makes the comparison process meaningful. Active gallery walks of test results extend this further by showing students that their data is part of a larger class dataset worth examining.

What does it mean when a design partially works?

Partial success is very common in engineering and is an important data point. A shelter that keeps rain off but lets in cold air has solved one part of the problem and not another. Students can identify which specific part of the problem was solved and which was not, then focus their redesign on the unresolved part. Partial results are more informative than a simple pass-fail outcome.