give and use feedback to name the parts of our plan that do not meet the criteria or constraints yet.
Phase 4: Build
Do Now. Think of a time someone gave you a helpful idea. How did they say it? What made it kind and useful?
Which is the most helpful feedback?
The reading opens over the lesson; close it to come back to exactly where you were.
Rescue Team, today we help each other improve. Real engineers share results and ask for ideas. More minds make more solutions.
Our critique protocol. One team shows its model and its data. Visitors give three kinds of feedback. I like names something that works. I wonder asks a question. What if offers an idea.
Tie feedback to the brief. Good feedback names a criterion or constraint. It points to a part of the system: the roof and gutter, the barrel, the pond, or the edge plants.
Worked example 1: Grace gives feedback. “I like that your plants kept the water 3 degrees cooler. I wonder why only a quarter of the edge is covered. What if you moved two rocks to the sunny side?”
Worked example 2: Leo uses feedback. Leo’s team heard, “Is the roof water clean enough for tadpoles?” Leo wrote: “Part to check: the barrel water. Goal: keep the pond healthy for frogs. Idea: ask the nature center to test the water, and keep the roof clean.” He named the part, the goal and a next step.
| Part of our system | Goal it does not meet yet | Evidence | Idea to improve |
|---|---|---|---|
| Roof and gutter | |||
| Barrel | |||
| Pond | |||
| Edge plants |
Visit two teams. Then fill in the improvement table for your own plan.
Plan your improvements.
Which part of your plan is the biggest failure point? Name the goal and the evidence.
Which feedback idea will you try? Why do you think it will help?
Now you know what to fix. Next time you build and test Version 2.
Exit ticket: what was the most helpful feedback you heard today? Why?
Pacing: warm-up 3, reading 7, mini lecture 5, two critique rounds 16, table and exit 9 minutes.
Norms: model kind, specific language. Post the three sentence starters.
Misconceptions: feedback is the same as criticism; only the rain number matters; rain barrel water is safe to drink (it is not). Roof water quality is a real question a nature center would check with experts.
Supports: give feedback cards with starters. Stretch: ask visitors to connect an idea to the shade research from 2.17.
Answer guide: strong tables name a part, a goal, a number as evidence and a specific fix.
U.S. Environmental Protection Agency, Soak Up the Rain: Rain Barrels · U.S. government work, public domain
Let’s reread the rain barrel page like critics. A critic looks for strengths and for things to check.
Strengths. A rain barrel catches water from a roof and holds it for later. It saves water, and the water is free. It also cuts down the runoff that flows off a property in a storm.
Size. A barrel holds only so much. A cistern is a much bigger container that can hold more water. It can sit above or below the ground.
Something to check. The page gives a warning. Rain that flows over a roof can pick up germs from birds and other animals. It can also pick up chemicals from roof materials. People think about this before using barrel water on plants they will eat.
The page also links to guides about how to look after rain barrels and other green projects over a long time.
So a good critic asks: how much water will we need, and is the roof water clean enough for frogs and tadpoles?
Source: U.S. Environmental Protection Agency, Soak Up the Rain: Rain Barrels (epa.gov)