All posts
·8 min read·Yom Akakpo

One episode did three times the rest. Here's what I missed.

Twenty-one episodes on the same channel, same format, same synthetic voice. One of them broke the algorithm. A field report on three wrong theories — and the fourth one that landed at 2am, on a re-read.

case-studyai-videoshort-formyoutube-shorts

Monday, close to midnight. I close one last tab, and by reflex I reopen YouTube Studio. Cocorico Histoire — twenty-one episodes published over four months. A French-language AI channel: sixty-second micro-documentaries on French history, its political machinery, its grand symbolic mess. Same format every time. Same synthetic voice. Same publishing slot.

And there it is — a row that has no business being there.

Episode 01 — Why the rooster is the symbol of France — sits at three times the likes and views of the others. Not thirty percent more. Not even eighty. Three times. I refresh the page twice. The number doesn't move. It stays planted above the channel median like a typographical error someone forgot to fix.

I want to understand. Because if I figure out what tipped this one over, I can replicate the mechanism across the seven other channels I run in parallel. And because at this point, with twenty median episodes already shipped, statistically I have a lot of mediocre ahead of me.

The table that kept me up for two weeks

| EP | Subject | Variance from median | |---|---|---| | 01 | Why the rooster is the symbol of France | +295% | | 02 | La Marseillaise wasn't written in Marseille | -8% | | 03 | July 14th isn't the storming of the Bastille | +12% | | 04 | The Eiffel Tower was nearly demolished | -22% | | 05 | The baguette isn't really French | +5% |

Same duration window (58 to 62 seconds). Same publish time. Same hashtag set. The only variables are the subject and the script structure. So the answer is in the subject or in the structure. Pick one.

Theory one — familiarity explains it

First instinct: episode 01 won because the rooster is the most recognizable symbol of the lot. Even someone who has never opened a French history book knows the rooster is the national bird. Higher click-through, the algorithm amplifies, the loop reinforces itself. Logical. Mechanical. Almost banal.

I push out episode 08, on the bleu-blanc-rouge flag. Even more universal — known by Americans who have no reason to care. If familiarity drives the mechanism, this one should take off.

Result: +5%. A ripple. Not a wave.

I bury the theory. The lever was real, but not sufficient.

Theory two — the hook, and only the hook

If it isn't the subject, maybe I just wrote the opening better that day. The hook for episode 01 reads: "The French rooster comes from an old Roman joke that backfired." Short, inversive, already the betrayal of a certainty.

I decide to rewrite episode 04, the Eiffel Tower, using the same mechanic. I move from a flat opener — "The fascinating history of the Eiffel Tower" — to something with tension: "They built the Eiffel Tower in order to demolish it twenty years later." Better. Significantly better. I publish a fresh cut, same slot, same hashtags.

Result: +3%. Better than before, granted, but light-years away from the multiplier I was chasing.

Bury theory two.

Theory three — the algorithm has moods

At this stage, I start drifting toward the lazy explanation: maybe it's just statistical noise. YouTube Shorts has brutal variance — a video that lands in front of the right cluster at the right moment can spike for reasons that don't replicate. The science behind recommendation algorithms is less a science than a meteorology, and a lucky strike is still a lucky strike.

I wait two weeks for the discovery window to reset. I re-upload a slightly remixed cut of episode 04. Same hashtags. Hook v2.

Still nothing.

At that point I'm out of theories. And that's precisely the moment when one starts re-reading the scripts, convinced the answer is in there somewhere, knowing only that one doesn't yet know how to read it.

The thing I wasn't seeing

I read episode 01 against episode 02, then against 04, then against 05. Not the numbers — the scripts. Out loud. Back to back, no pause.

The pattern surfaces, almost by exhaustion.

Episode 01 is the only one in the lot that betrays an installed certainty. The others are doing something else, and that something else is exactly why they don't climb.

Episode 02 (La Marseillaise written in Strasbourg) is an anecdote about something nobody was thinking about in the first place. It's a puzzle on an unknown — the viewer pauses politely, logs it, scrolls. Episode 04 (Eiffel Tower saved by military radio) is an elegant curiosity. Huh, interesting, but no mental boundary moves. Episode 05 (baguette invented in Vienna) touches identity — my bakery has been lying to me — and triggers a defensive posture rather than engagement.

