Why Do Engineers Test and Improve?
Have you ever built something and thought, "Hmm, I can make this better"? That is exactly what engineers do every single day! Engineers are people who design and build things to solve problems. But here is a secret: their first try almost never works perfectly. They have to test their designs and then make changes to improve them.
Throughout history, inventors and engineers have used testing and improving to create amazing things. Let's look at some cool examples!
All of these inventors asked the same big question: "What did my test results tell me, and how can I use that information to make my design better?" That is exactly what you will learn in this lesson!
Core Ideas About Testing and Improving
When engineers want to solve a problem, they follow a process. First they design a solution, then they build it, then they test it. Testing means trying out the design to see how well it works. After testing, they look at the results (what happened during the test) to figure out what to change. Here are the big ideas you need to know.
Test Results Are Clues
Failure Is Helpful
Change One Thing at a Time
Compare to the Goal
Test Again After Improving
The Design Cycle — A Visual Guide
Engineers follow a cycle when they design things. It goes around and around because they keep improving! The diagram below shows the Engineering Design Cycle. Notice how "Test" leads to "Improve" — that is the focus of our lesson today.
Look at the arrows in the diagram. After you test your design, the arrow leads to improve. Then the arrow goes all the way back to the beginning. This means you can go through the cycle as many times as you need to make your design great!
How Do You Use Test Results to Improve?
So your test is done. Now what? You need to look carefully at your test results and figure out what they are telling you. Here is a step-by-step way to do that.
Step-by-Step: From Test Results to Improvements
- Look at what happened. Write down or draw what you saw during the test. Did your design do what you wanted?
- Find the problem. If something went wrong, figure out which part caused the problem. Was it too heavy? Too short? Not strong enough?
- Think of a change. Come up with one idea for how to fix the problem. Remember, change only one thing at a time!
- Make the change. Rebuild or adjust your design with the improvement you thought of.
- Test again! Run your test one more time to see if the change helped. If it did not, go back and try a different change.
Let's say you built a ramp for a toy car, and your goal was for the car to roll at least 5 feet. Your test showed the car only rolled 3 feet. Your test result (3 feet) tells you the ramp needs a change. Maybe you make the ramp taller so the car goes faster. Then you test again and measure how far the car goes this time.
What Kinds of Improvements Can You Make?
When your test results show a problem, there are different kinds of changes you can try. The diagram below shows three main types of improvements engineers think about.
| Test Result (Problem) | Type of Change | Example Improvement |
|---|---|---|
| The tower fell over | Change the shape | Make the base wider |
| The boat sank | Change the materials | Use tin foil instead of paper |
| The pieces kept falling apart | Change the method | Use tape instead of just balancing |
| The car only rolled 2 feet | Change the size | Make the ramp taller |
Worked Example: The Paper Bridge Challenge
Let's walk through a real example together! Imagine your class has a challenge: build a bridge out of paper that can hold at least 10 pennies. Let's see how one student uses test results to improve their design.
Good Improvements vs. Not-So-Good Improvements
Not all improvements are created equal! Some changes are smart because they are based on what you learned from your test. Other changes are just random guesses. Let's compare the two.
| Good Improvement ✅ | Not-So-Good Improvement ❌ |
|---|---|
| Based on what the test results showed | A random guess with no connection to the test |
| Changes one thing at a time so you can track what helps | Changes many things at once so you cannot tell what helped |
| Focuses on the part that failed | Changes a part that was already working fine |
| Uses numbers from the test to set a new goal | Does not measure or compare results |
| Tests again after making the change | Assumes the change worked without testing |
How Real Engineers Improve Designs
You might think that improving designs is just something you do in school. But real engineers in the real world do this every day! Let's see how the testing-and-improving process you are learning connects to what grown-up engineers do.
| What You Do in Class | What Real Engineers Do |
|---|---|
| Build a paper bridge and test how many pennies it holds | Build a model bridge and test how much weight it can carry safely |
| Write down your test results in a notebook | Record test data on computers with special software |
| Change the shape or material and test again | Create a new version (called a prototype) and run more tests |
| Go through the design cycle 2–3 times | Go through the design cycle hundreds of times over months or years |
| Share your improvement ideas with your group | Share test results with a whole team of engineers and scientists |
A company that makes sneakers might test 50 different designs before picking the best one. Car companies crash-test cars and then improve the safety features. Video game designers test their games with real players and fix anything that is confusing or buggy. The idea is always the same: test, learn, improve, repeat.
Practice Problems
Now it is your turn! Read each problem and think about how you would use test results to suggest improvements. Try to answer each one before looking at the answer.
Lesson Summary
In this lesson, you learned that engineers test their designs and use the test results to figure out what to change. The Engineering Design Cycle goes around and around: Ask, Design, Build, Test, and Improve. When you improve, you can change the materials, change the shape or size, or change the method you use to build.
The most important rules to remember: always change one thing at a time so you know what helped, use numbers to measure your results so you can compare, and always test again after making a change. Failures are not bad — they are useful clues that help you make your design better. Real engineers do this same process every day, and now you can too!