One-sentence summary
A good project starts with a good problem; in this lesson we will learn how to find a problem that is based on a real need, that interests you and that you can actually build at your scale.
Why does it matter?
When people start a project, the first question they usually ask is, “What can I make?” But there is a better question: “Which problem do I want to solve?”
If you choose the wrong problem, even great code will not help. Choose a problem that is too big, and you will never finish it. Choose one that nobody cares about, and nobody will use it. Choose one that bores you, and you will give up halfway.
Choosing the problem is the most invisible step of a project, and also the most decisive one. A student who picks the right problem can build something useful even with simple tools. In this lesson we will walk, step by step, through turning an idea into a “problem you can actually build.”
Where do we find a problem?
Problems do not appear out of thin air. They usually come from observation. When you look around carefully, you notice small but real annoyances.
Look at your own daily life
The best problems are often the small difficulties you experience yourself, because you understand those best.
You can ask a few questions:
- At which moment of the day do I think, “I wish this were easier”?
- Is there a small, repeated annoyance at home, at school or in my room?
- Do I keep forgetting something, fumbling in the dark or doing a task by hand over and over?
Example 1: The night-light problem
Suppose that when you get up at night for a glass of water, your room is pitch dark. The light switch is by the door, not next to your bed. Walking to the switch in the dark is both hard and a little scary.
A real problem comes out of this:
“When someone enters the room at night, a soft light should turn on automatically, without anyone having to reach for a switch.”
This is the idea of an “automatic night light.” You can build it with the motion sensor, LED and simple conditional logic you learned in earlier modules. Small, real and at your scale.
Example 2: The forgotten-bag problem
A second example: in the morning rush you often leave your water bottle or lunch box on the table.
Another problem comes out of this:
“Before I leave through the door, if one of the items that should be in my bag is missing, I should get a short warning.”
This problem is small and real too. But be careful: detecting every single item can be hard. Maybe a simpler version that only checks whether the water bottle is in place is more buildable. Narrowing a problem can save a project.
Three qualities of a good problem
A good project problem sits where three circles overlap: interest, usefulness and reachability.
1. Interest: Does it make you curious?
Finishing a project takes time. It is hard to stay patient with a topic that does not interest you. Choose a problem where you can honestly say, “It would feel good to solve this.”
2. Usefulness: Does it really help someone?
A good problem makes life easier for at least one person. That person can be you, a sibling or a friend. Have an answer to the question, “Who would use this?”
3. Reachability: Can you build it with your tools?
Even the best idea does not become a project without materials and time. Choose a problem that fits the board, sensor, time and knowledge you have. Instead of a flying robot, a small night light for your desk is often a better start.
If a problem carries all three qualities at once, it is worth building a project on.
Keeping the problem at the right scale
The most common mistake for beginners is choosing a problem that is too big. “A smart system that controls every light in the house by voice” sounds amazing, but it takes weeks and usually stays unfinished.
The trick is to make the problem smaller. This is called narrowing the scope.
Bring the big idea down to its smallest working form:
| Too big | Narrowed (buildable) |
|---|---|
| A smart system that automates the whole house | A night light that works in one room |
| Voice-controlled lighting | Motion-activated lighting |
| A bag that detects every item | A bag that only checks the water bottle |
A small but finished project is always worth more than a big but half-done one. Finish the first version, then grow it if you want.
Mini practice
Now it is your turn to choose a problem. Use the checklist below. Write down one problem idea and mark each line honestly with “yes” or “no.”
PROBLEM-SELECTION CHECKLIST
My problem idea:
_______________________________________________
[ ] 1. This is a real need/annoyance, not just a wish.
[ ] 2. It makes life easier for at least one person.
Who: ______________________
[ ] 3. The topic genuinely interests me.
[ ] 4. It is buildable with the materials and
knowledge I have.
[ ] 5. I can finish it in the time I can spend.
[ ] 6. There is a clear test for saying "it works."
Test: ____________________
[ ] 7. I can narrow it to a smaller version if needed.
Rule: If you have 5 or fewer "yes" marks,
rethink or narrow the problem.If we put the night-light example on this list, most lines would be “yes”: a real need, useful to you and anyone who uses the room, materials on hand, and a clear success test — “the LED turns on when someone walks into the dark room.”
Common mistakes
Starting with a product instead of a problem
“I want to build a robot” is not a problem; it is a product. First answer the question, “Which problem will it solve?” The product is the shape of the solution; the problem is its reason.
Choosing a problem that is too big
Being too ambitious at the start is the most common place to get stuck. Shrink the idea and aim for a first working version.
Choosing a problem that helps no one
“It would be interesting” is not enough. If you have no answer to “Who would use this?”, the problem stays up in the air.
Not defining what “it works” means
If you do not know when the project is finished, it never is. Right at the start, write down “what must happen for this to count as a success?” For example: “When the room goes dark and someone enters, the LED should turn on within three seconds.”
Safety note
When you choose a problem, think about other people too. If you want to solve someone else’s need, respect their permission and their privacy.
- If you want to solve someone else’s problem, ask them first and get their permission. Nobody wants to be watched or tracked.
- If your idea involves collecting personal information such as camera, microphone or location, do not build it on your own; talk to an adult first.
- When working with electronic parts, batteries and sensors, check the connections together with an adult.
A good project is not only useful; it is also respectful of others and safe.
Lesson summary
- A project starts with choosing a good problem; find the problem to solve before the product to build.
- The best problems are often the small but real difficulties in your own daily life.
- A good problem sits where interest, usefulness and reachability overlap.
- Narrowing big ideas down to the smallest buildable version saves the project.
- Setting a clear test for “it works” and respecting other people’s permission is part of the job.
Check questions
- When planning a project, which is the better first question: “What can I make?” or “Which problem do I want to solve?”
- What are the three overlapping qualities of a good problem?
- What does “narrowing the scope” mean, and why does it help?
- Why is “I want to build a robot” not, by itself, a good problem?
- In the night-light example, what kind of test could you set to say “it works”?
Answers
- “Which problem do I want to solve?” is better, because a project is a solution; you first need to be clear about the problem to be solved.
- Interest (it makes you curious), usefulness (it really helps someone) and reachability (you can build it with your tools).
- Narrowing the scope means bringing a big idea down to its smallest working version. It helps because it makes the project finishable and lowers the risk of giving up halfway.
- Because it describes a product, not a problem. Without knowing which need it meets, the project has no clear direction and no clear “done” point.
- For example: “When the room goes dark and someone enters, the LED should turn on within three seconds.” It only needs to be a clear, observable, testable measure.
Source and verification note
For “How to Choose a Problem”, verification focuses on whether the relationship between Where do we find a problem? and Example 1: The night-light problem remains consistent across examples. A project page should make a result claim only when it is supported by a real prototype, test record or observation. Numbers such as cost, duration and success rate must be labelled clearly when they are estimates.
Next lesson
Understanding Users and Needs: Ways to understand who you are solving your chosen problem for, and what that person truly needs.