Teaching Robotics to Grades 1–7: What Actually Works
A year of running robotics labs and workshops with primary and middle school students taught me that curriculum design matters far more than the kit you buy.
Start with the machine, not the code
The first version of my robotics class opened with a slide deck about algorithms. I lost the room in four minutes. The second version opened with a servo sweeping back and forth on a desk, and the same students were asking how to make it faster before I had finished the demo.
Concrete motion earns attention. Code earns it afterwards.
- Show the finished behaviour before introducing any syntax
- Let students break the demo deliberately, then repair it
- Keep the first working program under ten blocks
Split the curriculum by age band, not by kit
Grades 1–2 and Grades 6–7 cannot share a lesson plan, even with the same hardware. I ended up writing three tracks that reuse the same kits but change the abstraction level.
- Grades 1–2: visual block sequencing with Scratch, no wiring
- Grades 3–5: blocks plus sensors with one variable at a time
- Grades 6–7: text-based programming, microcontrollers and circuits