Every stuck script has a diagnosis. The problem is that most content teams treat "writer's block" as one thing when it's actually four distinct failures, each with a different fix.
Source: This framework comes from Kallaway's "How to Script Viral Videos 10x Faster", which breaks down the scripting bottleneck into four specific blockers and provides a systematic approach to eliminating each one.
The blank page problem shows up the same way regardless of team size. Someone sits down to write a script, stares at the doc, rearranges a few bullet points, checks Slack, comes back, writes a sentence, deletes it. An hour passes. The script is still empty or barely started, and the production calendar slips another day.
The instinct is to push through it. Try harder, think harder, just start writing. But pushing through a problem you haven't diagnosed is like debugging code by randomly changing lines. You might stumble into a fix, but you'll waste enormous time, and you won't be able to repeat whatever worked.
The Blank Page Is a Symptom, Not the Disease
The blank page is the fever, not the underlying condition. Four distinct infections cause it, and each one requires a different treatment.
As Kallaway puts it: "Most people really struggle with script writing, hooks and storytelling. The reason is you don't have a system for converting raw ideas into winning scripts." The key word there is "system." When you don't have an answer to any of the four core scripting questions, that's what holds you up and causes the overthinking. The overthinking is a downstream effect of not having a structured response to one specific blocker.
The four questions every scripter faces, whether consciously or not:
- What is actually interesting about this topic that I should include?
- What is the best way to hook the viewer?
- If I hook them, how do I tell the rest of the story to hold their attention?
- If I hold their attention, how do I make sure they engage after watching?
When you have clear answers to all four, scripts flow. When any one of them is unresolved, the page stays blank. Each question has a different fix, and applying the wrong fix to the wrong blocker just creates a different kind of stuck.
Blocker 1: The Interestingness Problem (The Law of Interesting)
This is the most common starting blocker, and it's the one that feels the most like general creative paralysis. You have a topic. You know roughly what you want to cover. But you can't articulate why anyone should care about it, and until you can, every angle you try feels flat.
Kallaway's first step before writing any script is to "jot down a few bullets about what makes this story interesting to you." That sounds simple, but it forces a critical question: is there a formula for knowing when something is going to be interesting to others?
It turns out there is. Kallaway calls it the Law of Interesting: "Interestingness comes from shock value. Shock value is the distance between what someone already knows about a topic and what you tell them in the video. The greater the distance, the more interesting."
Think of it as an information gap metric. If your audience already knows 80% of what you're about to tell them, the interestingness score is low. If they know 20%, the score is high. Your job during the interestingness phase is to identify the facts, angles, or insights in your topic that create the largest gap between audience expectation and reality.
This reframes the problem entirely. You're not trying to "be creative." You're auditing your raw material for surprise density. A topic about email marketing isn't inherently boring or interesting. The interestingness depends entirely on which specific claims you make about email marketing and how far those claims sit from what your audience currently believes.
For content teams, the interestingness audit should happen before anyone opens a script doc. The writer or researcher identifies the 3 to 5 most surprising facts, angles, or counter-intuitive claims in the topic. If they can't find at least 2 that create meaningful distance from audience expectations, the topic probably needs a different angle, or it needs to be killed before it wastes production time.
Blocker 2: The Hook Problem (The 3-Step Formula)
You know your topic is interesting. You've identified the surprising elements. But you're stuck on how to open the video. The first 5 seconds feel impossible because they carry so much weight, and the pressure to nail them creates its own paralysis.
The fix is structural. Kallaway teaches a 3-step hook formula that removes the need to invent a brilliant opening from scratch every time:
Context Lean-In: Give the viewer just enough context to understand what the video is about and why it's relevant to them. This isn't a long setup. One sentence or phrase that signals "this is for you" to the right audience.
Scroll Stop: Introduce the element of surprise, contrast, or tension that makes someone pause their scroll. This is where your interestingness work from Blocker 1 pays off, because the scroll stop is usually the most surprising thing you found during the interestingness audit.
Haymaker: Deliver the punch. This is the specific, concrete claim or revelation that commits the viewer to watching. The promise of the video compressed into one sentence, specific enough that the viewer can immediately evaluate whether they want to hear more.
The formula works because it turns hook-writing from a creative problem into an assembly problem. You already have the pieces from your interestingness work. The 3-step structure tells you which piece goes where and in what order.
When a writer is stuck specifically on the hook and not on the topic's interestingness, the 3-step formula is the fix. Applying the interestingness audit to a hook problem wastes time, and trying to "just write a better hook" without structure leads to the same paralysis that caused the block in the first place.
Blocker 3: The Storytelling Problem (But/Therefore)
The hook landed. The viewer is in. Now you need to hold them for the next 3, 7, or 12 minutes. This is the blocker that shows up in retention graphs as the mid-video cliff, and it's probably the most expensive blocker for teams producing at volume because the hook work and the interestingness work are already done by the time this one hits. Wasted effort compounds.
The fix is the But/Therefore framework, drawn from Trey Parker and Matt Stone's rule for South Park scripts. Every beat in a story should connect to the next with "but" or "therefore," never with "and then."
"And then" is the enemy of storytelling because it creates a flat sequence: this happened, and then this happened, and then this happened. There's no cause and effect, no tension, no reason for the viewer to anticipate what comes next. The viewer can leave at any point in an "and then" sequence without feeling like they're missing something, because nothing was building.
"But" introduces a complication. "Therefore" introduces a consequence. Together they create a chain where each beat makes the next beat feel necessary.
A script about content strategy written in "and then" mode: "We tried posting daily, and then we hired an editor, and then we started doing Reels, and then our views went up." A script written in "but/therefore" mode: "We tried posting daily, but the quality dropped so badly that engagement fell 40% in two weeks. Therefore we hired an editor to maintain quality at the same volume. But the editor couldn't match our brand voice, so the first month of edited content felt generic. Therefore we built a brand guide with 12 specific examples of our voice."
Same information. Completely different experience. The but/therefore version creates forward pull because every beat raises a question that the next beat answers, while simultaneously raising a new question.
For script review, but/therefore works as a literal editing technique. Take the draft, find every transition between ideas, and check whether the connection is "and then" or "but/therefore." Any "and then" transitions are retention risks. Flag them, send the script back, and ask the writer to rebuild the connection with conflict or consequence.
Blocker 4: The Engagement Problem (Driving Action After Watching)
This is the blocker that shows up after the video is already performing well in terms of retention. People are watching, but they're not liking, commenting, sharing, or clicking through. The content holds attention without converting that attention into action.
The fix operates on two levels: structured CTAs and emotional payoffs.
A structured CTA isn't "don't forget to like and subscribe." That's a generic ask that viewers have been trained to ignore. A structured CTA connects the action to the content the viewer just consumed. "If this framework changed how you think about scripting, save this video so you can reference it next time you sit down to write." The CTA has a reason attached to it, and the reason is specific to the value the viewer just received.
The emotional payoff is subtler but arguably more powerful. When a video ends with a moment that makes the viewer feel something, the impulse to engage is organic rather than prompted. This could be a callback to the opening that reframes it in light of everything they've just learned, a personal admission that adds vulnerability, or a final specific detail that crystallizes the entire video's value into one concrete image.
Both of these can be scripted. Neither requires spontaneous inspiration. The structured CTA should be written as part of the script outline, not improvised on camera. The emotional payoff should be identified during the interestingness audit: what's the single most resonant element in this topic, and how do we save it for the final 15 seconds?
The Diagnostic Framework Turns Mystery Into Process
The power of the 4-blocker framework is diagnostic. When a script is stuck, you don't need to figure out why from scratch. You ask four questions:
- Can we articulate what makes this topic surprising? (Interestingness)
- Do we have a clear hook structure? (Hook)
- Does the script body use but/therefore connections? (Storytelling)
- Is there a structured CTA and emotional payoff? (Engagement)
The first "no" is your bottleneck. Fix that specific blocker with that specific tool, and the script usually starts moving again. This is a systems problem, not a motivation problem. You don't need to inspire your writers to push through the blank page. You need to give them a diagnostic that identifies which of four known problems they're facing and a protocol for each one.
Think of it like a CI/CD pipeline for scripts. Each blocker is a gate. The script can't move to the next stage until it passes the current gate. Interestingness passes before hook writing begins. Hook passes before body scripting starts. Body scripting passes the but/therefore check before the engagement layer gets added. Each gate has clear pass/fail criteria that a reviewer can evaluate in minutes.
The alternative, which is what most teams do, is to treat scripting as a single monolithic creative act. The writer is expected to simultaneously figure out what's interesting, craft the hook, structure the story, and engineer the engagement layer, all at once, in one draft. That's not a content production workflow. That's hoping your writer has a good day.
Distributing Blockers Across Roles Turns Writers Into Specialists
Different blockers can, and probably should, be assigned to different roles. The interestingness audit can be done by a researcher or strategist who understands the audience's existing knowledge level. The hook can be written by a specialist who studies hooks full-time and maintains a swipe file of proven structures. The but/therefore check can be done by a script editor during review. The engagement layer can be added by the creative director or content lead who has the clearest view of what's driving comments and shares across the channel.
When one person owns all four blockers, the bottleneck is that person's worst skill on any given day. When you distribute the blockers across roles, you've turned a single-point-of-failure creative process into a pipeline where each stage has a specialist and a clear handoff.
For a lean team of 2 to 3 people, the split might look like this: the content strategist handles the interestingness audit and hook structure (Blockers 1 and 2), the writer handles the body script using the but/therefore framework (Blocker 3), and the strategist adds the engagement layer during script review (Blocker 4). Each handoff has a specific deliverable and a specific check.
For a larger team producing 10 or more videos per month, each blocker can genuinely be a separate role or at least a separate step in the production workflow with its own owner and its own quality gate.
We've been testing variations of this at Clipflow, and the biggest shift isn't speed, although scripts do move faster when the blockers are pre-diagnosed. The biggest shift is that stuck scripts stop being mysterious. When a script is stuck, the writer doesn't say "I'm blocked." They say "I'm stuck on Blocker 2, I can't find the scroll stop," and the team can help solve a specific problem instead of offering vague encouragement.
The blank page was never the problem. It was always one of four problems wearing the same disguise. Name the blocker, apply the fix, and the page fills itself.
