Developing and Testing Prototypes

Active learning sticks with this topic because students need to feel the tension between expectation and reality when prototypes fail. When they test their own designs, the emotional and intellectual investment in the outcome makes the revision process meaningful. Hands-on testing also reveals hidden variables and design flaws that lectures cannot convey.

• 3rd Grade
• Science
• 4 activities
• 15 min–45 min

Learning Objectives

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

Inquiry Circle

⏱ 30 min·Small Groups

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.

Prepare & details

Describe what steps you would take when a prototype does not work as expected during testing.

Facilitation Tip: During Structured Failure Report, remind students to focus on the failure point and the cause, not just the broken part.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Inquiry Circle

⏱ 45 min·Small Groups

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.

Prepare & details

Explain how testing a small model before building the real thing saves time and materials.

Facilitation Tip: For Side-by-Side Comparison, set a timer so students notice subtle differences in how each prototype handles the same test.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Think-Pair-Share

⏱ 15 min·Pairs

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?

Prepare & details

Compare two prototype test results to determine which design should be improved and how.

Facilitation Tip: In Think-Pair-Share, assign roles: one student explains the failure, one suggests a fix, and they switch for the next round.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Inquiry Circle

⏱ 35 min·Small Groups

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.

Prepare & details

Describe what steps you would take when a prototype does not work as expected during testing.

Facilitation Tip: During Iteration Sprint, limit changes to one variable at a time so students can trace cause and effect clearly.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Teaching This Topic

Teachers should normalize failure by naming it as part of the process early and often. When students feel safe to break things, they test more thoroughly and learn more. Avoid rushing through the emotional moment of failure; instead, pause and ask students to describe what they see and feel before moving to fixes. Research shows that middle-grade students benefit from explicit reflection prompts after testing to link emotions to data.

What to Expect

Students will move from seeing failure as something to avoid to seeing it as data that guides the next iteration. They will articulate specific changes with evidence from tests, and revise designs without stigma. Success looks like clear connections between test results, identified weaknesses, and purposeful design improvements.

Watch Out for These Misconceptions

Common Misconception

During Structured Failure Report, watch for students who describe the failure only in terms of 'it broke' without naming the force or material property that caused it.

What to Teach Instead

Prompt students to complete the sentence: 'The ______ broke when we applied ______ because ______.' Provide a word bank: compression, tension, shear, brittle, flexible.

Common Misconception

During Side-by-Side Comparison, students may assume that if one prototype looks sturdier, it must be better without testing it.

What to Teach Instead

Ask students to set up identical tests and record side-by-side observations using a shared data table with columns for load, observation, and failure point.

Common Misconception

During Think-Pair-Share, students may frame revision as an admission of error rather than a step toward improvement.

What to Teach Instead

Give students a script: 'The test showed ______, so we decided to change ______ because ______.' Provide an example using a prior class prototype to model this language.

Assessment Ideas

Quick Check

After Structured Failure Report, collect the labeled drawings and one-sentence explanations. Look for evidence that students identified the failure point and connected it to a specific force or material property.

Discussion Prompt

During Side-by-Side Comparison, listen for students to articulate two specific differences between the prototypes and explain how those differences affected performance under the same test conditions.

Peer Assessment

After Think-Pair-Share, ask partners to complete a feedback form with two columns: 'What worked' and 'What could be improved,' with space for one reason for each.

Extensions & Scaffolding

• Challenge: Ask students to test their revised prototype at twice the original force and document the new failure point.
• Scaffolding: Provide a sentence stem for students to complete: 'The test showed that the ______ bent because ______. To fix it, I will ______.'
• Deeper exploration: Have students research a real engineering failure, trace the design choices that led to it, and present findings in a mini-case study.

Key Vocabulary

prototype	A 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.
test	An experiment or trial to check the performance, accuracy, or reliability of something. In engineering, tests reveal how a design performs under specific conditions.
failure point	The 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.
revision	The process of changing or improving a design based on the information learned from testing. It involves making modifications to address failure points.