You decided to join a contest. So what will you build? The hardest part is often not code or soldering; it is finding a right and doable idea. Ideas that are too big stay unfinished. Ideas that are too small do not convince the jury. You need the middle.
This article is the second part of our Project and Contest Guide series. In the first article we looked at which contest might fit you. Now we focus on this question: how do you find a good project idea? Seeing a problem, narrowing it, and testing "can we build this in time?"
Remember: A good idea is not the most complex idea. A good idea is a clear problem, a measurable goal, and a solution your team can actually build.
Where do ideas come from?
Ideas do not fall from the sky. Most of the time they come from these three places:
- Your own life: School, home, neighborhood, transport, energy, safety, accessibility
- Observation: "This always breaks," "This takes too long," "This is dangerous"
- What you learned: Arduino, sensors, software, workshop skills — problems you can solve with tools you have
Write 10 things in a notebook that annoy you, feel hard, or waste something. Then pick 2–3 and narrow them. Trying to invent a "super project" on a blank page usually fails.
Problem–solution frame
Every good project should fit into these three sentences:
- Problem: Who, where, what difficulty?
- Solution: What are we making? (device, software, method)
- Proof: How will we know it works? (measurement, test, comparison)
If one of these is missing, the idea is not contest-ready yet.
| Weak wording | Better wording |
|---|---|
| We will solve traffic | A warning system that reduces waiting time at the pedestrian crossing after school |
| We will do smart farming | A simple soil-moisture sensor that alerts with LED and buzzer when the classroom plant dries |
| AI will know everything | A visual warning board that reduces wrong socket use risk in the workshop |
| We will build a robot | A PID tune that reduces how often the line follower leaves the path on turns |
As you see, a good idea is narrow and measurable.
Steps to narrow the idea
- Who? Student, teacher, farmer, person with disability, older adult?
- Where? School yard, classroom, home, workshop, field?
- How much? Pick a measure: time, cost, error count, water amount
- With what? Materials and knowledge you have (Arduino, sensors, app)
- In how long? A realistic plan by the application deadline
If you cannot answer these five clearly, the idea is still too wide. Keep narrowing.
The "Can we build this?" test (5 questions)
- Is there at least one person on the team who knows this work?
- Can materials be found at school or at a fair price?
- Can we produce a first working prototype in 2–4 weeks?
- Can we show success with a number or clear observation?
- Is there a safety risk? (electricity, cutters, chemicals)
If you answer "no / not sure" to two or more, shrink or change the idea. You can always grow it later.
Real-life examples
1. A goal that is too big
You said "We will solve the city's whole trash problem." Two months later only a slideshow remains.
Better: "A warning and counting system that increases correct use of recycling bins in the school canteen."
2. Choosing only because "we want a robot"
You want to build a robot, but the problem it solves is unclear.
The jury asks "What is this robot for?" Problem first, robot second.
3. Copy idea
You want to rebuild last year's project exactly.
You can reuse the same skeleton, but add a new improvement: less energy, a better sensor, a clearer interface, cleaner test data.
4. Fantasy materials
The idea is great but needs expensive boards and special parts; there is no budget.
First drop to a version you can build with the Arduino / sensor kit you have. Fancy parts can come later.
5. No measure
You say "It got better" but there is no number.
Pick simple measures: time (seconds), error count, distance, moisture value, correct-sort rate. Compare before and after the test.
Mini method to find an idea (1 hour)
- 10 minutes: Write 10 problems in a notebook (no filtering).
- 10 minutes: Mark 3 of them.
- 20 minutes: Write problem–solution–proof sentences for each.
- 10 minutes: Run the feasibility test above.
- 10 minutes: Tell your strongest idea to your teacher or team; note what they do not understand.
If the other person asks "What exactly are you doing?" your sentences are not clear yet. Rewrite them.
A short note for parents: The idea should not come from you alone; your child finding it by observing and researching matters. Ask "What is hard for you at home / school?" Talk about the solution together, but leave the project to them.
Short questions you can ask yourself
- Can I say my problem in one sentence?
- Is my solution measurable?
- Does this idea fit my team and our time?
- Is there a risky step for safety?
- Did my teacher and teammates understand the idea clearly when they heard it?
What is next?
In this article we looked at finding and narrowing an idea. In the next part we will cover building a team, dividing tasks, and the captain role: who does what, how work is split, and how to stop one person carrying everything.
A clear problem is the base of a contest. Turn the big dream into a small, measurable step; then start building.
