How I Teach 7th Grade Girls to Think Like Problem-Solvers Without Calling It That

There’s a moment I’ve seen happen over and over with middle school girls, especially around seventh grade. It usually happens quietly, almost too quickly to notice if you aren’t paying attention.

A student figures something out.

Maybe she fixes a broken formula in a spreadsheet after twenty minutes of frustration. Maybe she realizes why a 3D print failed and adjusts the supports so it works the second time. Maybe she traces a discrepancy in a dataset back to the original source and catches an error nobody else noticed.

And for just a second, her face changes. Not exactly pride. More like surprise. Like she didn’t expect herself to be the kind of person who could solve that kind of problem. Then the moment passes, somebody says something ridiculous about lunch, and she goes right back to being a seventh grader.

I’ve been teaching for fifteen years, and during that time I’ve also spent years building websites, working with databases, troubleshooting technology, and creating digital tools. Officially, I currently teach seventh grade Science and Catholic Religion, which sounds like a combination that shouldn’t naturally lead into technology and problem-solving conversations. But honestly, teaching middle school has made me think more deeply about how people learn than any technical job ever did.

Especially girls. Because by middle school, many girls have already quietly decided what kind of person they are. And maybe more importantly, what kind of person they are not.

I hear it constantly. “I’m bad at science.” “I’m not good with technology.” “I can’t do math.” Sometimes they say it casually, almost like they’re discussing eye color or height — just another fixed fact about themselves they’ve accepted as true. The thing is, most of the time they’re wrong.

But once a twelve-year-old believes something about herself, directly arguing with her rarely changes anything. Telling a girl she’s “smart enough” usually doesn’t work because the issue isn’t intelligence. It’s identity. She has already absorbed years of subtle messaging about who technology belongs to, who is “naturally good” at logical thinking, and who is expected to struggle.

So I stopped approaching it directly.

I don’t call activities “coding” unless absolutely necessary. I don’t frame things as STEM enrichment or computer science practice. The labels themselves often create resistance before students even begin. The second some students hear the word “coding,” they mentally sort themselves into categories: kids who can do this and kids who can’t.

Instead, I give them problems. Real ones. I’ve found middle schoolers will tolerate an astonishing amount of complexity if the situation feels authentic. If something feels like a puzzle or a mystery, they lean in naturally in a way they often don’t with traditional assignments.

Last spring, I brought in a genealogy problem I had been trying to sort out myself. I had conflicting records for a woman born in the late 1800s. One census record listed an age that clearly didn’t line up with the other documents I had found. Something was wrong somewhere, but I genuinely didn’t know whether the issue was a transcription error, bad handwriting, inaccurate census reporting, or something else entirely.

We spent two class periods investigating it.

The students cross-checked records, compared timelines, debated possibilities, and started building theories. One girl who had spent half the year insisting science “wasn’t really her thing” ended up creating a color-coded timeline in Google Sheets tracking source reliability and conflicting evidence.

She didn’t think of herself as doing data analysis. She thought she was solving a mystery. And honestly, that distinction matters more than people realize.

Middle school students, especially girls, often engage more deeply when the focus shifts away from performance and toward curiosity. If they think the goal is to “be good at STEM,” many immediately become self-conscious. But if the goal is figuring something out, they forget to monitor themselves so closely.

That’s when the real thinking starts.

I’ve noticed the same thing with technology tools. Early on, I made the mistake of trying to “sell” the technology itself. I would introduce programs or devices with excitement, expecting students to be impressed. What I eventually realized was that overhyping the tool often backfires because it shifts attention onto whether students feel capable of using it.

Now I intentionally make the tools feel ordinary.

The spreadsheet is “just a way to organize information.” The database is “just helping us keep track of patterns.” The 3D printer is “just the thing we use when we need to make an object.”

Once the technology stops feeling magical, students stop treating it like something reserved for “tech people.”

The 3D printer, interestingly, changed classroom dynamics in ways I never expected. What surprised me most wasn’t how excited students were when projects worked — it was how calmly many of them handled failure. And in 3D printing, failure happens constantly.

Prints collapse. Supports fail. Layers shift. A design that looked perfect on screen turns into a tangled pile of plastic spaghetti twenty minutes later. At first, I expected students to become frustrated or discouraged, especially students who tend toward perfectionism academically.

Instead, many of the girls who are terrified of getting answers wrong on tests became remarkably resilient when troubleshooting print failures. I think part of the reason is that the failure feels externalized. The object failed, not them. So instead of shutting down emotionally, they naturally move into problem-solving mode. They adjust settings, rethink supports, resize pieces, and try again.

Watching that happen changed how I talk about mistakes in general.

Middle school girls are often deeply afraid of being wrong publicly. Not because they lack ability, but because they’ve learned to associate mistakes with embarrassment instead of learning. You can see it in classrooms constantly — the hesitation before answering, the apologetic tone when they’re uncertain, the relief when someone else volunteers first.

So I’ve become intentional about normalizing mistakes.

I make errors openly in front of students and narrate the process of fixing them. If I misread data or break a formula, I don’t hide it. I model what troubleshooting actually looks like. I also try not to immediately correct partially wrong answers. Instead, I’ll ask students to explain their thinking further, because often they uncover the mistake themselves while talking.

That moment matters.

Finding your own error teaches confidence in a completely different way than simply being corrected by someone else.

At the end of the day, though, what I want students to leave with isn’t really coding ability or even technical knowledge specifically. Those things are useful, but they aren’t the core goal.

What I actually want is for them to experience being stuck on something difficult without immediately deciding they are incapable. I want them to wrestle with problems long enough to realize confusion is survivable. That uncertainty doesn’t mean failure. That not knowing something right away is not evidence they “aren’t that kind of person.” Because honestly, that may be one of the most important things middle school girls can learn.

The educational system rewards quick correct answers so consistently that many students never develop comfort with sustained uncertainty. But real problem-solving almost always involves uncertainty. It involves trying approaches that fail, retracing steps, asking questions, and sitting in discomfort longer than feels convenient.

When a student experiences that process successfully — even once — it changes something. The student who has spent forty minutes troubleshooting a problem and eventually solved it learns something much more important than the answer itself. She learns she can handle not knowing. And once a girl realizes that, a lot of doors open.

The student who built the genealogy timeline, by the way, eventually concluded that our mystery woman had likely lied about her age in census records because she was older than her husband. She presented her findings to the class, walking everyone through the evidence carefully and confidently. By the end of the presentation, she did not sound like someone who thought science wasn’t her thing anymore.