Every engineering project begins with a problem — something that does not work well, is missing, or could be better. Good engineers are careful observers: they notice when things are inconvenient, unsafe, wasteful, or unfair, and they ask "Could I design something to fix this?" Identifying the right problem is just as important as building a good solution, because a perfect solution to the wrong problem helps nobody. Engineers learn to ask who has the problem, what makes it a problem, and what constraints (rules and limits) any solution must follow.
Take a "problem walk" around the school or home: have students observe and list things that could work better (a door that slams, a trash can that tips over, a water fountain that is too high for younger kids). Then practice narrowing broad complaints ("lunch is bad") into specific, solvable problems ("my sandwich gets squished in my backpack"). Introduce constraints by asking "What rules would a solution need to follow?" (must cost under five dollars, must fit on a desk, must be safe for a five-year-old).
Before you can solve a problem, you need to find a problem — and finding a good one is a skill. Engineers are trained observers. They walk through their day noticing small frustrations: a backpack zipper that always gets stuck, a park bench that collects rainwater and stays wet, a hallway where two groups of students always bump into each other going opposite directions. Each of these observations is the seed of an engineering project.
But noticing a frustration is not the same as having a good engineering problem. A good problem is specific and solvable. "School could be better" is a feeling, not a problem you can engineer a solution for. "Students' water bottles fall out of the shallow cubbies and roll across the floor" — that is specific. You know exactly what happens, you can watch it happen, and you can imagine designing something to fix it.
Once you have a specific problem, the next step is understanding it deeply. Who experiences this problem? When and where does it happen? What makes it annoying, dangerous, or wasteful? If the problem is "the classroom trash can tips over," you need to know: does it tip because it is too tall and narrow? Because people bump it? Because it gets too full and top-heavy? Each cause would lead to a different solution. Engineers who skip this step often build something clever that completely misses the point.
Finally, every real problem comes with constraints — rules and limits that any solution must follow. A solution might need to cost less than five dollars, fit on a desk, be safe for young children, or use only recycled materials. Constraints sound limiting, but they are actually helpful. Without them, you would face a paralyzing number of options. With them, many options are immediately ruled out, and you can focus your creativity on ideas that have a real chance of working. Constraints are not the enemy of creativity — they are the guardrails that keep creativity aimed at something useful.