// week 04 · the road of trials · sustained focus

The long build.

The cardboard boat gave them a result in four days. The Lip Dub gives them nothing for three weeks - and that's the point of this week. Sustained focus, delayed payoff, and work that only makes sense once it's finished. To keep the studio from burning out on one long project, every day pairs Lip Dub progress with something that finishes in a single afternoon and ends up on the Exhibition wall.

// the lip dub timeline · non-negotiable

Week 4 builds it. Week 5 films it. Week 6 is the margin.

Week 4Preparation, in full, as the sole Quest focus. Song chosen, song mapped, route walked, moments assigned, crew roles claimed, and as many rehearsal reps as the week will hold. Nothing is filmed for real this week.
Week 5The recording week. Blocking Tuesday, dress rehearsal Wednesday, the shoot Thursday, choose the take Friday.
TargetFully recorded by Thursday of Week 5.
Week 6Slack, deliberately. A reshoot window if the studio wants one; otherwise review and refine.

The buffer is the point. The film must not be a last-minute thing done the day before Exhibition. Shooting on Thursday of Week 5 leaves a full week of margin for a sick camera operator, a corrupted file, a take nobody likes, or a locked door on the route. Anything that erodes that margin is a regression, not a scheduling tweak.

Say the shape of it to the studio on Monday so it's public from day one: "This week we build all of it. Next week we film it - Thursday. We film early on purpose, because if something goes wrong we want a week to fix it, not a night."

01

The week at a glance

// guiding question

How do we get ready for the one take that counts?

// what gets built this week

Artifacts

  • A chosen song, voted at Town Hall #4 and final once voted
  • The five-step board - the whole project broken into five things, posted and left up
  • A lyric map: which section of the song belongs to which part of the studio, with timings written down
  • A walked camera route, drawn as a storyboard the studio can walk along
  • Every learner assigned at least one moment, on a master list owned by a named learner
  • Crew roles claimed - camera, sound, floor manager, continuity
  • The Lip Dub banner, built as a working prop rather than a decoration
  • At least two full walks of the route with the song playing, by Friday

What the guide does

  • States the timeline out loud on Monday and keeps saying it: we build this week, film next Thursday, and Week 6 is the spare week
  • Gives the song criteria before nominations open, not after
  • Screens every nominated song overnight for lyrics and licensing - anything unusable comes off the ballot quietly, before the vote
  • Holds the vote as final. Reopening it destroys the credibility of every vote after it
  • Protects rehearsal time from good ideas. The recovered afternoons go into walking the route and drilling handoffs, not into new content
  • Writes the timings down. "We'll remember" is how a Lip Dub falls apart in Week 6
  • Watches for the learners who ask for nothing - they're the ones who end up invisible in the final film
02

The five days

// day 01 · monday

Kickoff + Nominations

The timeline stated out loud, references watched twice, the five-step board goes up, and nominations open - with the song criteria given first.

// day 02 · tuesday

The Route, Before the Song

Scout and walk the physical route before the song exists. Song advocacy: every nominator gets sixty seconds to make a case.

// day 03 · wednesday

The Song + the Banner

Voted at Town Hall and final once voted. First full listen, first sections marked, and the banner built as a working prop.

// day 04 · thursday

Mapping + First Full Walk

The camera can't teleport. Lyrics mapped, storyboard drawn, and the route walked end to end with the song playing.

// day 05 · friday

Everyone Gets a Moment

Assignments made and crew roles claimed, then the second full walk with the song. The week ends with the shape of it visible.

03

Backup activities

There is no separate Challenge this week, and no side builds inside Quest either - every Quest block this week is fifty minutes of Lip Dub work. The studio needs the reps more than it needs variety, and four extra afternoons of walking the route is what makes Thursday of Week 5 a comfortable shoot date rather than a hopeful one.

Two of the original one-afternoon builds stayed, because they turned out to be Lip Dub production work rather than side projects: the Banner is a prop that has to be legible on camera and survive a corridor, and the Storyboard is the route itself. Both are still in the week, on Wednesday and Thursday.

The other two are below, in full and unchanged. They are backup, not cut. Reach for them when the studio needs a change of gear from the same song, when a block finishes early, or when a wet Tuesday needs rescuing - and be honest that both of them earn their place at Exhibition if you run them.

// backup · ~25 min, finishes same day

The Portrait Wall

Every learner photographed doing their special ability - the one they wrote on their Week 2 Trading Card. Not posed headshots: the kid who explains fractions is explaining fractions, the kid who finds lost things is under a table.

Exhibition: printed large, hung as a grid with the trading cards beside them. Reuses: Trading Cards.

// backup · a full block

The Chain Reaction

A studio-wide Rube Goldberg machine where each team owns one section and every section must hand off to the next team's. Pure engineering, and the handoff points are where all the negotiation happens - the same problem as the boat seams, with different materials.

Exhibition: filmed on a phone; the successful run plays on a loop. Reuses: Week 3 team skills.

// in the week · wednesday quest

The Banner

A large studio banner built as a physical prop for the Lip Dub - which means it has to be legible on camera, carried by several people at once, and survive being run down a corridor.

Exhibition: hangs behind the screen at the premiere. Reuses: Standard of Excellence language.

// in the week · thursday & friday quest

The Storyboard & the Crew

The Lip Dub route drawn as a physical storyboard the studio can walk along, and the behind-the-camera roles claimed - camera, sound, continuity, floor manager. Not everyone wants to be on film, and this is where that becomes an asset rather than a problem.

Exhibition: storyboard displayed beside the screen. Reuses: Roles board.

03b

Backup activities, in full

