Why I started using video games in my STEM classroom (and what it actually looks like)
The first time I let my seventh graders open Kerbal Space Program, I was half expecting chaos. It was a Thursday afternoon in the computer lab, and the room smelled like old carpet and hand sanitizer. A student named Marcus, who usually spent science class with his head on the desk, sat up the moment the game loaded. Within ten minutes, he’d built a rocket that wobbled off the launch pad and exploded. He laughed, but then he kept going. He didn’t look away from the screen.
That was three years ago. I’ve been teaching STEM at the same middle school since before the term “STEM” became a selling point on school brochures. I remember when we called it “science lab” and the big question was whether the vinegar rocket would reach the ceiling. I didn’t want video games in my classroom. I associated them with the kids who zoned out at home, and I had a rule in my syllabus: no phones, no games, no screens unless I said so.
Then our district bought a class set of laptops and started pushing “computer science integration.” The vice principal sent out a list of educational apps. One of them was Kerbal Space Program—a game where you build rockets and try to get little green astronauts to orbit. I almost deleted the email. But on day three of a unit on forces and motion, I was losing half the class to the ceiling fan, and I thought, fine, let them play.
Now, before you picture a classroom full of kids gaming all day, let me tell you what it actually looks like. I don’t hand them a game and say “have fun.” I hand them a card that says: Build a rocket that reaches an altitude of 5,000 meters without exploding. That’s the assignment. They have a budget of in-game parts, and they have to track their test flights in a notebook. If the rocket explodes, that’s not a failure—it’s data. I got that phrase from a Kerbal forum, and it’s the best thing I ever stole for my class.
Marcus, the kid who didn’t do homework, kept a log. His handwriting was messy and his spelling was shaky, but his notes said things like “more thrust at start” and “fins make it stable.” He was doing engineering iterations without knowing the term. When I called on him the next day to explain why his second rocket worked, he talked for two minutes straight. The kid who never raised his hand explained drag and thrust to a class that had stopped paying attention to me forty minutes earlier.
Other teachers asked me what I was doing differently. I told them: I didn’t change the curriculum. I changed the entry point. The students who struggled with worksheets could still struggle with a game, but it looked different. It looked like experimentation. It looked like them arguing with a partner about which fuel tank to use. The quiet ones, the ones who got lost in word problems, suddenly had something physical to point at.
Here’s what surprised me most. Video games don’t make every student engaged. Some kids honestly find them stressful. I had a student named Leah who couldn’t stand the timer in certain parts of the game. She was a good student, a careful reader, and she said the rocket building made her anxious because she didn’t know which parts were “supposed” to go together. That was a lesson for me. Games are not a magic fix. They’re just another way into the material, and some kids prefer the textbook. So now I offer both. On game days, there’s always a paper-based version of the assignment for students who want it. Leah builds her rocket on paper, calculates the scale, and I give her the same participation credit.
The other thing I learned is that the game is not the lesson. The lesson is the conversation that happens after the game. When I first started using Kerbal, I made the mistake of just letting them play and then expecting them to write a reflection. They wrote terrible reflections, all “it was fun” and “I learned about rockets.” So I changed the questions. Instead of “What did you do today?” I started asking, “What did you try that didn’t work, and what did you do next?” That simple question changed everything. It forced them to think about process. And at least once a week, a student brings up a solution they found themselves, and I step back and don’t even need to grade it.
I still have a love-hate relationship with game days. They’re louder than my regular classes. There’s the occasional argument over whose turn it is at the keyboard. I’ve had to gate off the “sandbox” mode because a few kids would rather build flying deathtraps than solve the actual problem. But I also notice that my office hours fill up with kids asking about orbital mechanics instead of asking if they can go to the bathroom. And Marcus—he failed my class in the fall. By spring, he was passing. I can’t say it was because of the video game. He told me he spent a lot of weekends watching Kerbal tutorials and building his own rockets at home. Maybe he just grew up a little. But I saw him teach two kids at the next table today, and his explanation was clearer than mine would have been.
I think about what I want parents to know. Some of them worry, and I understand why. Screen time is already a battle at home, and there’s a natural fear that school is just giving kids more of what they shouldn’t have. I tell them what I tell myself: the game is a tool, not a reward. If your kid comes home talking about why their rocket flipped over, or asking to watch a video about orbital reentry, that’s a good sign. It means the game is doing what a math worksheet couldn’t.
Do video games belong in every STEM classroom? I don’t know. It depends on the teacher, the students, and the school’s patience. The costs are real—time, noise, and the constant risk of a lesson devolving into a free-for-all. But I keep coming back to the same observation. There’s a difference between a student who is waiting for the bell and a student who is trying to solve a problem. I’ve seen both in my classroom, often in the same child.
Last week, Marcus showed me a rocket that made it to orbit. On paper, it wasn’t that impressive—fourth grade physics, maybe. But he stood there with his hands in his pockets and told me he was going to try to land on the Mun next. I told him the Mun was a lot harder. He shrugged and said, “It’s just data when it explodes.” I smiled. I didn’t tell him he’d absorbed my lesson. I just told him to get back to work. There are still forty minutes left in the period, and the ceiling fan is still spinning, but today, nobody’s watching it.
Please indicate: Thinking In Educating » Why I started using video games in my STEM classroom (and what it actually looks like)