Analyzing Test Results

Active learning works because second graders build confidence in their own reasoning when they see data with their eyes and talk it over with peers. Turning numbers and observations into clear statements about what worked and what did not gives students concrete evidence that their ideas matter in the engineering process.

• 2nd Grade
• Science
• 3 activities
• 15 min–25 min

Learning Objectives

1. Analyze test data to identify specific measurements that indicate prototype success or failure.
2. Compare the actual performance of a prototype to its intended design goals using collected evidence.
3. Evaluate the strengths and weaknesses of an initial design by referencing specific test results.
4. Explain how test results provide evidence for design modifications.

Case Study Analysis

⏱ 20 min·Small Groups

Analysis Chart: Expected vs. Actual

Provide each group with a two-column chart: 'What We Expected' and 'What Actually Happened.' Groups fill in each row for each element of their test (strength, stability, appearance, function). A third column, 'What This Tells Us,' prompts students to interpret the gap between expectation and result as information for improvement rather than as failure.

Prepare & details

Explain what the test results reveal about the prototype's performance.

Facilitation Tip: During Analysis Chart: Expected vs. Actual, model how to circle one result and trace a finger back to the matching design feature so students connect data points to physical parts.

Setup: Groups at tables with case materials

Materials: Case study packet (3-5 pages), Analysis framework worksheet, Presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Gallery Walk

⏱ 25 min·Whole Class

Gallery Walk: Strengths and Questions

Groups display their prototype and test data for a gallery walk. Visitors use two-color sticky notes: one color for a strength they notice, one color for a question they have about the results. Groups return to read feedback and discuss: do the visitor questions reveal something they had not considered about their own results?

Prepare & details

Compare the actual performance of the prototype to the intended outcome.

Facilitation Tip: During Gallery Walk: Strengths and Questions, stand near each poster for 30 seconds to overhear conversations and jot one phrase that captures how students are reasoning about the evidence.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Think-Pair-Share

⏱ 15 min·Pairs

Think-Pair-Share: Evidence Only

After analyzing results, each student writes one conclusion about their design's performance using only evidence from the test data (no 'I think' or 'I feel' statements). Partners share conclusions and check each other: is there actual data supporting this claim? This focused exercise builds the habit of grounding engineering conclusions in evidence.

Prepare & details

Assess the strengths and weaknesses of the initial design based on evidence.

Facilitation Tip: During Think-Pair-Share: Evidence Only, supply sentence stems on the board such as 'The test showed that… because…' so students practice stating evidence before they share with the group.

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

Teaching This Topic

Teachers approach this topic by making data feel tangible: students mark expected versus actual outcomes on a shared chart, then physically move to different stations to discuss strengths. Avoid rushing to solutions; instead, ask 'What does this number tell us?' repeatedly to build evidence-based talk. Research shows that second graders’ analytical language grows when they first describe what happened, then explain why it matters.

What to Expect

Successful learning looks like students naming specific features that matched or missed their predictions and suggesting at least one actionable improvement. They should use vocabulary such as 'expected,' 'actual,' 'strength,' and 'question' when they speak and write about the test results.

Watch Out for These Misconceptions

Common Misconception

During Analysis Chart: Expected vs. Actual, watch for students who skip the row when the actual matches the expected because they think no learning happens there.

What to Teach Instead

Pause the class and ask everyone to point to one row where actual matched expected, then prompt students to explain which specific design choice made that match happen and how that feature could be used elsewhere.

Common Misconception

During Gallery Walk: Strengths and Questions, watch for students who label every feature as 'good' without naming what made it work or what data supports that judgment.

What to Teach Instead

Hand each student a sticky note with the prompt 'I know this was a strength because…' and require them to fill in one piece of evidence before they move to the next poster.

Assessment Ideas

Exit Ticket

After Analysis Chart: Expected vs. Actual, give students a half-sheet with a simple data table (e.g., bridge held 5 pennies) and ask them to write one sentence explaining what the results tell them about the bridge's strength and one suggestion for improvement.

Discussion Prompt

During Gallery Walk: Strengths and Questions, circulate and ask each small group two questions: 'What evidence shows this was a strength?' and 'What evidence shows where it fell short?' Listen for students to point to specific data points on the chart.

Quick Check

After Think-Pair-Share: Evidence Only, show students a picture of their tested prototype and ask them to point to one part and explain, based on test results, why it was a strength or a weakness.

Extensions & Scaffolding

• Challenge: Ask early finishers to propose a new test that would check their improvement idea and sketch the modified prototype.
• Scaffolding: Provide a word bank with terms like 'held,' 'bent,' 'rolled,' and 'dropped' to help students write their analysis sentences.
• Deeper exploration: Invite students to compare their results with a partner’s and create a class list of patterns they notice across multiple tests.

Key Vocabulary

Prototype	A first model of a new invention or design that can be tested to see if it works.
Test Results	Information gathered from testing a prototype, showing how well it performed.
Performance	How well a prototype works or functions during a test.
Evidence	Facts or information that show whether something is true or correct, like measurements from a test.
Design Goal	What the inventor wanted the prototype to do or achieve, like holding a certain number of objects.