Skip to content
Engineering Design and Innovation · Weeks 28-36

Developing and Testing Prototypes

Students will create models and run controlled tests to see where a design fails.

Need a lesson plan for Science?

Generate Mission

Key Questions

  1. Describe what steps you would take when a prototype does not work as expected during testing.
  2. Explain how testing a small model before building the real thing saves time and materials.
  3. Compare two prototype test results to determine which design should be improved and how.

Common Core State Standards

3-5-ETS1-23-5-ETS1-3
Grade: 3rd Grade
Subject: Science
Unit: Engineering Design and Innovation
Period: Weeks 28-36

About This Topic

Developing and testing prototypes sits at the heart of NGSS standards 3-5-ETS1-2 and 3-5-ETS1-3, asking students to create physical models, run controlled tests, and use results to inform revision. The emphasis in this topic is on what happens when a prototype doesn't perform as expected , and how that outcome drives the design process forward rather than ending it.

Third graders learn to distinguish between a failed test (which generates data) and a failed process (giving up without learning anything). A prototype that collapses under load, leaks, or tips over has done exactly what a prototype is supposed to do: reveal a weakness before resources are invested in a full build. Students who can articulate what they learned from a failed test are demonstrating genuine scientific and engineering thinking.

Small-scale model testing builds judgment about materials, structures, and mechanisms that transfers to more complex problems. Active learning is the natural mode for this topic , students need to physically experience the test-fail-revise cycle, not just read about it. Peer comparison of test results adds an important dimension, as different groups often find different failure points in similar designs.

Learning Objectives

  • Design a simple model to test a specific engineering design problem, such as a bridge that can hold weight.
  • Analyze test results from a prototype to identify specific points of failure and explain why they occurred.
  • Compare the outcomes of two different prototype tests and recommend specific improvements for one design.
  • Explain how testing a small-scale model before full construction can save time and resources.

Before You Start

Introduction to the Engineering Design Process

Why: Students need a basic understanding of the steps in the engineering design process, including identifying a problem and brainstorming solutions, before they can test and revise prototypes.

Properties of Materials

Why: Understanding how different materials behave (e.g., strength, flexibility) is crucial for students to predict and analyze how their prototypes will perform during testing.

Key Vocabulary

prototypeA first model of a new product or invention that can be tested and studied. It is used to see if the design works before making the final version.
testAn experiment or trial to check the performance, accuracy, or reliability of something. In engineering, tests reveal how a design performs under specific conditions.
failure pointThe specific part or characteristic of a prototype that causes it to not work as intended during a test. Identifying these points is key to improvement.
revisionThe process of changing or improving a design based on the information learned from testing. It involves making modifications to address failure points.

Active Learning Ideas

See all activities

Structured Failure Report: What Broke and Why

After prototype testing, each group completes a structured failure report (even if the design succeeded): What did we test? What did we expect? What actually happened? What does this tell us about our design? Groups share reports in a whole-class gallery, identifying common failure modes across different designs.

30 min·Small Groups
Generate mission

Side-by-Side Comparison: Two Prototypes, Same Test

Pairs of groups test two different prototype designs under identical controlled conditions and record results on a shared comparison chart. They then analyze: which performed better, on which measure, and why? Groups must cite specific test data to support their comparison rather than general impressions.

45 min·Small Groups
Generate mission

Think-Pair-Share: The Expensive Lesson

Present a scenario: an engineering firm built a full-size bridge before testing a model. The bridge failed and cost $10 million. Ask: "What would have been different if they had tested a model first?" Pairs discuss, then share. Connect to the classroom: what does testing a small model before the real thing save?

15 min·Pairs
Generate mission

Iteration Sprint: Fix One Thing

After identifying the primary failure point from testing, give groups 10 minutes to make exactly one change to their prototype design (no redesigning from scratch). Test again under the same conditions. Record: did the change improve performance? By how much? This isolates the effect of a single design variable.

35 min·Small Groups
Generate mission

Real-World Connections

Car designers build and crash small-scale models of vehicles to test safety features and identify weaknesses before manufacturing full-sized cars. This saves millions of dollars and prevents potential injuries.

Civil engineers test models of bridges and buildings in wind tunnels or under simulated loads. This helps them ensure structures are safe and can withstand environmental stresses before construction begins in cities like Chicago or New York.

Watch Out for These Misconceptions

Common MisconceptionIf the prototype passed the test, it doesn't need to be changed.

What to Teach Instead

Passing one test at one intensity level doesn't mean a design is optimal. Engineers ask: at what point does it fail? Could it be lighter, cheaper, or simpler and still pass? Even successful prototypes go through iterative improvement. Asking students to deliberately stress-test a design that "passed" often reveals improvement opportunities.

Common MisconceptionTesting a model and testing the real thing will give the same results.

What to Teach Instead

Scale models are useful but imperfect representations. Some material properties and physical forces don't scale linearly. Engineers know this and use scale testing to identify relative performance differences between designs, not to precisely predict full-scale behavior. This limitation of models is itself an important scientific concept.

Common MisconceptionWhen you change a prototype after testing, you're admitting you made a mistake.

What to Teach Instead

Revision based on evidence is the goal of the design process, not an admission of error. Engineers expect to revise designs , the question is not whether to change but what to change and why. Students who see iteration as failure avoidance rather than evidence-based improvement tend to avoid testing their designs under real stress.

Assessment Ideas

Quick Check

After students test their prototypes, ask them to draw their model and label one part that broke or bent. Then, have them write one sentence explaining why that part failed.

Discussion Prompt

Pose the question: 'Imagine your bridge prototype collapsed. What are two specific things you learned from that test that will help you build a better bridge next time?' Listen for students to connect the collapse to specific design choices or material weaknesses.

Peer Assessment

Have students share their prototype test results with a partner. Prompt them with: 'Point to one thing your partner's prototype did well and one thing that could be improved. Explain why you think that part needs improvement.'

Ready to teach this topic?

Generate a complete, classroom-ready active learning mission in seconds.

Generate a Custom Mission

Frequently Asked Questions

What steps should students take when a prototype fails during testing?
First, record exactly what happened: where the failure occurred, under what conditions, and what changed at the moment of failure. Then analyze: is this a materials problem, a structural problem, or a design concept problem? Generate 2-3 possible fixes that address the specific failure point. Test one change at a time so you know which change made the difference.
How does testing a small model save time and materials?
Small models use less material, fail faster, and can be rebuilt quickly. Identifying a design flaw in a 30-cm cardboard model costs far less than discovering the same flaw after building a full structure. In the classroom, this translates to more iteration cycles in the same amount of time , which produces stronger final designs and more learning.
How do you compare two prototype test results fairly?
Test both prototypes under identical conditions: same materials for the test medium, same measurement method, same number of trials. Record specific data (weight held, water level at failure, distance traveled) rather than general impressions. Use a comparison chart to identify which prototype performed better on each criterion, and note whether the differences were large or small.
How does active learning help students understand prototype testing?
The physical experience of testing , watching a structure buckle, measuring how much weight a bridge holds, timing how long waterproofing lasts , produces evidence that students can reason from directly. Structured failure reports and side-by-side comparisons require students to articulate conclusions in engineering terms. Peer comparison adds perspectives that individual testing misses and prepares students for collaborative engineering work.