Both of these are written out to be run as-is. Nothing has been cut - they moved out of Quest, not out of the guide.

// backup 01 · ~25 min · finishes same day

The Portrait Wall

What it is: a photographic portrait of every learner, shot properly, printed large, and hung as a single grid at Exhibition next to the Trading Cards they made in Week 2.

  1. Set up one corner as a studio - plain wall, a lamp, a chair. Ten minutes of setup by whoever wants the job.
  2. Two learners run the camera. Not the guide. They direct, they frame, they take three shots each.
  3. The rule for the sitter: you don't have to smile. You have to look at the camera. That's it.
  4. Everyone gets photographed, no exceptions - same rule as the Trading Cards.

Why it's a good one to reach for: it's fast, it finishes inside the block, and it gets the camera into learners' hands - which matters when they're operating it for the real take on Thursday of Week 5.

Carry forward: portraits get printed and hung alongside the Week 2 Trading Cards. The pairing is the point - a face and, next to it, what that person said they were good at and what they needed.

// backup 02 · a full block

The Chain Reaction

A whole-studio machine where every team's section must hand off to the next. It is a Lip Dub in miniature - individually easy, collectively brutal, and it fails at the joins.

// reality check · read before you plan this

Twenty-five minutes will not produce a working machine

Be clear-eyed about this. Teams of learners this age building a chain-reaction section from scratch, from shared materials, in twenty-five minutes, will not produce something that reliably triggers the next section. Expect that most of the fifteen minutes of "runs" will be learners tipping dominoes over by hand and calling it a handoff. That is what this activity actually looks like.

That's fine if the goal is the lesson - it fails at the joins - and the debrief carries the day rather than the machine. It is not fine if you've told the studio you're building a working machine, because then twenty-five minutes of chaos reads as failure.

Two ways to make it land:

  • Name the constraint at the brief. "You have twenty-five minutes. That's nowhere near enough. Your job isn't a perfect machine - it's a section that reliably does one thing and passes to your neighbor." One trigger, one action, one handoff. Nothing more.
  • Or cut the scope and buy the time. Give every team the same three materials and a pre-marked start and end point, and drop the build to fifteen minutes with thirty for runs and repairs. Fewer variables, more reps at the join - which is the only part that teaches anything.

Either way, say out loud before they start that hand-triggering is allowed. Otherwise the run degenerates into an argument about cheating instead of a conversation about joins.

The brief (5 min):

Build (25 min):

  1. First five minutes: teams talk to their neighbors, not to each other. Enforce this. The joins get negotiated before the middles get built, or the whole thing has to be rebuilt at the end.
  2. Instruction swap at the halfway point - each team hands their written instructions to their neighbor and watches them try to follow it. Ten seconds of that teaches more about clear writing than a term of marking.
  3. Teams build. Guide circulates and only ever asks about joins.

The runs (15 min) - and film every one:

  1. Full run attempt. It will fail. Note where - the join, almost always, and rarely the middle.
  2. Hand-triggering is allowed and should be announced as allowed. What's being tested is whether the handoff was negotiated, not whether the physics worked.
  3. Two minutes of repair, by the two teams who own that join - not by the guide, and not by the whole studio shouting.
  4. Run again. Repeat until it goes end to end or the block runs out.
  5. If it never completes, that's a completely acceptable outcome. Say so in advance so nobody's afternoon rests on it.

Close (5 min): one question - "Which join was hardest, and what did the two teams have to do to fix it?" Then connect it forward: "That's what we're doing with the Lip Dub, except the marble is a song and the join is a person."

Carry forward: the successful run - or the best failed one - goes in the Exhibition reel. Keep the written instructions too; they're better writing evidence than most things that end up in a folder.

// the rule that makes this work

Every day ends with a run of whatever exists

The failure mode of a project like this isn't difficulty, it's fog - days in a row of work that doesn't look like anything yet. The answer isn't a side build; it's that every Quest block ends by running whatever exists so far, however partial. Thirty seconds of the opening with four people in the right place is visible progress. A studio that walks the route on Wednesday, Thursday and Friday can feel the thing getting better, which is the whole problem solved.

On the Exhibition wall: the room fills with the v1-beside-v2 pairs (Personal Working Guides, Trading Cards, both Mirrors, Standard of Excellence), the boat build sequence, the Spark journals and every learner's station. It does not depend on these two builds - but it's better with them, so run them if the week allows.

If the studio is flagging on the same song three days running, that's the signal to reach for a backup - not to abandon the rehearsal, but to spend one block differently and come back. Just don't spend two.

04

Key launches this week

non-negotiable

The one-shot problem

We name the menu: take a breath, use the PWG, use Work It Out, ask a guide. We rehearse the menu before we need it.

Where: Day 1 Morning Launch

non-negotiable

The handoff - it fails at the joins

Some discomfort is growth. Some discomfort is harm. The studio learns to tell the difference and respond accordingly.

Where: Day 2 Morning Launch

build over time

Standard of Excellence v2 - moved to Week 5

The posters get refined based on real lived experience. What did we learn that we didn't know in Week 1?

Where: Day 3 Town Hall + Day 5

05

Common pitfalls Week 4

// from the last guide

What to watch for

Rescuing too early. The point of a three-week build is the three weeks. If a guide steps in at the first sign of struggle, the muscle doesn't build.

Making it punitive. The challenge should be intrinsically hard, not externally imposed as punishment. Frame it as a gift, not a hurdle.

Letting real conflict get personal. When the inevitable conflict emerges, name the dynamic, not the person. "We're seeing X pattern" not "learner Y is doing Z."

← previousWeek 3 · The Shared Road