
interview and survey the people who have our problem, and use what they say to explain the need.
Capstone: Investigate
Do Now. Diego’s team wants to fix the bus line. Diego thinks the problem is that kids are slow. Then he asks a bus driver. The driver says, “Kids cannot see which bus is mine.” Same line, different problem!
Why should Diego's team ask the bus driver AND the students?
Engineers listen first. Before you build, you find out what people really need. You can do it two ways. An interview is a short talk with one person. A survey asks many people the same few questions. Then you count the answers.
Good interview questions are open. An open question cannot be answered with yes or no. “Is the lunchroom loud?” is closed. “Tell me about a time the lunchroom noise bothered you” is open.
Worked example 1: Mei’s lunchroom survey. Mei’s team asks 20 classmates one question: “How loud is lunch, from 1 (quiet) to 5 (very loud)?” They make a tally. Most kids pick 4 or 5. Then they ask a lunch aide an open question. She says the noise is worst when everyone arrives at once. Now the team has numbers AND a story. Both are evidence.
Worked example 2: needs change over time. Priya’s team studies the soggy corner. The custodian says it was not always muddy. A few years ago, more blacktop was added nearby. Now more rain runs off into that corner. The need changed because the place changed. Needs and wants change over time, too. Long ago, people wanted a lamp that burned oil. Today people want lights that use little energy.
Today’s job. Each team writes 3 open questions. Then you interview at least one person who has your problem and survey your class. Record everything in the data table. Do not plan a solution yet. Just listen.
Copy this data table into your notebook. Fill it in during your interview and survey.
| Who we asked | Question | What they said, or the tally | What it tells us about the need |
|---|---|---|---|
| Our class survey | 1: __ 2: __ 3: __ 4: __ 5: __ |
On your own. Look at your team’s data table.
Use the information your team gathered to explain the problem. Who has it, and what did they tell you? Use one number from your survey and one quote or idea from your interview.
Has this need changed over time? Tell what might have been different a few years ago, or what people might want in the future.
Today you listened like real engineers. Next time, you will measure the problem and write the rules your design must follow.
Exit ticket: rewrite your problem statement using what you learned today. What changed from your first version, and why?
Materials: clipboards, printed data tables, pencils; a short list of approved interviewees (lunch aides, custodian, a bus driver, the office staff, the librarian, a younger class).
Setup: Arrange 5-minute interview slots in advance. A visiting adult can also come to the room, which keeps teams supervised. The class survey can be a show of hands that each Recorder tallies.
Listen for: closed questions, leading questions (“Don’t you think it’s too loud?”) and teams pitching solutions. Model one open question per team before they go.
Support / stretch: Give question starters (“Tell me about a time…”, “What is the hardest part of…”). Stretch: have a team interview two different kinds of people and compare what each sees.