change one part of our plan, retest it and compare Version 1 and Version 2 with data.
Phase 4: Build
Do Now. Look at your improvement table. Circle ONE change you will make today.
Why change only one thing before you retest?
The reading opens over the lesson; close it to come back to exactly where you were.
Rescue Team, time to go around the loop. You found failure points. Now you change one part and test again.
Use evidence to choose. Pick the change that targets your biggest failure point. Your data and your feedback tell you where to start.
Worked example 1: Mia seals the seam. Version 1 saved 80 mL. Water dripped from the gutter seam. Mia overlapped the foil and taped it. Version 2 saved 130 mL. Cost went from $170 to $175. Still within the budget.
Worked example 2: Samuel’s trade-off. Version 1 covered only a quarter of the edge. Samuel added five more plants at $10 each. Now more than half the edge is covered. But his cost went from $170 to $220. That breaks the $200 budget. So he swapped two plants for rocks at $5 each. Cost: $210. Still over. He removed his $20 extra hose, and the cost became $190.
Fixing one part can affect another. That is called a trade-off. Samuel met the edge goal but had to fix the cost.
Compare with a table. Put Version 1 and Version 2 side by side for every goal. Then decide which version is better overall.
| Goal | Version 1 | Version 2 | Better? |
|---|---|---|---|
| Rain test (mL saved) | |||
| Shade test (degrees cooler) | |||
| Edge covered | |||
| Water plants | |||
| Cost |
Make one change, retest and fill in the comparison table.
Explain your improvement.
What did you change? What evidence told you to change it?
Is there still a failure point? What would you test next?
Version 2 is tested. Next time we learn how real people help other habitats after a change.
Exit ticket: finish the sentence. Our data showed ___, so we changed ___.
Pacing: warm-up 3, reading 6, mini lecture 6, revise and retest 18, writing and exit 7 minutes.
Misconceptions: changing many things at once is faster (you cannot tell what helped); Version 2 is always better on every goal. Samuel’s example changes the edge first, then fixes cost; point out he retests the edge after the swap.
Supports: provide the comparison table pre-filled with Version 1 data. Stretch: run two rain trials of Version 2 and find the average.
Answer guide: strong answers cite numbers from both versions, name every goal, and note any trade-off.
NASA Jet Propulsion Laboratory Education, Engineering Design Process Flow Chart · NASA/JPL-Caltech education resource; reuse follows the JPL Image Policy
Engineers at NASA’s Jet Propulsion Laboratory build robots and spacecraft. They share a chart for students. It shows the steps engineers use to solve problems. It is a flow chart. You follow it from box to box.
First, engineers identify the problem. Next, they brainstorm many ideas. Then they select one design. After that, they build a model or prototype.
Then they test the prototype and judge how well it worked. The chart asks a question: was the problem solved?
If yes, the engineers share their solution. If no, they do not stop. The arrow goes back. They build again and test again. On the chart, build, test and improve make a circle. They keep going until they find a solution.
So building is not something you do just once. A prototype is meant to be tested, changed and tested again.
Source: NASA Jet Propulsion Laboratory Education, Engineering Design Process Flow Chart (jpl.nasa.gov)