
give and use peer feedback, plan fair tests for each criterion, and show what I know at the mid-build checkpoint.
Capstone: Build
Do Now. A friend says your drawing “is bad.” Another friend says, “I wonder if the colors would be easier to see if they were bigger.” Which comment helps you more? Why?
Which kind of feedback helps a designer most?
Peer critique. Two teams pair up. Team A explains its prototype in one minute. Team B gives feedback using the starters: I like… (something that works), I wonder… (a question), What if… (an idea to try). Then the teams switch.
Plan a fair test for each criterion. A fair test changes only one thing. You keep everything else the same. You decide what to measure and which tool to use.
Worked example 1: Priya’s rain-garden tray. Criterion: less soil washes away. Test: pour one cup of water on a bare soil slope, then on the same slope with plants and mulch. Change: plants or no plants. Measure: how much muddy water collects at the bottom, in a clear cup. Keep the same: the cup of water, the slope, the tray and the soil.
Worked example 2: Malik’s bird-window sample. Criterion: the glass no longer looks like open sky. Test: from 10 steps away, classmates look at a plain pane and a pane with dot stickers spaced close together. Measure: how many people see trees in each pane. Feedback said, “I wonder if the dots are too far apart.” So Malik plans a second sample with closer dots. That part did not meet the criterion yet, so it is the part to improve.
Evidence finds failure points. Your test data will show which parts work and which do not. That is how you know what to change.
Fill in your test plan, one row for each criterion or constraint.
| Criterion or constraint | What we change | What we measure, and the tool | What we keep the same |
|---|---|---|---|
Mid-build checkpoint. Answer these on your own.
Revise! Make one change based on your feedback. The Recorder notes what changed.
Explain how the evidence from your test plan will help you find problems in your prototype.
How confident are you that you can I can plan a fair test for each criterion of my prototype.
You gave feedback, made a change and planned your tests. Next time, you run those tests and find out how well your design works.
Exit ticket: write one “I like” and one “What if” you received. What did you change because of it?
Materials: prototypes; critique sentence-starter cards; test plan tables; trays, cups and water; rulers or step counts.
Setup: Pair teams with different problems so feedback is fresh. Time each round (1 minute to explain, 2 minutes of feedback). The checkpoint blocks are the mid-build check; review them before 5.07.
Listen for: tests that change two things at once, and “we can’t measure that.” Help teams turn a criterion into a count, a step distance or a 1–5 rating.
Support / stretch: Give a test plan with one row filled in. Stretch: ask teams to plan a test for a constraint, such as cost or build time.