Crash! Rocket knocks a box of paper clips into a deep, narrow jar. His hand will not fit inside.
"Let's build a grabber!" he says, reaching for tape.
Raven stops him gently. "Wait. What do you notice about the jar? What exactly is the problem?"
Nova hovers over the jar. "Engineers say the problem first," she says. "Then they build."
An engineer is a person who designs solutions to problems.
A problem is something people need or want that is not working yet.
Before building, engineers say the problem clearly.
A good problem says who needs help and what they need.
| Problem statement | Clear? |
|---|---|
| Rocket needs a way to get paper clips out of a narrow jar. | Yes: who and what are clear |
| Stuff is bad. | No: we cannot tell who or what |
A clear problem has two parts: who needs help, and what they need.
Here is a fuzzy one: "Things fall." Who? What things? We cannot tell.
Here is a clear one: "Raven needs a way to hang her keys."
Now an engineer knows exactly what to solve.
| Statement | True or false? |
|---|---|
| Engineers say the problem before they build. | ? |
| A clear problem says who needs help. | ? |
| A magnet can pick up aluminum foil. | ? |
| A magnet can pick up steel paper clips. | ? |
You think like an engineer already! Tomorrow we learn two big engineering words: criteria and constraints.