Episode 01, the rooster, sits in another category entirely. The rooster is an object every French person has carried around since kindergarten. It exists with an implicit opinion attached — I know what it is, it's ours. The hook arrives and says: "The Latin for 'rooster' and 'inhabitant of Gaul' is the same word. Gallus. So for centuries, the Romans were literally calling us 'the chickens'."

The gap between "I know" and "oh, actually I don't" — that's what produced the 3×.

Not novelty. Not the hook in isolation. Not the algorithm. The betrayal of the familiar.

Three rules I pulled out of it

I rewrote the channel's editorial doc against this grid. Three rules, in order.

1. Open on the familiar, never on the unknown

A viewer scrolling Shorts has about a second and a half to decide. If your first frame is about an object, a name, a figure the viewer has no prior opinion on — a nineteenth-century politician, an obscure architectural detail — they swipe. The swipe is free; attention is not.

If your first frame is about an object the viewer thinks they already understand — the rooster, the AZERTY keyboard, the snooze button, the baguette — they stop. Because they want to confirm what they know. And that pause buys you four or five additional seconds, the time the twist needs to deploy.

Practical rule: the topic of an episode has to be expressible in the first second as an object or word your grandmother knows.

2. The first reversal has to land before the eight-second mark

The eight-second mark is the wall. Past it, the viewer has either committed to continue or already swiped. The "except..." construction has to land before that wall.

In episode 01, the inversion arrives at six seconds: "It's an old Roman joke. In Latin, 'rooster' and 'inhabitant of Gaul' are the same word." The viewer is confronted with the betrayal before they've had time to decide to leave.

If your script structure is setup → setup → setup → payoff at the twenty-fifth second, you'll lose seventy percent of the audience before the payoff. Prefer a cascade of reversals. Each segment betrays something the previous segment established. Not one final revelation — several small flips, stacked.

3. The viewer is a co-investigator, not a student

The voice that works is "I just learned something — listen". Not "let me explain X to you". The distinction looks thin; it is in fact structural.

In the first register, the narrator is at the viewer's level: they're discovering at the same pace, the viewer witnesses the narrator's realization as much as the revelation itself. In the second, the narrator is positioned above — they know, they transmit, the viewer receives. The asymmetry kills engagement.

Compare:

  • "The history of the rooster as a French symbol dates back to antiquity." — encyclopedic, flat, forgettable.
  • "I just learned something about the rooster and I haven't recovered." — conversational, partial, shareable.

The signal that confirmed I was on the right track sat in the comments under episode 01. Half of them were surprise markers — "WAIT WHAT 😭" — and the other half were additions: "I knew the rooster part, didn't know the Roman thing." Nobody wrote "thanks for the info". Nobody complimented the episode on its pedagogical clarity. That was engagement, not passive consumption.

What I did with the lesson

I forked a new channel out of this realization: WhyFactory.

Same synthetic voice, same sixty-second format, same render stack. But one editorial mandate, written as a single sentence: "why this everyday thing exists, and the twist you didn't see coming." The familiar first. The reversal within the first six seconds. Every time.

Eight episodes shipped, eighteen more queued in a prioritized backlog:

  • why the AZERTY keyboard exists,
  • why the inventor of Pringles was buried in a Pringles can,
  • why the elevator close-door button does nothing,
  • why our fingers wrinkle in water,
  • why a penguin named Nils Olav holds a colonel's rank in the Norwegian Royal Guard,
  • why bananas are radioactive,
  • why the barcode pattern was inspired by Morse code drawn in the sand.

Every opener follows the same protocol: "I just learned a wild thing about [familiar object]", then the first reversal in segment two. It's too early to say WhyFactory holds — I want two months of data before I'd call anything. But the mechanism that produced episode 01's 3×, that's the one I write against now, every script.

If you skip everything, keep this

You're running a channel. One episode spiked against all apparent logic. The temptation is to reach for the obvious explanation: the topic, the hook, the algorithm. All plausible. All probably wrong, or at best insufficient.

Re-read the outlier next to the median, out loud, with one question in mind: what is this one doing, structurally, that the others aren't? Not on the surface — not in duration, not in publish time. In the relationship the script holds with the person watching.

What I had to admit, in my case: people don't engage with content that teaches them something. They engage with content that betrays what they thought they already knew. It's the only metric I optimize against now.


Building your own AI video channel? The publishing layer of my stack — the part that ships your render to YouTube, TikTok, Instagram, Facebook, Threads and LinkedIn from a single MCP call — is exactly what Shortflow does. You can connect a channel in two minutes.