From Blink LED to IoT: A 12-Month Roadmap for Class 7
Most "robotics for kids" courses make one of two mistakes:
- Too slow — six weeks of theory before a single LED blinks
- Too fast — kids "complete" 10 projects without understanding any
This roadmap is the one we run with class-7 batches. 2 hours per week, zero prior experience, real output every month.
Month 1 — Electricity exists
- Concept: current, voltage, resistance — felt with hands, not formulas
- Build: simple LED circuit on a breadboard
- Win: "I lit a light using a battery"
Month 2 — The Arduino arrives
- Concept: microcontroller = a tiny brain that takes instructions
- Build: blink an LED with code
- Win: "My code made it blink fast, then slow"
Month 3 — Inputs
- Concept: buttons, switches, sensors as the "senses" of the brain
- Build: press a button → light an LED
- Win: kid debugs their first wiring error themselves
Month 4 — Sensors
- Concept: analog vs digital signals
- Build: dark-detector night light (LDR + LED)
- Win: project actually used at home for a week
Month 5 — Motion
- Concept: motors, servos, PWM
- Build: a servo that follows a hand
- Win: "It MOVES because of MY code"
Month 6 — Mid-year showcase
- Recap of all 5 builds
- Parents invited to demo day
- Kids explain what they built and why
The showcase is non-negotiable. It triples retention into the second half.
Month 7 — Displays
- Build: LCD or OLED showing live sensor data
Month 8 — Buzzers & alerts
- Build: distance alarm (ultrasonic + buzzer)
- Concept: thresholds and decisions in code
Month 9 — Wireless
- Build: a Bluetooth-controlled LED from a phone
- Concept: communication between devices
Month 10 — Networking basics
- Build: an Arduino sending data over serial to a computer
- Concept: data flow, baud rate, debugging
Month 11 — IoT, for real
- Build: connect to Wi-Fi (ESP8266/ESP32), log sensor values online
- Concept: cloud, dashboards, latency
Month 12 — The capstone
- Build: smart plant monitor
- Soil moisture sensor + DHT11 + ESP32
- Sends data to a free dashboard
- Buzzer alert when water is low
- Showcase: parents, school principal, and AI-generated certificate
What kids should be able to say at the end
- "I can wire a sensor without copying a diagram"
- "I can find a bug in my code"
- "I built something useful at home"
- "I want to build the next one"
If your program isn't producing those four sentences by month 12, something in the curriculum loop is broken — not the kid.
