Facilitate, Don't Fix: Let Kids Solve It
The moment you grab the glue gun and 'just show them quickly,' the learning walks out the door.

On this page
You know the feeling. A student's circuit won't light, their tower keeps toppling, their code throws the same error for the fifth time. They look up at you, and every instinct says step in and fix it. It's faster. It's kinder. It's also the moment they stop learning.
Most of us were never taught the other move: being genuinely helpful without taking the work out of a kid's hands. That move has a name, and a whole research-backed practice behind it.
In this guide:
- What "facilitate, don't fix" actually means
- Why hands-off help leads to deeper learning
- A clear, repeatable way to do it in class
- A real example from a middle school science room
- Variations, common mistakes, and FAQs
What is "facilitate, don't fix"?
It's a way of helping where you support a student's thinking instead of solving the problem for them. You watch, you ask questions, you point them back to their own ideas — but you keep your hands off the project.
The phrase comes from the Exploratorium's Tinkering Studio in San Francisco, which developed it through years of running open-ended maker activities like marble machines and paper circuits. Their facilitators are trained to "observe, not interrupt" and to "offer prompts to deepen rather than resolve struggle." In plain terms: your job is to keep the struggle productive, not to end it.
This isn't the same as ignoring kids or refusing to help. You're very much there, very much engaged. You're just helping in a way that leaves the learning where it belongs.
Why does it work?
Because the person doing the thinking is the person doing the learning. When you fix a student's project, you do the valuable cognitive work — noticing the problem, forming a theory, testing it — and they get a working project but none of the understanding.
The Tinkering Studio's framework, developed with researchers at Harvard's Project Zero, names four "Learning Dimensions" they watch for: engagement, initiative, social scaffolding, and development of understanding. Notice that not one of them is "the project works." A finished project tells you nothing. A kid who set their own goal, hit a wall, formed a hunch, and tested it — that's the whole point.
There's a motivation angle too. The Tinkering Studio team puts it simply: self-direction produces durable motivation and agency. When a student cracks a problem themselves, they trust they can crack the next one. When you crack it for them, you quietly teach them to wait for the adult. Over a year, those two paths produce very different learners.
And here's the part that surprised me most: engaged kids actually want the struggle. As the Tinkering Studio notes, when learners are genuinely engaged, they tolerate productive struggle — they'll return to the same ramp angle a dozen times. Rescuing them too early doesn't relieve frustration. It cuts off the satisfying part.
How to run it, step by step
You don't need a makerspace to use this. You need a few questions ready and the discipline to keep your hands still. Here's the sequence I use.
Pause before you move. When a kid gets stuck, count to five before doing anything. Most of the time they'll try something in those five seconds. Resist the reflex to reach for the materials.
Lead with "What are you trying to do?" This is the Tinkering Studio's first move, and it does two jobs: it makes the student name their own goal, and it tells you what they actually want — which is often not what you assumed.
Then ask "What have you tried?" Now you find out where their thinking is. You'll often hear them solve it out loud while answering. If they haven't tried anything, that's your real problem to address — gently push them to take one small action.
Probe, don't tell. Use questions that send them back to the work: "What do you think will happen if...?" and "Why do you think that happened?" These two prompts come straight from the framework and they're remarkably hard to answer without thinking.
Offer a provocation, not a solution. If engagement is fading, reignite it instead of resolving it: "Can you make it spin?" or "What would happen with a heavier one?" You're adding a challenge, not removing the obstacle.
Point sideways to a peer. "Maya's mechanism does something like that — go ask her how." This builds the social scaffolding dimension and gets you out of the role of sole answer-giver.
Step back and let them work. After a prompt, physically move on. Hovering signals that you're about to take over. Walking away signals that you trust them.
A real example: 7th grade science, paper circuits
Here's how it looked in a seventh-grade physical science class building paper circuits — copper tape, a coin-cell battery, an LED on a folded card.
A student named Daniel had a circuit that wouldn't light. The old me would have spotted the reversed LED in two seconds and flipped it for him. Instead I crouched down and asked, "What are you trying to do?" He said, "Get this light on, obviously." Fair. So I asked, "What have you tried?"
He listed it: new battery, pressed the tape down, checked the bulb in his neighbor's working circuit. Good troubleshooting, actually. So I pointed at the LED legs and asked, "Why do you think that one worked in Sara's card but not yours?" He stared, then said, "Wait — does it matter which leg goes where?" I just raised my eyebrows and stepped back.
Thirty seconds later: "It's the long leg! It has to touch the plus side!" He'd discovered LED polarity on his own — and he taught it to two other kids at his table within the minute. If I'd flipped that LED myself, he'd have a glowing card and no idea why. That's the trade in one small moment.
Variations and when to use it
For very young children, lean almost entirely on observation and provocations. Long questions lose them. "Ooh, what's it doing?" and "Can you make it taller?" go further than "what have you tried."
For a stuck whole class, turn it into a quick share instead of fixing thirty projects one by one. Pause everyone and ask two students to describe a problem they hit and what they're trying. Peers solve more than you'd expect.
Use it most in open-ended work: making, design, problem-solving, coding, lab investigations, writing conferences. Any time there's no single right path, facilitation beats fixing.
Ease off it when a student is in real distress, when safety is involved, or when they're missing a piece of information they genuinely can't reason their way to. Productive struggle is the goal; pointless struggle is not. Teach the fact, then hand the thinking back.
Common mistakes to avoid
The biggest one is asking a question and then answering it yourself two seconds later. Silence feels uncomfortable, but it's where the thinking happens. Wait longer than feels natural.
Another is the fake question — "Do you think maybe the battery is backwards?" That's a fix wearing a question costume. Kids see through it instantly. Ask real questions you don't already answer in the asking.
Watch out for hovering, too. Standing over a table with your hands twitching toward the materials tells students you're about to rescue them, so they wait. Ask your question and physically move away.
And don't measure your lesson by how many projects worked. A room full of finished-but-not-understood projects is a worse outcome than a messy room full of kids who figured something out. Judge the thinking, not the gluing.
How UNI-FIED helps
If you want to use this without rewriting your prep from scratch, UNI-FIED builds routines like "facilitate, don't fix" right into ready-to-teach activity cards for your exact topic and grade. Each card comes with the facilitation prompts already written — the "what are you trying to do?" and "why do you think that happened?" questions matched to the task — so you can keep your hands off the project and your questions ready. It's the practice, packaged so you can actually run it tomorrow.
Frequently asked questions
Isn't this just slower? In the moment, yes, slightly. Over a unit, no. Kids who learn to troubleshoot stop needing you for every snag, which frees you up enormously by week three.
What if a student gets genuinely frustrated and gives up? That's your cue to step in — but with a smaller prompt, not the answer. Lower the bar ("just get one part working first"), or send them to a peer. Save the direct fix for true dead ends.
Does this work for non-maker subjects? Yes. The same questions work in a writing conference, a math problem, a debugging session, or a history source analysis. Anywhere there's thinking to protect, it applies.
How do I stop myself from jumping in? Literally put your hands behind your back or in your pockets when you crouch down. Sounds silly; works. If your hands can't reach the materials, you'll talk instead.
What's the research behind it? The framework comes from the Exploratorium's Tinkering Studio, developed with Harvard's Project Zero, based on years of watching what engaged, learning-rich making actually looks like.
Try it once tomorrow: next time a kid looks up stuck, ask "what have you tried?" and then count to five.
Sources & further reading
Run this in your classroom tomorrow
UNI-FIED turns your topic, grade, and lesson length into ready-to-teach activity cards built on routines like this one — no prep, no curriculum change.
See how UNI-FIED worksRelated routines
Published September 21, 2026.