Walls are a feature of making, not a bug in the studio. The kid will hit four kinds: the AI proposed something they didn’t like, the project broke, the playtest revealed their idea doesn’t quite work, or they’re bored. Each has a different parent move. None of them is “fix it for them.” The hardest one to learn (and the one that pays the most) is that being on the other side of a wall is what we’re trying to teach.
Four shapes of hitting a wall.
From watching kids in cohort and our own kids at home, frustration in the studio almost always falls into one of four shapes. Naming the shape is half of knowing what to do about it. None of these is bad. They’re the friction of real making, and most kids will hit all four within their first three or four sessions.
Shape one. The AI proposed something the kid didn’t like. Inkie ran a wizard and the ChangeDisclosure card shows a dragon that’s the wrong shade of green, a level layout that doesn’t match the feeling the kid was after, or a paragraph in the story that sounds nothing like the character. The kid wrinkles their face. This is the most common wall and also the easiest one.
Shape two. The project broke. A wizard introduced a bug. The game crashes on level start. The story file won’t open. The kid presses play and the screen goes black or the audio loops. This wall feels different. It’s technical. The kid usually thinks they did something wrong, even when they didn’t.
Shape three. The playtest revealed the kid’s idea doesn’t work. The kid built exactly what they wanted, ran it, and found out that the thing they wanted isn’t fun. The boss fight is too easy. The puzzle is unsolvable. The story’s ending doesn’t land. This wall is the deepest because the problem isn’t the AI or the software. It’s the kid’s original idea, and the artifact is what revealed it.
Shape four. The kid is bored. The wizard takes too long. The project is at an awkward middle stage. Nothing’s on fire but nothing’s exciting either. The kid’s eyes drift. This wall looks like the others but isn’t. It’s an energy wall, not a creative one.
The move for each one.
The studio’s decision row is the parent’s first ally for shape one. The kid is looking at three buttons. They don’t have to know which to press.
For shape one, the move is to point at the Review button (not the change) and ask “what do you want it to look like instead?” The kid tells you. They press Review. Inkie tries again, closer this time. The studio architecture made the wall undo-able, which means it isn’t really a wall. It’s a wrong first take, and the kid has the affordance to keep iterating until it’s right.
For shape two, the move is different. A broken project isn’t the kid’s fault and they shouldn’t carry it. Press Undo on the last change if you can see what introduced the bug. If you can’t, send a screenshot from the in-studio bug-report button. The studio team will respond, usually within a few hours. While you wait, the kid does something else. The page at /parents/safety has the bug-report walkthrough and the typical response window. This is the one wall where it’s genuinely fine for the parent to handle the procedural part. Just don’t narrate the fix as if the kid did something wrong, because they didn’t.
For shape three (the playtest wall), the move is a conversation. Not a fix. Ask the kid what they noticed when they played it. Most kids can describe the problem precisely when asked the right question. “The boss was easy because I made the player too strong.” “The puzzle’s answer was on the same screen as the puzzle.” The kid is doing the diagnostic work. Your role is to listen long enough for the diagnosis to surface. Then ask what they want to change. They’ll go run a wizard. Shape three is where iteration is born. Don’t skip past it.
For shape four, the move is to leave. Close the laptop. Go outside. Eat a snack. The boredom wall almost always dissolves when the kid’s body is doing something else for fifteen minutes. We’ve written about why the studio doesn’t try to hold attention against the kid’s will at why we don’t track screen time. The short version: sessions that end when the kid is ready produce kids who want to come back. Sessions that grind through boredom produce kids who don’t.
The praise question.
Across all four walls, what comes out of your mouth matters as much as which move you pick. Carol Dweck’s research on praise, beginning with her 1998 paper with Claudia Mueller and synthesized in her 2006 book Mindset, found that the kind of praise a kid hears after a difficulty shapes how they handle the next one.1 Praise effort, strategy, or specific decisions and the kid develops a working theory that difficulty is something they can work through. Praise the outcome or the kid’s underlying ability and the kid develops a working theory that difficulty means they’ve hit their ceiling.
In studio terms this is concrete. When the kid pushes through a wall and finally gets the thing they wanted, the wrong response is “wow, that looks great.” The right response is closer to “you tried three different versions before that one. The third one was the one that worked. How did you know?” The kid will answer. The answer is the lesson. You just gave them the language for their own iteration.
The wall is the part where the kid learns who they are when something doesn’t work the first time. On the praise question
Our piece on iteration is the move walks through the longer version of the Dweck argument and how it ended up wired into the Keep / Review / Undo decision row. The short version for these walls: praise the decision the kid made, not the thing they ended up with. The thing they ended up with is theirs. The decision is what they’re learning.
Theo’s Achilles is a useful example because we have real data on it. The level-3 arrow-trap mechanic took four undone changes before it felt right.
Four undos is not a kid losing patience. It’s a kid developing taste in real time. The praise that worked at the table afterward was: “you pressed Undo four times. Most kids would have kept the first one. How did you know it wasn’t right yet?” He thought about it and said “it didn’t feel scary.” That sentence is a nine-year-old naming his own aesthetic. The praise made the decision visible to him.
When walking away is the answer.
Some walls don’t want to be solved at the keyboard. The kid has been at it for forty minutes, the wizard has missed three times in a row, the boredom-and-frustration combination is starting to compound. The parental instinct in this moment is to step in and unblock. Resist it. The instinct after that is to push the kid to keep going (“you’ve almost got it”). Resist that too.
What works is the smallest possible exit ramp. “Want to come back to it later?” The kid usually says yes. They close the laptop. Twenty minutes later, the project is still there waiting. The kid’s body has reset, their working theory has had time to consolidate, and they often come back with the next move already in mind. Productive failure, in Manu Kapur’s formulation, depends on the kid’s ability to walk away from a problem with the problem still alive in their head.2 The walking-away is part of the productive part.
The other version of walking away is finishing the session on a small win. If the kid is close to a wall, suggest a small wizard you know will land. Add a new sound effect. Change a character name. The kid presses Keep, the change works, the session ends with a small forward step. Albert Bandura’s work on self-efficacy is the technical name for what you just built: a small recent success the kid can carry into the next session.3 They’ll open the studio tomorrow remembering that they shipped something, not that they got stuck.
The deeper lesson.
The reason any of this matters is that the wall is the project. Not the part before the wall. Not the part after. The wall itself. Every real project has one or several. Learning to be on the other side of a wall, with the project still alive, is the thing the studio is trying to build. The artifact is the visible output. The skill is the durable one.
Most kid software hides walls. The friendly bounce-back animation, the “try again” voiceover, the soft pivot away from anything that didn’t work. The studio doesn’t. The wall is in plain sight. The decision row, the bug report, the conversation about the playtest, the walk away and come back. Each one is a place where the kid develops the muscle that a creative life depends on: I’ve seen this kind of difficulty before. I have moves for it. I’m the kid who pushes through.
That’s what you’re building when you don’t fix it for them. It looks like sitting on your hands. It’s actually the most active thing a parent can do.
If you want the deeper pieces, our walkthrough of iteration is the move covers the Dweck research and the decision row. The piece at a parent’s first 30 minutes is the version of this post for the very first session. Or play Theo’s game at god-games.vercel.app to see what an artifact with four undos in its history looks like on the other side.
References
- Carol S. Dweck, Mindset: The New Psychology of Success, Random House, 2006. See also Claudia Mueller & Carol Dweck, “Praise for intelligence can undermine children’s motivation and performance,” Journal of Personality and Social Psychology, vol. 75, no. 1, 1998 — the foundational paper on the praise distinction.
- Manu Kapur, Productive Failure: Unlocking Deeper Learning Through the Experience of Failing, Wiley, 2024. Two decades of empirical work on the role of struggle and walking-away in durable learning.
- Albert Bandura, Self-Efficacy: The Exercise of Control, W. H. Freeman, 1997. The foundational work on how recent mastery experiences shape a learner’s sense of agency.