Articles · EdTech · District leadership · Equity
Coding, robotics, and a workforce pipeline any district can start
Lessons from leading K-12 STEM, robotics, and a state coding academy: how any district can build a ladder from kindergarten blocks to real work.
By Dr. William Hickman · 5 min read
As superintendent of a nine-school district in Mississippi, I led STEM from kindergarten through grade 12, green-screen animation studios, smart labs, and a robotics program, and we added Wi-Fi on school buses and in city parks so students could get online outside school. At the state level, I developed Mississippi’s technology plan for schools and the Mississippi Coding Academy, a workforce program funded through grants and partners. Tom Vander Ark of Getting Smart recognized our district among the top 30 U.S. districts for innovation worth visiting.
I share that list for one reason: none of those pieces requires a wealthy district. What a pipeline requires is a ladder every child climbs, a reason to climb it, and someone waiting at the top. Here is how I would advise any district to start.
Build a ladder, not a club
A robotics team that meets until six is a filter, and it filters for the wrong things: a parent who can pick up at six, a family that can pay the fee, a teacher’s recommendation, a child who already thinks she is a robot person. The students who most need to learn that failure is information are often the ones sitting in a reading drill when the team meets.
So put coding and robotics in the school day, for every child in a grade. A rough ladder by age looks like this:
- About ages 5 to 7: picture blocks and simple floor robots, building sequencing, repetition, and cause and effect.
- About ages 8 to 10: full block languages, adding variables, conditions, events, and debugging.
- About ages 10 to 12: first typed code, alongside blocks.
- Ages 13 and up: projects with an audience, such as a game others play, a robot competition, or a website.
The bands overlap, and the child, not the calendar, should decide when to move up. The evidence that young children can do this is solid: Marina Bers and her colleagues have shown that kindergartners can learn programming and engineering concepts with tools built for their hands.
Clubs and teams still matter. They should be the top of the ladder, not the only rung.
Teach the thinking that outlasts the tool
Every board will ask some version of this: why teach children to code when machines write code now? It is a fair question. The machine writes code. It does not know what you want. Someone still has to specify what the program should do, decompose the problem into parts, and verify what came back. AI has taken over many keystrokes, and in doing so it has made those three skills more valuable, not less.
Teach coding for what it teaches directly. A 2019 meta-analysis by Scherer, Siddiq, and Sánchez Viveros found that learning to program has a moderate positive effect on children’s cognitive skills, larger for nearby skills such as reasoning and smaller for distant ones. Treat any spillover as a bonus, not the reason.
Rooms built for making
Smart labs and studios earn their cost only if students make things in them. A green-screen studio where students write, shoot, and edit their own work is creation, often in teams, which is the strongest thing a screen can do. A lab where students take turns on a drill program is not, no matter how new the furniture.
Two rules keep a lab honest.
Build before you buy. Nothing is purchased for students until a teacher who will use it has built something with it, on paid time. Equipment nobody has learned stays in its boxes.
Only students touch the robot. Adults ask questions; students make the fixes. When a volunteer repairs the robot the night before a competition, the result belongs to the adult. When students repair it, the learning belongs to them. Grade the engineering notebook, not whether the robot finishes the course.
Connectivity is part of the pipeline
The school day ends, and learning should not stop at the curb. Putting Wi-Fi on buses and in parks is about meeting students where they actually are after the bell: on long rides, at the park, wherever families gather. Every district can map this for itself. Where do your students spend the hours between dismissal and dinner, and can they get online there? City offices, libraries, and local businesses often share that goal and can share the cost.
Connect the top of the ladder to work
A pipeline needs an end students can see. A workforce program like the Mississippi Coding Academy depends on grants and partners, and the general lesson for any district is that schools cannot build that end alone.
- Bring partners in at the design stage, not the ribbon cutting: employers, colleges, and workforce agencies.
- Use grants to start, and write the sustainability plan on day one, so the program outlives the grant.
- Give students work someone outside school cares about: a real client, a community problem, an actual user.
- Help students leave with proof: a portfolio, a finished project, and a credential where one exists.
Check who is climbing
Pull your participation numbers in computer science, robotics, and engineering, and set them beside enrollment by grade, gender, and student group. If the team looks like the gifted roster, you have a club, not a program.
The research gives you a reason to care. A longitudinal study of FIRST robotics led by Melchior and colleagues at Brandeis University found that participants were more likely than comparison students to take STEM courses and pursue STEM majors, with effects for girls and for students from under-resourced schools. I label that evidence mixed to robust, because the study was quasi-experimental, but the direction is encouraging. It works like a youth league: you never find out who loves the game until everyone gets to play.
The next play
- Ask one question in every building: at what grade does a child here first write a program as part of the ordinary school week? If the answer is “never” or “a sixth-grade elective,” start lower.
- Put a block-coding app on every kindergarten through second-grade device, and give teachers one paid afternoon to build something before they teach it.
- Put one robotics unit in the school day for an entire grade this year.
- Map after-school connectivity for your students, and invite the city and the library into the conversation.
- Invite three local employers to a planning meeting about what your students could build for them.
The case for coding, robotics, and making at school, along with a buying guide for districts, is in Screen Time Is Good.