Building It With Them, Not For Them

"Never help a child with a task at which he feels he can succeed." — Maria Montessori

Almost every parent who builds a robot with a kid slides into some version of this. In week one the kid is thrilled. By week three the parts are late and the event is a month away. In week five something doesn't fit, it's nine at night, and you take the piece out of their hands because it'll be quicker. By week six you're building a robot and your kid is watching you do it.

Nobody sets out to do that. It happens one sensible decision at a time, each one faster than the alternative.

It's the least technical part of the course, and it's the part most likely to decide whether there's a second season.

Why it happens

There are three pressures, and they all push you the same way.

Time. You can do it in ten minutes and they'll take an hour. On a Tuesday in week two, the hour is fine. In the last week before the event, it feels impossible.

Money. These are real parts, and some of them cost twenty dollars. Handing a twenty-dollar motor to someone who might break it goes against every instinct you have.

Danger. A soldering iron is hot, the lithium batteries these robots run on (LiPos) can catch fire if they're mistreated, and a weapon is a weapon. Some of that caution is right, and you shouldn't talk yourself out of it.

Follow any of them without thinking and it ends with you holding the robot. So decide ahead of time where each one really applies, while you're calm and it's still week one.

Decide who owns what before you need to

At the start, sit down together and make two lists, out loud, and write them down.

What's theirs, for good. Their decisions stand even when you'd have chosen differently. This list has to include things that actually matter, or it's just for show.

What's yours, for good. The things that are truly dangerous or can't be undone. Explain why once, and then don't reopen the argument every week.

The most important list is the one in between: things that are yours for now and become theirs later. Name them at the start, along with what has to happen for each one to move over. Something like, "You solder with me watching until you've done six joints that hold, and then it's yours." A kid who can see the ladder will put up with being on the bottom rung. A kid who thinks the bottom rung is permanent stops trying to climb.

What kids can actually take on

Treat these as rough guides rather than rules, because a motivated nine-year-old will outdo a bored thirteen-year-old at all of it.

Almost any age, with supervision: driving practice, weighing parts, sorting and counting hardware, running the checklist, packing the pit box, photographing the build, choosing the paint and the name.

Around eight and up: assembling with hex drivers, tightening setscrews (the tiny headless screws that lock a part onto a shaft), applying thread locker, taking the robot apart and putting it back together, preparing a part in the slicer software and starting a print, running the pre-event checks.

Around ten and up, with real teaching: soldering under supervision, wiring the harness, working out a fault from what the robot is doing, reading the ruleset and finding an answer in it.

Usually yours for a while: charging and disposing of the batteries, anything involving the weapon while it's powered, and the final safety check.

The name and the paint job are what the kid will remember, and they're what makes it their robot in the way that matters most to them. Don't treat them as busywork.

The slump around week four

Somewhere in the middle, interest drops off. That's normal, and it doesn't mean you picked the wrong project.

It comes down to how the project is shaped. Weeks one and two are decisions and shopping, and those feel like progress. Weeks four and five are waiting on parts and waiting on prints, and those feel like nothing is happening. A kid has no way of knowing that ahead of time.

A few things help.

Warn them early. Try something like, "There's going to be a boring stretch around week four where we're waiting on parts and it feels like nothing's happening. That's normal, and it passes." Once you've said it ahead of time, the slump feels like something expected rather than like the project failing.

Keep one thing they can see moving. A print running, a part getting painted, ten minutes of driving. Something they can watch change.

Start driving practice early. Module 12 makes the case that practice is the best use of time in the whole project anyway. It's also the only part of the build that's fun right away, needs no parts, and gets visibly better.

Let them make a wrong call that costs something small

This is what makes it a project the kid did rather than a project the kid watched.

Pick a decision where getting it wrong costs less than ten dollars and a reprint, and make it truly theirs. Wheel size, weapon shape, or which of two colors. Then let it play out, even if it goes badly.

The learning comes from watching something you chose turn out differently than you expected. A kid who's had one decision go wrong and then fixed it understands something about building that no amount of good advice can get across.

Don't step in to rescue it. And don't say "I told you so," because that turns a lesson into a grudge.

When time gets tight, hand over more

Late in the build, when things are tight, the instinct is to take over, because the deadline is real.

Try handing over more instead, and make up for it by cutting something else. A simpler weapon the kid built beats a better one you built, because the weapon was never the point.

If you really do have to take something over, say what you're doing and why, and say it's temporary. "I'm going to do this joint because we're out of time, not because you can't." That takes four seconds to say, and it's the difference between a kid who feels helped and one who feels replaced.

At the event

Decide who's driving before you get there, not while you're standing in line. If it's the kid's robot, the kid drives, including in the match you can already tell they're going to lose.

Let them do the repairs, and stand a little further back than feels comfortable. The pit area is loud and rushed, and it's where parents most often take the soldering iron out of a kid's hand. If something really is beyond them, someone two tables over will usually help, and getting help from a stranger who builds robots is a better experience for a kid than getting rescued by their parent.

Their robot is going to get wrecked. Tell them ahead of time that this is what normally happens and it isn't a failure, and then when it happens, act like you meant it. The kid will read your face before they look at the robot.

What they actually take away

The robot is just the vehicle. What lasts past the season is a short list, and none of it is really about robots.

They learn that a hard thing is a string of small, ordinary steps. Nothing in this build takes talent. It just takes doing the next thing.

They learn that the boring middle is part of it, and that the people who finish aren't the ones who stayed excited the whole way through.

And they learn that something you made can get destroyed and you can make it again. That's the big one, and it's why the plastic class is such a good place to learn.

Before you start, take five minutes to set up a record

Pick somewhere to keep notes. A shared note, a folder, or a notebook by the workbench all work.

Four lines per session: what we did, what broke, what we learned, and what's next. Have the kid write it when they can.

The record is the raw material for the rebuild, it settles "didn't we already try that?" arguments in week five, and ten years from now it'll be the only record of this that still exists. Set it up before the fun starts, and don't make remembering it the kid's job.