Great STEM Programs Shouldn’t Just Offer Content or Technology

They Should Offer the Moment a Learner Realizes: “I Can Make Something Work”

There’s a moment in a STEM classroom when everything slows down and attention narrows.

It’s the moment when a team is ready to run their robot, and the room notices.

• A student turns on the power to their robot,
• they clear the area of obstacles,
• one last check of their code,
• and then…

They hit go and watch something they built finally behave the way they intended. A mechanism transfers motion cleanly. A circuit closes and stays closed. A robot follows a path that previously existed only in the team’s imagination.

To the learner, the room takes on a held-breath kind of feel as they focus on their creation. They aren’t confused or afraid. They’re absorbed in something new, something important, something that has never happened before.

This worked. And it worked because I made it work.

Great STEM programs don’t succeed because of the content they deliver or the technology they provide. They succeed because they create that moment. The moment when a learner realizes their creativity and thinking can cause something real to happen in the world.

What I Learned First as a Teacher

Before I was an engineer or an author, I was a classroom teacher. I tried to teach physics the traditional way:

• have students read the book and write out notes,
• teach the content,
• give homework problems from the book
• give a test.

But what I found was – it didn’t work very well. Kids weren’t really learning. They were memorizing just enough to get by. So, I shifted gears and tried designing learning experiences that felt real to students rather than performative. I used toys to teach projectile motion. I used Christmas tree lights and electric motors to teach electric circuits. I used Matchbox car launchers to teach Newton’s second law. My students didn’t just write down the equations; they experimented with them in ways that were relevant to them.

One of the most effective projects I ever ran was a Rube Goldberg machine challenge. Each group of students received a simple wooden frame, two feet tall, built from 1.5”x1.5” pieces of wood. The requirements were intentionally spare. Their machine had to accept a ball bearing at a height of one foot, raise it to one and a half feet, and then deliver it to the next machine in line.

That was the entire assignment.

There were no instructions, no diagrams, and no examples to copy. This was not an oversight. It was a deliberate decision. The absence of instructions forced students to confront the problem directly rather than search for the “right” way to do it.

Students brought in springs, scraps of metal, electric motors scavenged from old toys, and whatever else they could imagine using. I provided additional hardware and tools, and I handled the parts that crossed into genuine danger – I drilled holes, I managed sharp edges, and I made sure no one got hurt. Everything else belonged to them.

The thinking, the design, the failures, and the revisions were theirs.

Why Constraints Beat Instructions

Testing day was always the moment everything became real. We lined all the machines up across the room, one feeding into the next, creating a single system rather than a collection of isolated projects. One ball bearing. One continuous run.

Sometimes the ball made it through two machines and failed on the third. Sometimes it jammed. Sometimes it dropped to the floor immediately. And sometimes, after days of trial and error, it traveled cleanly through nearly every creation.

When it worked, there was no argument.

Reality made the call.

What I was assessing had very little to do with recall or compliance. I was watching for things that cannot be faked:

• Cause and effect
• Systems thinking
• Iteration under constraint
• Responsibility for outcomes

What emerged from that process wasn’t just understanding, but confidence. Not the kind that comes from praise or grades, but the quieter kind that comes from evidence. When a student watched their machine finally work, they didn’t feel successful because an adult approved of it. They felt successful because the world responded to their thinking. That kind of success builds self-esteem that lasts, because it’s grounded in something real.

Students stopped asking whether something was “right” and started asking why it didn’t work. That shift matters because it moves learning from performance to ownership. When a machine finally worked, students knew exactly why, and they knew it had happened because of their thinking.

And I saw the pride on their faces.

Years later, I felt that same moment again outside the classroom. While working as an engineer, I was writing automation software, translating intent into code and code into physical action. When a program finally ran the way I’d imagined, the satisfaction I felt was familiar. Something in the world behaved differently because I had thought carefully and acted intentionally.

Different tools. Same moment.

Why Robotics Programs Resonate

This is why well-designed robotics programs resonate so deeply with students and educators alike. Programs from companies like VEX Robotics and Wonder Workshop are effective not because of their hardware or software, but because they engineer that same moment of agency.

A robot matters because it responds to intent. When students build and program something that behaves exactly as they planned, they aren’t just learning STEM concepts. They’re learning that their thinking matters, that their choices have consequences, and that effort can change outcomes.

That lesson doesn’t feel abstract. It feels earned.

Creation, Ownership, and Identity

I saw a similar moment again through writing. Helping kids write their own stories and self-publishing them on Amazon produces a familiar scene. An Amazon box arrives. It gets opened carefully. Inside is a real book, with the child’s name on it, something that never existed before they imagined it. And then the smile… I’ve seen this many times, thanks to parents and their videos, and it’s heartwarming to see.

I remember opening that box with my first novel inside. No one forgets that moment, because once again, it’s not about the object. It’s about proof.

Teaching, engineering, robotics, and writing look unrelated on the surface, but they share a common structure. They give learners real constraints, real tools, and real responsibility, while balancing freedom with support. When learning works this way, confidence is not given. It’s earned.

And it almost always ends with the same realization:

“I made that work.”