Grades 2–9 · STEM & Computer Science
STEM Design Challenges and Computer Science Labs for Grades 2–9
Short answer: This STEM and computer science collection has thirteen units on algorithms, debugging, data, accessibility, sensors and engineering design. Most run unplugged or on paper models. Each unit includes four 90-minute double lessons, a 42-page teacher PDF, 16 slides, five worksheets, five answer keys and a 20-point learning check with model responses.
- Grades2–9, by unit
- Units13 units
- DevicesMost units are unplugged; Scratch and spreadsheets optional
- Includes42-page PDF, 16 slides, 5 worksheets, 5 answer keys
Computer science is easiest to teach when students can trace what a program does step by step. Many of these units do exactly that on paper. A robot on a grid follows E E N N E until it hits a blocked square. A search for book number 55 in a sorted list of seven counts its comparisons. A leak sensor reads 0,0,1,0,1,1,1,0, and students decide which alert rule raises fewer false alarms.
The other strand is design for real users. Students audit a mock web form, redesign a tactile map and compare emergency alert prototypes against a user who wears hearing protection. Accessibility is not a separate topic here; it is how the design is tested.
Units for this topic
Unplugged Robot Debugging Cards
Grid commands let young students trace and debug a program without screens.
Build a Library Search Algorithm
Students compare linear and binary search on a short sorted list.
Sensor Calibration with a Paper Microcontroller
A paper microcontroller teaches calibration against known references.
Spreadsheet Skills for Classroom Data
Cleaning duplicate and missing rows comes before any chart.
Data Labels and Machine Learning Bias Lab
Unbalanced training data shows students where machine learning bias comes from.
Creative Commons Remix Lab
Students decide whether a remix fits a stated Creative Commons license and write attribution.
Accessible Game Design in Scratch
Adds equivalent input and visible cues to a Scratch game.
Website Accessibility Audit Lab
A small interface audit covers keyboard access, labels and color-only cues.
Repair a Broken Web Form
Students specify form behavior that helps users recover from errors.
Design an Accessible Emergency Alert
Alert prototypes are tested against a user profile and a measurable test.
Design a Water-Leak Detector
Two alert rules are compared for speed and false alarms on simulated readings.
Design a Better Tactile Map
A tactile practice map is redesigned with a clear symbol key and user feedback.
Test an Evacuation Route with a Paper Simulation
Students test an evacuation route on paper, find the bottleneck and explain which change helps most.
Algorithms and debugging, unplugged
Unplugged Robot Debugging Cards gives Grades 2–5 a start at (1,1), a goal at (4,3) and a blocked square at (3,1). Students trace the commands until the first invalid move and repair the program without making it longer. Build a Library Search Algorithm compares linear and binary search on sorted IDs and asks students to state why binary search only works on a sorted list.
Sensor Calibration with a Paper Microcontroller reports readings of 3, 13 and 23 for reference values 0, 10 and 20. Students choose a correction, write pseudocode, test it on a raw reading of 18 and explain why one reference point is weak evidence.
Data, licensing and machine learning
Three units deal with data before it reaches a chart or a model. The spreadsheet unit has a duplicate row and a blank value, and students calculate group means from valid rows only. The Creative Commons Remix Lab asks whether a cropped and recolored photo fits a CC BY license or a CC BY-ND license, and students draft an attribution with creator, source, license and changes.
Data Labels and Machine Learning Bias Lab uses a mock photo classifier trained on 20 bright photos and two dim ones. On test sets of ten, it gets 9 bright photos right and 4 dim ones. Students compute both accuracies, name a plausible data issue and design a retest.
Accessibility and design for users
Four units put accessibility at the center of the design process.
- Accessible Game Design in Scratch: a game advances only on a mouse click and signals success only with sound; students add a keyboard event and a visible cue
- Website Accessibility Audit Lab: a mock interface with a placeholder-only label, color-only error marks and a custom control that Tab skips
- Repair a Broken Web Form: required fields show only a red border and the form erases the name after an email error
- Design a Better Tactile Map: the draft uses identical raised dots for the desk and the exit
Engineering design challenges
The engineering units use simulations with clear rules. The evacuation route unit compares two exits by walking steps and how many tokens each door processes per turn, and it states that students are not designing a real evacuation procedure. The water-leak detector unit compares an alert on one wet reading with an alert on two consecutive readings. Design an Accessible Emergency Alert compares a siren alone with a flashing icon paired with a vibration puck.
A five-step sequence
-
Choose plugged or unplugged
Check whether the unit needs devices. Most do not, and the Scratch and spreadsheet steps are optional.
-
Trace the starting case
Use the slides to trace the first case one step at a time, recording state on the board.
-
Find the failure
Students locate where the program, design or dataset breaks, using the worksheet's test grid.
-
Repair and retest
Lessons two and three ask for a fix, then a test on a new case to see if the fix holds.
-
Explain the design choice
The learning check asks students to justify their repair and name a limit, scored with the 100-point sheet.
Common mix-ups and what to try
Debugging means starting over.
The debugging units ask students to find the first invalid step and repair it without making the program longer.
A computer model is fair because it is a computer.
The bias lab shows that a classifier trained mostly on bright photos performs worse on dim ones.
Accessibility is something you add at the end.
The design units test prototypes against specific users from the start.
Related teaching guides
Frequently asked questions
What does the STEM and Computer Science collection contain?
Thirteen units covering debugging, search algorithms, sensor calibration, data cleaning, Creative Commons, machine learning bias, accessible game and web design, emergency alerts, evacuation simulation, leak detection and tactile maps. Each includes a teacher PDF, slides, worksheets, answer keys and a learning check.
Do students need computers?
Most units run on paper. The Scratch unit and the spreadsheet unit benefit from devices, but the worksheets can be completed without them.
Which units work in elementary school?
Unplugged Robot Debugging Cards starts at Grade 2, and the Scratch, search algorithm and tactile map units start at Grades 3–4.
Is the evacuation unit a real safety plan?
No. It is a paper simulation for comparing routes and bottlenecks, and it says clearly that students are not designing a real procedure.
What if a unit does not fit my computer science standards?
Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.
Can a non-specialist teach these?
Yes. The teacher background section and slide notes explain each concept, and every worksheet has an answer key.
Ready for your next lesson?
Start with one unplugged unit and see how your students trace and repair their first case.
View Unplugged Robot Debugging CardsInstant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

