What happens to a project that fails

Not every project in our room gets finished. A robot never quite gets the arm working right. A story gets three chapters in and stalls. A game idea turns out to be more scope than a kid wanted to carry to the end. If our marketing only showed the projects that shipped clean, you'd be forgiven for thinking failure is rare here. It isn't, and we don't treat it as a problem to hide.

Abandoned isn't the same as wasted

A project that doesn't get finished still did its job if the kid learned something specific from working on it — a new tool, a new debugging habit, a clearer sense of what she actually wants to build next. We ask kids to be able to say what they learned even from a project that's going in a drawer, and almost always they can, in more detail than they can about a project that went smoothly. Struggle produces more specific memories than ease does. A kid remembers exactly why the robot arm never worked in a way she won't remember exactly why a simple project that went fine, went fine.

What we don't do

We don't quietly finish it for her so there's something to show at pickup. That would turn the project into a prop instead of hers, and it would teach the wrong lesson entirely — that an unfinished thing is an emergency an adult needs to solve rather than a normal outcome she can walk away from. We also don't push every kid to finish every project on principle. Persistence matters, and we do coach toward it, but forcing a finish on something a kid has genuinely lost interest in produces resentment, not grit.

The actual conversation with a stalled project

A mentor's job here isn't cheerleading and it isn't grading — neither is really what the mentor role is for — it's asking a specific, useful question: is this stuck because something's hard and worth pushing through, or stuck because the idea itself has stopped being interesting to her? Those get different responses. The first gets more time and maybe a nudge in the right direction. The second gets permission to set it down, on purpose, with the parts that did work named out loud before she moves to the next thing.

Why this matters more than it looks like it does

A room where every project has to succeed teaches kids to only attempt things they're already confident about — which is a small, safe, and ultimately boring set of things to spend a year building. A room where failure is a normal, undramatic outcome teaches kids to reach past what they know they can pull off, because the downside of missing isn't shame, it's just moving on to the next attempt with slightly more information than they had before.

What a parent sees

Sometimes a kid comes home with nothing to show for a session, and that's a hard thing for a parent to watch without worrying. Ask what she tried and what got in the way, the same way you'd ask about a session that went well. If she can answer, the time wasn't wasted — it just didn't produce an object. Most of what a kid actually gains here isn't the object anyway.