Skip to main content

Week 12: After Five Minutes

What happens after a pilot ships — the series bible, the release calendar, reading a retention curve, and which parts of this semester's process actually scale into a season.

24 May 2027

The pilot is finished and delivered; this lecture is about the five minutes after someone presses play, and about everything past that first episode — a second one, a season, a feature cut. None of that is a bigger version of the same problem. Some of it scales cleanly from what the semester has already built, and some of it does not scale at all.

Reading the curve

A retention curve plots what share of viewers are still watching at each point in an episode, and its shape matters more than its overall average: a steady curve with one sharp drop tells a different story than a slow, even decline, even where both end at the same final number. The sharp drop is where something specific went wrong; the slow decline is closer to the whole episode being paced too loosely throughout.

TimeShare still watching
The sharp drop is where something specific went wrong. Illustrative curve, not data.

Every drop-off point maps back to a specific decision earlier in the process — a hook that didn’t land in its first three seconds, a cut that read as confusing rather than deliberate, a stretch where the beat sheet’s density flattened out. The curve doesn’t explain why a moment failed; it only points at where to look.

The bible carries forward what the pilot built

A series bible is the document that lets a second episode start from where the first one left off rather than from zero: the model sheets and master plates that lock identity, the beat-sheet conventions that worked, the hook types that held an audience and the ones that didn’t. Writing the bible once, after the pilot, is what makes a second episode cheaper to produce than the first one — without it, every new episode re-solves continuity and pacing problems the pilot already solved.

The release calendar

A season is not just a pile of finished episodes; it’s a schedule someone commits to and a viewer can rely on. A release calendar states when each episode goes out and holds that date the same way an assessment’s due date gets held — a season that ships on an unpredictable schedule loses the audience a retention curve is trying to measure in the first place, regardless of how good any single episode is.

What scales, and what doesn’t

Generation, continuity discipline, and the quality gate scale close to linearly: more episodes need more passes through the same queue, with the same roles, checked against the same reference material. What doesn’t scale the same way is judgment — deciding which hook actually fits a beat, deciding whether a drop on the curve is a pacing problem or a one-off, deciding what belongs in the bible and what was a one-episode accident. Adding more people to a queue multiplies throughput; it does not multiply the judgment behind any one decision, which stays a single person’s job no matter how many episodes are in production.

Before class

Bring the finished pilot and one specific guess, based on its beat sheet, at where its own retention curve would drop.

This week’s exercise

Write a one-page account of the semester’s process: what you’d carry into the bible for a second episode, one change the retention-curve reading would justify, and what you now believe does or doesn’t scale past a single episode. Bring the finished pilot and this account to Wednesday’s Dailies.

Reading

Teaching team