Prototype and Test Improvements
Lesson preview: the Mini Lesson and Vocabulary are open to everyone. Guided practice, exercises, the parent checklist and the printable PDF worksheet come with full access (free 7-day trial or membership).
What you will learn
- 1Explain why a low-fidelity prototype is built before a final build
- 2Plan a fair test that changes only one variable at a time
- 3Explain how a baseline and a data table show whether a change helped
- 4Iterate on the design by keeping what worked and fixing what failed
Mini Lesson
A prototype is a rough first version of a design — built quickly, tested honestly, and improved on purpose. Real engineers never trust a first draft. They build, test, learn, and rebuild. In this lesson you will plan a prototype, test it fairly, record what happens, and iterate. The goal is not a perfect first try; the goal is to fail forward — to learn something useful from every attempt.
Low fidelity vs high fidelity
- Low fidelity: cheap, fast, made of paper, tape, cardboard, or sticks. The job is to test the BIG idea, not the looks. Build it in minutes, not hours.
- High fidelity: closer to the real product. Better materials, more careful build, longer to make. Only worth doing AFTER the low-fidelity test proves the idea is worth it.
- Fidelity = how close the prototype is to the real thing. Start low, raise fidelity only as questions get more specific.
Why we test
A design that has not been tested is just a guess. Testing turns a guess into evidence. We test to find out: does it work, how well does it work, and what breaks first? A failed prototype is not a wasted prototype — every failure points to the next improvement. That is what fail forward means: keep moving, but learn from each fall.
Setting up a fair test
- Pick one variable to change (the independent variable). Example: ramp height.
- Pick one variable to measure (the dependent variable). Example: distance the car rolls.
- Keep everything else the same (controls). Same car, same floor, same release method.
- Run each test more than once and average the results — one trial can lie.
Baseline first
Before you change anything, record a baseline — how the prototype performs in its starting form. Without a baseline, you cannot tell whether your change was an improvement, no change, or a step backward. The baseline is your "before" picture.
Recording observations
- Use a simple data table: trial number, what you changed, what you measured, what you noticed.
- Write what actually happened, not what you wanted to happen. Honest data is the only data worth having.
- Photos and quick sketches count as observations — capture before, during, and after.
The iteration cycle
- Build a low-fidelity prototype.
- Test it and record the baseline.
- Identify one thing that worked and one thing that failed.
- Change ONE thing to fix the failure — keep what worked.
- Test again. Compare to the baseline. Repeat.
Words to know
prototype
A rough first version of a design, built to be tested and improved.
test
A planned trial that produces measurable evidence about how a design performs.
iterate
To improve a design through repeated cycles of build, test, and adjust.
fail forward
To treat each failure as useful information that guides the next improvement.
fidelity
How close a prototype is to the final product; low fidelity is rough, high fidelity is polished.
baseline
The starting performance of a prototype, recorded before any changes are made.
Tip: when you change two things at once and the result improves, you do not know which change helped. One change per round. Slower at first, faster in the end.
Unlock the full HSEA system for 7 days.
Add your first kid profile and your 7 days start: every lesson in every grade, saved progress for each child. Nothing to set up, no card required, nothing to cancel.
- ✓ All 1,880 lessons, Grades 1–6, every subject
- ✓ Profiles + saved progress for every kid
- ✓ Printable lessons with answer key