Skip to content
Make the first robotics project a question you can test
Teen robotics โข build and test โข project notebook
Use a baseline-and-change log for mechanical builds or supported command tests. Keep assembly and programming separate and follow the kit's instructions.
Start with the kit you actually have and one result you can observe. For an assembly model, that might be whether a documented mechanism completes its movement without binding. For a programmable robot, it might be whether changing one supported command changes the final direction. The project is not โlearn all of roboticsโ; it is answer one question using a safe, repeatable setup.
Use the four-step log below after reading the exact kitโs instructions, age guidance and operating conditions. If you still need to select hardware, our robotics kits for teens buying guide covers programming, devices, sensors and package checks. This page is for planning and carrying out a bounded projectโnot another product ranking.
The four-step robotics project log
- Define one goal. Describe an observable result and the manual-approved activity that can produce it.
- Record the baseline. Note the model, instructions, power arrangement, surface, starting position and initial program or assembly state.
- Change one permitted variable. State the change before making it. Keep other conditions as similar as practical, and follow the power-off procedure for hardware adjustments.
- Explain the result. Separate what you observed from what you think caused it. Record an unanswered question if the result is unclear.
NASA JPLโs engineering-design flow chart describes identifying a problem, building, testing and improving a design. It is useful context for the process, not evidence of this kitโs performance or approval to modify hardware beyond its instructions.
Copy this baseline-and-change sheet
Use a notebook, print this section or copy the headings into a document. Leave a field blank only if you have decided it does not apply; an unknown power requirement or missing instruction is a reason to stop, not a blank to work around.
| Record | Your project notes |
|---|---|
| Project and boundary | Question: ____ ; exact kit/model: ____ ; manual page/program: ____ |
| People and preparation | Required adult help: ____ ; workspace: ____ ; specified power/charging: ____ |
| Success condition | I will observe or measure: ____ ; this will count as a working result: ____ |
| Baseline setup | Assembly/configuration: ____ ; file/version: ____ ; surface/start: ____ ; permitted operating conditions: ____ |
| Baseline observation | What happened: ____ ; relevant measurement or description: ____ |
| One permitted change | Change: ____ ; manual permission/reference: ____ ; prediction: ____ |
| Power-off check | Shutdown/disconnection completed before hardware adjustment: ____ ; recheck before restart: ____ |
| Repeat observation | Same conditions restored: ____ ; actual result: ____ ; unexpected differences: ____ |
| Conclusion and next step | Supported conclusion: ____ ; uncertainty: ____ ; next approved test or support request: ____ |
Record a short sentence rather than a verdict such as โbetter.โ โThe model moved forward but veered leftโ tells you more than โfailed.โ If you measured something, include the unit and how you measured it. A photograph of the unpowered starting build can help, but it does not replace the manualโs connection diagram.
Project card A: check a mechanical assembly against its baseline
Use only with: an assembly kit whose manual describes the motion you want to observe and allows you to inspect or reseat the relevant parts. This is a project-planning example, not confirmation of any particular modelโs manual or performance.
Question
โDoes the model complete the documented movement after I correct one assembly step to match the instructions?โ This tests the accuracy of the build. It does not require designing new gears or changing the supply.
Procedure
- Compare the unpowered build with the manual. Confirm that the intended test is permitted and that the model is ready to operate.
- Run the documented baseline only if safe to do so. Describe the motion from a safe distance; do not touch gears or hold a stalled mechanism while powered.
- If an alignment issue is identified, stop and disconnect power. Correct only the step the manual describes, then have the assembly checked before restarting.
- Repeat the same permitted test in the same workspace. Record whether the observed motion changed.
Interpretation: if the movement changes after a correction, the observation is consistent with that correction mattering. It does not prove that the same fix explains every problem. If the part is damaged, the adjustment is not documented or you cannot identify the fault, stop and use the supplierโs support route.
Do not substitute: a stronger power source, forced gears, removed guards, improvised lubricant or a new gear ratio. โChange one variableโ only applies to permitted changes; it is not permission to alter the design arbitrarily.
Project card B: test one change in a supported command sequence
Use only with: a robot whose manual documents user-editable commands and a safe stop procedure. A remote-control or preset-action toy does not automatically qualify.
Question
โWill replacing one supported turn command change the final direction as predicted?โ Use the robotโs actual command names and meanings. Do not assume that one movement command equals a fixed square or that every turn is 90 degrees.
Procedure
- Choose a short working sequence from the official tutorial. Save or record it as the baseline and mark the robotโs start position and facing direction.
- Check the clear test area and run the baseline. Record the endpoint and direction separately.
- Make one permitted code change. Write the prediction before running it; do not also alter speed, surface or assembly.
- Restore the same starting state, including clearing old commands where the manual requires it, and run the revised version.
Interpretation: a different final position and a different final direction are not the same observation. Describe both before deciding whether the command behaved as expected. If the robot is inconsistent, first check whether the starting position, program or surface changed. Do not compensate by adding more commands at random.
For a concrete, named-platform route example and a paper alternative, see our coding robot guide. Verify that guideโs example matches your exact robot before trying its commands.
Troubleshoot in layers, with power off for hardware checks
| Symptom | Next question | Useful evidence |
|---|---|---|
| No movement at all | Does the manualโs setup/power/start procedure match the present state? | Switch/charge status as documented, exact error or indicator, last completed instruction. |
| Program cannot be sent | Is the selected device, connection and editor configuration correct? | Exact error message, software version and relevant setup page. |
| Program runs but motion is unexpected | Does the unpowered assembly match the diagram? Is the correct saved program running? | Photo of checked assembly, filename and baseline description. |
| Result varies between trials | Were the start, surface and permitted power/operating conditions comparable? | List of differences, without guessing a cause. |
| Binding, heat, unusual smell or damage | Can the equipment be safely shut down and referred for help? | Record the symptom after stopping; do not keep testing. |
Inspect wiring or mechanical parts only after the prescribed shutdown and disconnection. A program paused in an editor may leave the circuit powered. Do not repeatedly energize an apparently faulty build. If a check cannot be completed safely or confidently, ask an appropriately skilled adult or the manufacturer rather than turning the uncertainty into another trial.
Required safety controls work together
Follow all task-specific precautions in the exact manual. Adult supervision, eye protection, guarding, tool handling and fume controls are not interchangeable options: where more than one is required, use them together. Do not assume cutting, soldering or power tools are included in a robotics project merely because it is intended for teenagers.
These project cards do not require soldering. If a different activity does, arrange a separate, suitable teaching setup with trained oversight and appropriate heat and fume controls. The HSEโs solder-fume guidance identifies the rosin-flux fume hazard and the need for extraction; it is not a complete child-use protocol.
Keep hair, jewellery, loose clothing and fingers clear of moving parts. Keep small components away from younger children. Follow the specified supply and charging arrangements; household mains work and opening adapters are outside this guide. Solar models need their documented light and operating conditions, not improvised high-heat illumination or unattended outdoor exposure.
Stop for unexpected heat, smoke, smell, damage, binding or an unidentified connection. Disconnect safely and seek guidance before further use. Finishing the planned test is never more important than stopping at an unclear hazard.
Turn the notes into a short project explanation
Use four sentences: โMy question wasโฆ My baseline showedโฆ I changedโฆ The new result wasโฆโ Add โI still do not knowโฆโ when appropriate. That last sentence distinguishes an honest result from a guessed explanation.
A useful next step might be repeating an unchanged, safely working test to check consistency, trying one other documented setting or asking for replacement instructions. It need not be another purchase. Save the working file, mark the current manual step and store parts so the project can be resumed without reconstructing its history.
Parents and club leaders can ask which observation supports the conclusion rather than taking over the build. A project can finish with an identified limitation and a clear support question. No perfect run, speed target or guaranteed learning outcome is required.
Select hardware only after choosing a project card
For the mechanical card, obtain a manual that actually permits the motion, inspection and correction you plan. A solar assembly format can be relevant to that kind of build, but its model name does not confirm the specific test. Separate multi-model configurations are not one universal package; check actual contents and whether solar-panel or battery-compartment components are part of the selected option.
For the command card, require documented user-editable commands, an interface that works with the intended device and a safe stop procedure. A physical robot shape, remote control or battery compartment does not establish coding, Raspberry Pi compatibility or app support. No exact current kit is verified here as a replacement for either project card.
Request the exact manual, age guidance, tools, parts and power conditions before buying or testing. Battery inclusion is not implied by a pictured compartment. If a required instruction is missing, use the store contact route to ask for that specific information rather than guessing.
Browse robot building formats, coding activities or engineering toys by the documented task. Other problem-solving formats and STEM activities are alternatives, not interchangeable technical specifications.