
give and use kind, specific feedback to find new ideas for my team’s silent signal.
Phase 4: Build
Kind, specific, helpful. Read the two comments below. Which one would help you more?
Which comment is the most helpful feedback?
Engineers share ideas. No engineer works alone. Teams show their designs to others. Fresh eyes spot problems the team missed. They also spark new ideas. Sharing makes MORE possible solutions, not fewer.
The gallery walk. Each team sets up a station: its signal tool, its code key, and its test run data. Half of each team stays as the “guides.” The other half walks to other stations. Then switch.
The protocol. At each station:
Worked example 1: a great set of notes. Visitors at Mei’s station wrote: “I like that help is many fast flashes. It is easy to spot.” “I wonder if the flashlight is bright enough outside.” “What if you add a flag for sunny days?” The last note gave Mei’s team a brand-new idea.
Worked example 2: sorting feedback. After the walk, Malik’s team sorts its notes into two piles: “Try it” and “Not now.” They pick the one change that best helps the criteria. Good designers also research: Malik looks up how real fire alarms flash for people who cannot hear well.
| Feedback note | Try it or not now? | Which criterion would it help? |
|---|---|---|
Practice the protocol before the real walk.
After the gallery walk, record your team’s results.
Copy the best feedback note your team got. Explain how it helps you create a new or better solution.
Write one idea you got from ANOTHER team's station that you might use. Explain why it would work for field day.
Feedback is a gift. Your team now has new ideas. Next lesson, we look closely at how people SEE signals, and do a little research.
Exit ticket: what is one thing you need to make a great design, besides building? (Hint: think about research and talking with others.)
Materials: three colors of sticky notes, team stations with prototypes and code keys, a timer (about 4 minutes per station).
Setup: model the protocol with a sample station first. Post sentence starters at each station.
Listen for: vague notes (“good job”); guides who defend instead of listen; teams that want to change everything at once.
Support / stretch: give visitors a checklist to guide notes. Stretch: visitors suggest how two teams’ codes could be combined.