
give and use kind, specific feedback to find the parts of our key that do not yet meet the criteria.
Phase 4: Build
Do Now. Read two pieces of feedback. “Your key is bad.” “I wonder how a volunteer knows what ‘cloudy’ looks like.” Which one helps the team improve?
What makes feedback helpful to a design team?
Junior chemists, real engineers share their work early. Other people spot problems you cannot see, because you already know how your key is supposed to work. Sharing ideas also creates new ideas.
The protocol. Team A reads its key aloud for 2 minutes. Team B runs one known powder through it without help. Then Team B gives feedback with three sentence starters: “I like…”, “I wonder…” and “What if…”. Team A listens, takes notes and says thank you. Then the teams switch.
Look for evidence, not opinions. When Team B gets stuck, that is evidence of a failure point. Write down exactly where they got stuck and which criterion that step breaks.
Worked example 1: Kofi’s critique. “I like that vinegar comes first, because one test removes baking soda. I wonder how a volunteer knows how much water to add in Box 2. What if you wrote ‘half a cup of water, one pea-sized scoop’?” His feedback named one step and one fix.
Worked example 2: Lena’s notes. Lena’s team heard that the magnifier step confused the testers. Sugar and salt looked alike to them. Lena wrote: “Box 3 fails the ‘any volunteer’ criterion. Evidence: 2 of 2 testers guessed wrong.” Now her team knows exactly what to fix.
| Feedback | Which step? | Which criterion or constraint? | Evidence | Our idea to improve |
|---|---|---|---|---|
| I like… | ||||
| I wonder… | ||||
| What if… |
Run the protocol with your partner team. Check your thinking as you go.
Sort the feedback you received.
List two parts of your key that do not yet meet a criterion or constraint. For each, give the evidence from today's test.
Which one part will you improve first? Explain how the evidence you collected points to that part.
Feedback is a gift, junior chemists. Next time is our mid-build checkpoint, so review your notebook tonight.
Exit ticket: what is one idea you borrowed from another team today? How will it help the pantry?
How confident are you that you can I can use test evidence to find the parts of a design that need improving.
Materials: each team’s kit and key card, known powder samples, critique sentence-starter cards, sticky notes, a timer.
Setup: pair teams in advance. Run two rounds of 12 minutes each. Model the protocol once with a sample key before teams start.
Listen for: feedback aimed at people instead of designs; designer teams explaining or arguing instead of listening; “I wonder” comments with no step named.
Support / stretch: give students a sticky-note template with the three starters printed. Stretch: ask the critique team to rank the partner key’s steps from most to least reliable.