The Engineering Design Process for Student Projects
By the School Project Lab Team · Updated · 5 min read · High School (9–12)
In this guide
The engineering design process is a step-by-step cycle engineers use to solve problems: define the problem, research, brainstorm, build a prototype, test it, and improve it based on what you learn. Unlike a single experiment, it's meant to repeat until the design meets its goals. This guide explains each step with practical examples so teens can run a real design project and parents know how to support it safely.
Engineering Design vs. the Scientific Method
Students often learn the scientific method first, so it helps to see the difference. The scientific method asks a question about how something works and tests a hypothesis. The engineering design process starts with a problem and ends with a solution that's been built and tested.
For example, a scientific question might be "Does the shape of a boat hull affect how much weight it can hold?" An engineering problem might be "Design a small boat from aluminum foil that holds as many coins as possible without sinking." Both use data, but engineering focuses on creating something that works and making it better.
Different textbooks and programs describe the steps in slightly different ways, sometimes with five steps, sometimes with eight. The core ideas are the same, and your teacher may prefer a particular version.
The Steps of the Engineering Design Process
1. Define the Problem
Write a clear problem statement. Who has the problem? What exactly needs to be solved? A good statement is specific: "Students with limited hand strength struggle to open standard water bottles" is much better than "Make something helpful."
Then list your criteria (what the design must do) and constraints (limits like budget, size, materials, and time). For example: must open a bottle with one hand, must cost under ten dollars to build, must fit in a backpack.
2. Research
Find out what already exists. How have others tried to solve this? What works and what doesn't? Look at existing products, read articles, and if possible, talk to people who have the problem. Their feedback is gold.
3. Brainstorm Solutions
Generate many ideas before judging any of them. Sketch quickly and aim for quantity. Wild ideas sometimes lead to practical ones. A brainstorm of fifteen rough sketches is far more useful than one careful drawing.
4. Choose the Best Idea
Compare your ideas against the criteria and constraints. A simple decision matrix works well: list ideas down the side, criteria across the top, and score each idea from one to five. The highest total isn't automatically the winner, but it gives you a reasoned starting point.
5. Build a Prototype
A prototype is a test version, not a finished product. Build it with inexpensive materials like cardboard, craft sticks, tape, and foam. The goal is to learn quickly, not to make it beautiful.
Safety matters here. Use hot glue, cutting tools, and any power or battery-operated equipment only with adult supervision, and wear safety glasses when cutting or drilling. Low-temperature glue guns and kid-safe saws are good choices for many builds.
6. Test and Collect Data
Decide in advance how you'll measure success. If your criterion is "holds at least two pounds," test it with real weights. Run several trials and record the results in a table. Note exactly where and how the prototype fails. Failure isn't a setback; it's information.
7. Improve and Redesign
Use your data to make specific changes. Change one major thing at a time when possible, so you know what caused the improvement. Then test again. Most strong projects go through several cycles of building, testing, and improving.
8. Communicate Your Results
Share what you built, how you tested it, what you changed, and why. A display board, slideshow, or written report should show the problem, criteria, sketches, photos of each prototype, data tables, and final results. Showing earlier failed versions often impresses teachers and judges, because it proves you followed the process.
Parent tip: When your teen's prototype breaks, resist the urge to fix it. Ask instead, "What did you learn from that?" and "What will you change next?" Those two questions turn frustration into the kind of thinking engineers rely on.
Example Project Walkthrough
Here's how a full project might look for a high school student.
Problem: Plants on a classroom windowsill dry out over long weekends.
Criteria and constraints: Keep soil moist for at least four days, use no electricity, cost under fifteen dollars, fit on a standard windowsill.
Research: The student looks at self-watering planter designs and learns about wicking, where water travels through absorbent material.
Brainstorm: Ideas include an upside-down bottle drip, a cotton-rope wick from a reservoir, and a sponge layer under the soil.
Prototype and test: The student builds all three with recycled bottles and measures soil moisture daily using a simple moisture meter. The bottle drip empties too fast; the wick works best but needs a larger reservoir.
Improve: The student redesigns with a bigger reservoir and a thicker wick, retests, and meets the four-day goal.
Communicate: The final board includes the problem, sketches, photos of all versions, a moisture data table, and lessons learned.
More Project Ideas to Try
If you need a starting point, these problems work well with the engineering design process and use safe, low-cost materials:
- Design a phone stand that holds a device at three different viewing angles.
- Build a container that keeps an ice cube from melting as long as possible.
- Create a bridge from craft sticks that holds the most weight for its own mass.
- Design a better backpack organizer for heavy textbooks.
- Build a small, wind-powered vehicle with a paper or fabric sail.
- Create a tool that helps someone with limited mobility pick up small objects.
The best projects come from problems the student has noticed in their own life, school, or community. A real problem makes the research more meaningful and the final presentation more convincing.
Quick Checklist
Tap the boxes as you go — progress saves on this device only.
- Write a clear problem statement
- List criteria and constraints
- Research existing solutions
- Sketch at least ten ideas
- Pick the best idea with a score chart
- Build a simple prototype
- Wear safety glasses when cutting
- Use hot glue only with an adult
- Test and record data
- Improve and test again
- Photograph every version
- Present the problem, process and results
Time and Cost Estimate
| Item | Estimate |
|---|---|
| Prep time (problem, research, sketches) | 3 to 6 hours |
| Build and test cycles | 6 to 15 hours |
| Presentation prep | 2 to 4 hours |
| Typical cost | $10 to $50, depending on materials |
| Difficulty | Moderate to challenging |
Costs stay low when you prototype with recycled and craft materials. Save more expensive materials for the final version once your design is proven.
Keeping the Work Student-Led
The real value of an engineering project is the problem-solving the student practices. Parents can supervise tool use, help source materials, and ask good questions, but the ideas, decisions, and building should come from the teen. A rough, honest prototype the student truly designed is far more meaningful, and usually more impressive to teachers, than a polished product built by an adult.
Frequently asked questions
How is the engineering design process different from the scientific method?
The scientific method tests a hypothesis to answer a question about how the world works. The engineering design process solves a problem by designing, building, testing and improving a solution.
How many prototypes should I build?
There is no fixed number, but most good projects include at least two or three versions. Each round of testing should lead to a specific improvement you can explain.
Can I use the engineering design process for a science fair?
Many science fairs accept engineering projects, sometimes in a separate category. Check your fair's official rules and ask your teacher how engineering entries are judged.