Science · 3rd Grade

Active learning ideas

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.

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

• 15–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Outdoor Investigation Session
• 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.

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.

What to look for

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.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

Activity 02

• Outdoor Investigation Session
• 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.

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.

What to look for

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.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

Activity 03

• 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?

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.

What to look for

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.'

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

Activity 04

• Outdoor Investigation Session
• 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.

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.

What to look for

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.

• Remember
• Understand
• Analyze
• Social Awareness
• Self-Awareness
• Decision-Making

A few notes on teaching this unit

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.

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

• 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.

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

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

  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.

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

  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.

---

Methods used in this brief

• Outdoor Investigation Session
• Think-Pair-Share