Why this lesson: in Lesson 18 you learned which numbers matter. Now the harder skill — turning those numbers into one change for next time. Most creators drown here: they see five weak metrics and try to fix all of them at once. You're going to fix exactly one, and you'll always know which.
First, recall
From the cheat sheet: signals are read in order — Stop, then Stay, then React. A weak Stop means the feed never even tests your Stay. That ordering is the whole trick to this lesson: fix the earliest weak signal first.
The diagnostic loop
One post, four steps, repeat forever:
1Read
2Find earliest weak signal
3One fix
4Repeat
Read the post's numbers. Walk them in order — Stop, then Stay, then React — and stop at the first one that's weak. That's your bottleneck. Make one change aimed at it on the next post, then read again. Because the signals gate each other, fixing a later one while an earlier one is broken is wasted effort — the feed never gets far enough to reward it [YouTube for Creators].
The key idea
Don't fix your worst number — fix your earliest weak number. A brilliant CTA can't save a post nobody stayed for, and great value can't save a post nobody stopped on. Repair the funnel front-to-back.
Worked example · great stop, weak stay
Your "Use it" Reel on an AI prompt trick posts these numbers:
Stop — strong. 58% scroll-stopped. The hook is clearly working.
Stay — weak. Sharp 2-second drop-off; average watch time collapses right after the hook.
React — can't tell. Barely anyone stayed long enough to save or share, so this number is meaningless right now.
The earliest weak signal is Stay. So the fix is not the hook — the hook is fine. The fix is the value: you're over-promising in frame one and under-delivering in second three. Next post, make the first thing after the hook actually pay off the promise. One change, aimed at the earliest leak.
The trap here is "58% stopped, let me make the hook even punchier." That optimizes a signal that isn't broken and ignores the one that is.
Get a human read too
Analytics tell you where people dropped, not always why. When the numbers can't explain the leak, borrow a pair of eyes. Post an early piece to r/NewTubers — 695k small creators who'll tell you bluntly whether your hook confused them or your payoff fell flat [r/NewTubers]. It's the fastest feedback loop when you don't yet have an audience of your own.
Quick self-check
No clues in the formatting — pick from memory, then click.
1. Your post shows a strong Stop but a weak Stay. What do you fix next time?
Stop is fine — the earliest weak signal is Stay. People stopped, then bailed, which means the value under-delivered on the hook. Fix that, not the parts that are working.
2. Why fix the earliest weak signal rather than the worst-looking number?
Signals are read in order. If Stop is broken the feed never tests Stay or React — so a weak later number is often just a symptom of the earlier leak. Repair front-to-back.
3. How many changes should you make per post when running the loop?
One change. Change five things and you can't tell which one moved the number. One fix per cycle keeps the experiment readable — and the earliest weak signal tells you which one.
Your turn · do this now
Take your last post's numbers, walk them Stop → Stay → React, and write down the first weak one and the single fix you'll try next. Paste both to me — I'll tell you if you picked the right bottleneck or skipped an earlier leak.
Primary source · study this
The YouTube for Creators — Resources Hub is the ground truth for reading retention curves and audience-retention reports. Study how they teach you to spot the exact second viewers leave — that timestamp is your fix.
💬 Your teacher is here. Not sure which signal is your real bottleneck, or which single fix to try? Paste your numbers and we'll diagnose it together — one leak, one change.