Science · 3rd Grade · Engineering Design and Innovation · Weeks 28-36

Building and Testing Prototypes

Students will construct prototypes of their chosen designs and conduct controlled tests to gather data on their performance.

• Common Core State Standards
• 3-5-ETS1-3

About This Topic

Building and testing a prototype brings the engineering design process from abstract planning into physical reality. NGSS standard 3-5-ETS1-3 asks students to plan and carry out fair tests to identify failure points of a design and suggest improvements. Third graders often think of testing as either "it works" or "it doesn't" , this topic teaches them to treat failure as data.

A prototype is not the final product; it's a physical hypothesis. When a prototype fails a test, students have learned something specific about their design: where the weak point is, what conditions break it, which material didn't perform as expected. This reframe , from failure as disappointment to failure as information , is one of the most important shifts engineering education can achieve at this grade.

Active learning through hands-on prototype construction and controlled testing is the core of this topic. The physical experience of building something, watching it perform (or not), and explaining what happened produces richer understanding than any description of the testing process could. Students who have never seen a prototype fail in an instructive way haven't yet understood what prototyping is for.

Key Questions

1. Construct a prototype based on a chosen design plan.
2. Analyze what can be learned from a design that fails during testing.
3. Explain why it is helpful to build a small model before the real thing.

Learning Objectives

• Construct a functional prototype based on a given design plan for a specific engineering challenge.
• Analyze test data to identify at least two specific reasons why a prototype failed to meet design criteria.
• Explain the value of building a small-scale model before constructing a full-sized product, citing at least one example.

Before You Start

Designing Solutions

Why: Students need to have experience creating a plan or drawing for a solution before they can build a prototype of it.

Identifying Problems

Why: Understanding the need for a solution and the specific problem it solves is essential before designing and testing a prototype.

Key Vocabulary

Prototype	A first model of a design that can be tested to see if it works. It is not the final product.
Controlled Test	A test where only one part or condition is changed at a time to see how it affects the outcome. This helps identify what caused a result.
Failure Point	The specific part of a design or the specific condition that causes a prototype to stop working or break.
Data	Information collected during tests, such as measurements or observations, that helps engineers understand how a design performs.

Watch Out for These Misconceptions

Common Misconception

If a prototype fails, the design is bad and should be thrown out.

What to Teach Instead

Failure is expected and informative, not a verdict. A prototype that fails in a specific way tells the engineer exactly what needs to change. Engineers rarely get designs right on the first prototype , iterative testing and revision is the designed-in method. Reframing class discussions to treat failure as useful information shifts students' relationship to testing.

Common Misconception

Testing a small model doesn't tell you much about a full-size version.

What to Teach Instead

Small-scale models reveal structural principles, material behavior, and design weaknesses that apply at full scale. While some properties don't scale perfectly (like buoyancy), the relative performance of different design choices is generally consistent. Engineers use scale models precisely because they're cheaper and faster to build and test than full prototypes.

Common Misconception

The goal of testing is to prove your design works.

What to Teach Instead

The goal of testing is to find out where and how a design can be improved. Testing to confirm success produces less useful information than testing to find failure points. Controlled tests that gradually increase stress until failure point generate the most actionable design data. Students who only test under easy conditions miss the purpose of prototyping.

Active Learning Ideas

Build and Break: Controlled Prototype Testing

Groups build their chosen design from a previous brainstorming session and define their test conditions before testing (how much weight, how much wind, how much water). Run the test, record results, then deliberately increase the intensity until the prototype fails. Ask: "At what point did it fail? What broke first?" This identifies the design's actual weak point.

50 min·Small Groups

Failure Analysis Discussion: What Can We Learn?

After a round of prototype testing, hold a class failure gallery: each group shares one thing that didn't work as expected and one thing they learned from it. Use sentence stems: "Our design failed when... This tells us that... Our next version will..." Normalize failure as part of the process, not evidence of poor work.

20 min·Whole Class

Think-Pair-Share: Why Test Small First?

Show images or videos of engineers testing small models of large structures (bridge load tests, airplane wind tunnel models, crash test vehicles). Ask: "Why would an engineer bother building a small version first?" Pairs discuss, then share. Build a class list of reasons: saves materials, identifies problems early, faster to modify small models.

15 min·Pairs

Data Recording Lab: Testing Two Prototypes

Provide a structured data sheet with columns: Design Features, Test Condition, Observed Result, Conclusion. Groups test two versions of their prototype under identical conditions and record results. Pairs compare data sheets with another group and discuss: what counts as a fair test?

40 min·Small Groups

Real-World Connections

• Toy designers build prototypes of new toys, like action figures or board games, and test them with children to see if they are fun and safe before mass production.
• Car engineers build prototype vehicles to test new features, such as improved fuel efficiency or crash safety, under specific conditions before manufacturing the final car model.
• Architects create small-scale models of buildings to show clients how the finished structure will look and to identify potential construction issues before breaking ground.

Assessment Ideas

Quick Check

After students build their prototypes, ask them to complete a short worksheet. Include questions like: 'What is one part of your prototype you think might break? Why?' and 'What is one thing you will change in your design based on what you think might happen during testing?'

Discussion Prompt

Facilitate a class discussion after testing. Ask: 'Tell us about a time your prototype did not work as expected. What specific observation did you make? What does this observation tell you about your design?' Encourage students to use the term 'failure point'.

Exit Ticket

Students write on an index card: 'One reason it is helpful to build a model first is ______. For example, if I were building a bridge, a model would help me see ______.'

Frequently Asked Questions

What's the difference between a prototype and a final product?

A prototype is a test version of a design, built to identify problems before committing to a final version. Prototypes are expected to fail , that's their job. A final product has been through multiple rounds of prototype testing and revision. In classroom engineering, students rarely reach a "finished" design; instead, they experience the iterative testing process that leads toward one.

How do you run a fair test with a prototype?

A fair test changes only one variable at a time while keeping everything else the same. Before testing, students define exactly what they'll measure, what conditions they'll use, and how they'll record results. Testing the same prototype under different conditions in the same way allows comparison. If test conditions vary between trials, results can't be reliably compared.

What should students record when testing prototypes?

Students should record: the specific test conditions (weight, force, water level), what happened during the test, where failure occurred if it failed, and what that suggests about the design. Structured data sheets help third graders record systematically. The record should be detailed enough that another person could repeat the test under the same conditions.

How does active learning improve prototype building and testing?

Physical construction and testing produce learning that description alone cannot. When students build with their hands, make real materials decisions, observe unexpected failures, and analyze results with peers, they develop an intuitive understanding of design tradeoffs. Failure analysis discussions , where groups share what broke and what they learned , build a classroom culture of inquiry that supports the full engineering design cycle.