Engineering day. Cardboard fails at the joins, so today is about joins - and about undoing work that isn't good enough, which is harder than doing it the first time. Town Hall asks where we haven't been role models this week. Team 3 goes up to Spark.
By 2:40 today every boat has been sat in, wobbled, and repaired - and the studio has said out loud where it fell short of being a role model this week.
Publicly, one at a time. Failures happened where they're cheap instead of on Friday where they're not.
At least one team replaced a taped join with a fold. Redoing is the skill of the day.
Town Hall produced something uncomfortable and nobody was punished for saying it.
Standard rhythm. Thinking Puzzle up by the cubbies.
Standard rhythm.
Talking points, not a script. Hit these in your own words - the studio can tell the difference, and the ones that land are the ones you actually mean.
The team going up today has four hours to think about it. That's better than four minutes. These aren't warm-up games - each is a situation a D2 learner is genuinely likely to hit in a Spark room. Running it at 8:30 lets it sit at the back of their head all morning, instead of being handed to them on the way out of lunch.
The setup (3 min):
“Third day of the rota. One Spark learner has decided you're hers. She sits with you every time, saves you a spot, holds your hand on the stairs, and tells the other kids you're her reading buddy.
It feels great. Be honest - it does.
Across the room there's a kid who hasn't spoken to anyone all week.”
The harder half (2 min):
“Today she grabs your arm the second you walk in. And the quiet kid looks up, sees you're taken, and goes back to his book.
What do you do? And be careful - if you just walk away from her, what have you taught her?”
The thinking (6 min):
The move (4 min) - land it on something they can say out loud:
The teaching underneath: this is the week's central idea in its warmest disguise. Being chosen feels like success, and it's the thing most likely to stop a mentor doing the actual job. The kid who needs you least is usually the one asking loudest.
This one often surfaces something real from D2's own studio - who gets picked, who doesn't. Let the connection be made if a learner makes it, but don't force it, and don't let it turn into naming names.
Today's briefing (5 min):
Two or three members of Team 2, five minutes flat, one question only:
"What should today's team know before they go up?"
This is a handover, not a debrief - it exists to brief the team who leave at 12:55, which is why it can't wait until the afternoon. The fuller three-question version happens at 3:10 Reflection, once today's team has been up and can answer it too.
Keep it tight. If it runs long it eats the dilemma, and the dilemma is the thing they actually need.
Standard rhythm.
Standard rhythm.
Standard rhythm.
Standard rhythm.
Learner-led, rotating leader - not the same learner who led Town Hall #2. Coach them Monday or Tuesday.
Agenda:
The second question will produce something about the boat teams - a takeover, an argument, someone frozen out. That is exactly what you want, and it is far more useful than anything about Spark. Resist the urge to defend anyone, including yourself. Write down what's said and bring it back on Thursday.
Lunch and downtime, uninterrupted. Nothing is scheduled in this hour and nothing should be. The dilemmas run at 8:30 now, precisely so this stays clear.
12:55 - Team 3 leaves. The one exception, and it applies to the day's Spark team only. Everybody else stays at lunch until 1:00 as normal.
Remind Team 3 at the start of lunch, not at 12:54. They should be moving before the Spark learners do, so they arrive in position rather than into the middle of a transition.
12:55 - today's team leaves. Team 3 heads upstairs. They go up before the Spark learners move so they're already in position rather than arriving into chaos.
Their three jobs, in order:
Meanwhile in D2: everyone else runs D.E.A.R. as normal, 1:00–1:30. Nobody misses anything by going up, and nobody misses anything by staying.
Say it to the team on the way out, every single day: "You're not the guide. You're the role model. Notice, wait, and ask - don't fix.say this exactly" The failure mode for D2 this week is enthusiastic overstepping, and it comes from good intentions every time.
1:30 - Team 3 comes back down and writes while it's fresh. Twenty minutes, in the Spark journal, four questions. Same four every day so the entries can be read as a set on Thursday.
Guide moves: read over shoulders and push question two. Learners will write "Spark was loud" - that's an observation about Spark, not an answer. The question is what they found hard. "I got impatient" is the answer you're looking for, and it takes a prompt to get there.
Everyone else, 1:30–1:50: keep reading, or start hauling boat materials out so Quest opens with zero setup time. Quest is only 50 minutes and this week every minute of it counts.
The engineering session - and the one where teams find out whether Monday's negotiation actually held. The skill on the table is redoing work you already did. Every team will have to undo something today, and how they handle that is more revealing than how they handled building it the first time.
The seam problem (5 min) - demonstrate, don't lecture:
Take a taped cardboard joint, hold it in a tub of water for thirty seconds, and pull it apart in front of them.
"Cardboard doesn't fail in the middle. It fails at the joins. Every seam is a place your boat can let water in, and today is seam day."
Three rules on the board, and they stay up for the rest of the build:
Jobs rotate (30 seconds). New job for everyone today - nobody keeps yesterday's. Announce it flatly and move on; the complaining is part of the exercise.
Open with yesterday's list (4 min): The "one thing to solve tomorrow" sentences are on the board. Each team reads theirs aloud and says whether it's still the problem. Some will have found a bigger one.
Seam work (26 min):
The dry stress test (12 min) - run this as an event:
Some boats will fail this. Say the useful thing out loud when they do: "Better today than Friday.say this exactly That's what a test is for."
Close (8 min):
Midweek is when the build zone gets away from you. Hold it. A team that can't leave their patch clean at 3:00 has a job-allocation problem, not a tidiness problem - ask them who the Quartermaster is.
Best callouts today come from the dry test: whoever took a failure well, and whoever undid good work because it wasn't good enough. Name perseverance and humility precisely rather than saying "good job."
Today's team, in front of everyone, three questions. This is the debrief that used to sit in the morning launch - it works better here, because now the team has actually been up and the studio has watched them go.
Question two is the one that matters. If they say "nothing was hard," push once: "Nothing? You sat with a five-year-old for half an hour and every minute was easy?" The honest answer is usually near "I didn't know what to say" or "I wanted to just read it for them."
Five minutes is deliberately short - it forces answers rather than stories. Whatever surfaces here becomes tomorrow morning's briefing.
Send-off by name.
Talking points for this week's email. Drop these into an AI assistant along with two or three live notes from your actual week - a name, a moment, something that surprised you - and it'll give you a draft in your own voice. The specifics are what make it land; the structure below is just the scaffolding.
The draft underneath is an example of the shape and the tone, not a template to send as-is. A parent who gets the same email as every other parent can tell.
Subject: Testing things before they matter
Hi families,
Today was engineering day. We found out that cardboard doesn't fail in the middle, it fails at the joins - so teams spent the afternoon reinforcing every seam, and several had to take apart work they'd been proud of on Tuesday. That was the harder lesson and the more useful one.
Then every boat took a dry test: the team's rider sat in it on the floor while everyone watched, and shifted their weight. Some boats did not survive. The line I kept repeating was "better today than Friday," and by the end they were saying it to each other.
At Town Hall the studio took on a genuinely hard question - not "how has being a role model gone" but "where have we not been role models this week?" They answered it honestly, mostly about how they've been treating each other in their build teams. I was impressed.
Friday reminders: forms, swimsuit worn under clothes, towel, complete change of clothes, and shoes that can get wet.
- [your name]