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

Communicating Engineering Solutions

Students will present their engineering solutions, explaining their design process, results, and improvements.

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

About This Topic

Communicating engineering solutions is the capstone skill in the NGSS engineering design sequence (3-5-ETS1-2, 3-5-ETS1-3). Students learn that an engineering solution isn't complete until it has been clearly explained to an audience , and that explaining a design process reveals both its strengths and the reasoning behind it. This is not just a presentation skill; it's a professional engineering practice.

Third graders learn to structure an engineering explanation around four questions: What was the problem? What did we try? What did we learn from testing? What did we change and why? This structure maps directly onto the design process and gives students a framework for presenting to peers, younger students, parents, or community members.

Active learning formats for communication , peer critiques, structured presentations with audience feedback, compare-and-contrast reviews , push students to engage with each other's solutions rather than passively listening. Critiquing a peer's design against stated success criteria is itself a high-level thinking task that reinforces both the content and the communication standard. Students who have to explain their engineering choices in response to questions develop a much deeper understanding of their own design decisions.

Key Questions

1. Explain the engineering design process used to solve a specific problem.
2. Critique the effectiveness of a peer's engineering design by comparing it to the stated success criteria.
3. Justify why sharing and presenting a solution to an audience helps improve future engineering designs.

Learning Objectives

• Explain the steps of the engineering design process used to solve a given problem.
• Critique a peer's engineering solution by comparing its features to the established success criteria.
• Justify how presenting an engineering solution to an audience can lead to improvements in future designs.
• Compare and contrast two different engineering solutions for the same problem based on their effectiveness and efficiency.

Before You Start

Designing and Building a Solution

Why: Students must have already gone through the process of designing and building a solution to have something to communicate and present.

Identifying and Defining a Problem

Why: Understanding the initial problem is crucial for explaining the context and purpose of the engineering solution.

Key Vocabulary

Engineering Design Process	A series of steps engineers use to solve problems, including defining the problem, brainstorming solutions, designing, building, testing, and improving.
Success Criteria	Specific, measurable requirements that define what makes an engineering solution effective and successful.
Iteration	The process of repeating a design step, such as testing or modifying, to improve a solution.
Prototype	An early model or sample of a product built to test a design concept or process.

Watch Out for These Misconceptions

Common Misconception

Presenting a design means showing that it worked.

What to Teach Instead

A full engineering explanation includes failures and revisions, not just successes. Presenting only a successful final design omits the most informative part of the process. Audiences , especially engineering and scientific audiences , want to understand what was tried, what failed, and how that failure informed the final design. Students who hide failures in presentations are missing the professional norm.

Common Misconception

Critiquing a peer's design is the same as saying their design is bad.

What to Teach Instead

Engineering critique is evidence-based evaluation against shared criteria, not personal judgment. A critique that says "your design met criteria 1 and 2 but the test data shows it didn't meet criterion 3 , here's what the data says" is constructive and professional. Teaching students to frame critique in terms of criteria and evidence, not preference, makes peer review useful rather than hurtful.

Common Misconception

If you can explain how something works, you understand it.

What to Teach Instead

Surface-level explanation ("it holds weight because it's strong") doesn't demonstrate engineering understanding. Explanations that reference specific design features, test data, and the connection between design choices and performance are the target. The teach-back activity and criteria-based critique both push students toward this deeper level of explanation.

Active Learning Ideas

Engineering Showcase: Structured Presentations

Each group presents their design in a 3-minute structured format: problem statement, design solution, test results, revisions made. Audience members (other groups) use a feedback card with three prompts: one criterion your design clearly met, one question about your testing process, one suggestion. Presenters respond to questions before rotating to the next group.

45 min·Small Groups

Critique Protocol: Comparing to Success Criteria

Post each group's success criteria alongside their design and test results. Peer reviewers evaluate: did the design meet each criterion? For each criterion, mark yes/partially/no and cite specific evidence. Groups receive written critiques and respond in writing: "We agree with... We disagree with... because the data shows..." This models formal engineering review.

35 min·Pairs

Gallery Walk: Process Documentation

Groups create a 4-panel display (problem, design, testing, revision) and post it for a gallery walk. Each student visiting a display adds one sticky note: something they would do the same, or something they would do differently and why. Designers read the notes after the walk and discuss: did any feedback surprise you?

30 min·Whole Class

Teach-Back: Explain to a Younger Audience

Groups prepare a 2-minute explanation of their design for a partner class of younger students (or for each other, imagining a younger audience). Simplifying an explanation for a non-expert audience requires deep understanding , students often discover gaps in their own knowledge when they can't explain a step clearly. Debrief: what was hardest to explain, and why?

25 min·Small Groups

Real-World Connections

• Product designers at companies like Apple present new device concepts to marketing teams and executives, explaining the problem the device solves and how its features meet user needs.
• Civil engineers present bridge designs to city planning committees, detailing the materials used, structural integrity, and how the bridge will serve the community's transportation needs.
• Robotics engineers share their robot designs at competitions, explaining how their robot performs specific tasks and how they plan to improve it for future rounds.

Assessment Ideas

Peer Assessment

Students present their engineering solution. After each presentation, peers use a checklist to evaluate: Did the presenter clearly state the problem? Did they explain their design choices? Did they mention testing results? Peers then provide one specific suggestion for improvement.

Quick Check

Provide students with a scenario where an engineering solution failed. Ask them to write two sentences explaining what the engineer might have learned from testing and one change they would make to the design.

Discussion Prompt

Pose the question: 'Why is it important for engineers to share their work with others?' Facilitate a class discussion, guiding students to connect sharing with feedback, collaboration, and advancing technology.

Frequently Asked Questions

What should students include when explaining their engineering design process?

A complete engineering explanation covers four elements: the problem being solved (including criteria and constraints), the solution chosen and why it was selected over alternatives, the testing process and what the data showed, and revisions made based on test results. Students who can walk through all four elements demonstrate understanding of the full design cycle, not just the final product.

How do you teach students to give useful engineering critiques?

Anchor critique in the criteria established at the start of the design process. Teach students to ask: did this design meet criteria X? What evidence supports that judgment? A critique that references specific test data and named criteria is useful; a critique based on general impressions is not. Using a structured critique protocol (yes/partially/no for each criterion, with evidence) scaffolds this for third graders.

Why does presenting a design help future engineering work?

Presenting forces designers to articulate reasoning they may have applied intuitively. Questions from an audience reveal assumptions that weren't explained. Written or spoken critiques from peers identify issues the designer was too close to see. Engineering teams share design reviews precisely because outside perspectives improve outcomes , this is a professional practice students are learning at a foundational level.

How does active learning improve engineering communication skills?

Passive presentation (teacher-assigned reports) develops writing but not the interactive reasoning that engineering communication requires. Active formats , peer critique protocols, gallery walks with sticky-note feedback, teach-back to a different audience , require students to respond, defend, and revise in real time. This prepares students for the kind of collaborative design work they will do in later grades and in professional contexts.