Why Your Script Feels Too Predictable

A director I worked with early in my career had a specific way of describing scripts she didn't want to make. She'd say, "I kept being right." She meant that every choice the script made was the obvious one — the beat she expected, the turn that the genre promised, the decision that every other film in this territory had made before. Nothing surprised her. And because nothing surprised her, nothing delighted her.

Predictability is a quiet problem in screenwriting because it doesn't announce itself the way weak dialogue or structural issues do. The script isn't broken. Things happen. Characters make choices. The story reaches its conclusion. But the audience was always one step ahead, and being consistently right about what would happen is the opposite of being engaged.

The fix is not random twists. A surprise that comes from nowhere — that violates the internal logic of the story, that betrays character or setup — is as unsatisfying as no surprise at all. The goal is the surprise that feels inevitable in hindsight: unexpected in the moment, obvious once it lands. Getting there requires understanding exactly why predictability happens in the first place.

A predictable script doesn't fail on one page — it fails in the cumulative pattern of choices made across every page.

Why scripts become predictable in the first place

Predictability is what happens when a writer defaults to the expected choice at every decision point.

The mentor dies. The rivals become lovers. The hero hesitates and then does the right thing. The betrayer has a change of heart. The competent antagonist reveals their weakness at the worst moment. None of these are wrong — many of them are among the most powerful beats in storytelling, precisely because they resonate with deep patterns of human experience. The problem is when every beat is the default, and the audience can feel the tumblers clicking into place like a lock they already know the combination to.

I diagnosed this in my own writing when I started noticing that my "instinct" for what should happen next in a story was really just genre memory. I knew what happened in films like mine. When I didn't consciously work against that knowledge, I reproduced it. My scripts weren't lazy — they were heavily influenced by everything I'd absorbed as a viewer, and I was unconsciously making the same choices all those other stories had made.

The way out isn't to be contrarian. It's to be deliberate. At every major story decision, ask: what would the expected version of this be? Then ask whether you have a reason — character-based, thematic, emotional — to do something else instead.

The second and third option exercise

This is the most useful practical habit I've developed for fighting predictability. At every significant decision point — every turning point, every key character choice, every major beat — I brainstorm at least three versions of how it could go.

The first version is usually the obvious one. The mentor dies heroically. The protagonist makes the morally clear choice. The plan works on the second attempt. Write it down. You might still use it. But don't let it be the only option you considered.

The second version introduces a complication to the obvious path. The mentor survives but in a way that fundamentally changes the relationship. The protagonist makes the morally clear choice but at a cost the obvious version didn't require. The plan works but reveals something about the antagonist that wasn't visible before.

The third version is often the most interesting one. What if the mentor lives and the protagonist has to watch them diminished, which is harder than mourning them? What if the protagonist can't make the morally clear choice? What if the plan works and that's somehow worse than if it had failed?

The second option is almost always more interesting than the first. The third is often where the real story lives.

Most of the time I end up choosing something between the first and third options — a version that has the emotional resonance of the expected beat but complicates it in a specific way. The important thing is that I considered alternatives. The moment I'm choosing from options rather than defaulting to one, the script gets more interesting.

Why surprises need to be set up before they land

The most important thing about a narrative surprise is that it has to be earned. A twist that comes from nowhere — that required the story to withhold information unfairly, or to have a character act in ways incompatible with who they've been — feels like a cheat. The audience doesn't feel delighted; they feel tricked. And there's an important difference.

A satisfying twist makes the audience want to rewatch the film to catch the clues they missed. A cheap twist makes them feel angry that they weren't given fair information.

The clues have to be there. The setup has to be planted, usually multiple times, in ways the audience registered but didn't fully process. The surprise should feel, in retrospect, like the only possible thing that could have happened — even though in the moment it was completely unexpected.

I worked on a thriller where the big reveal was that the protagonist had been unconsciously self-sabotaging throughout the story. The reveal itself was well-conceived. But when I sent the draft out, nobody said "I should have seen that coming." They said "That came out of nowhere." Which meant I hadn't planted the setup. The rewrite seeded the self-sabotage throughout Act Two — small moments, easy to rationalize as stress or bad luck, that in retrospect were clearly deliberate. The same reveal, properly planted, transformed from a cheap twist into something that sent readers back to the beginning of the script.

Setup is what converts a shock into a satisfaction.

Subverting expectation without violating logic

There's a failure mode at the other end of the spectrum from predictability: the script that's surprising in ways that feel arbitrary. Characters do unexpected things, plot turns go in strange directions, nothing unfolds the way genre conventions suggest — but the audience doesn't feel engaged. They feel lost, or cheated, or both.

This happens when subversion is the goal rather than the result. When the writer is trying to be unexpected rather than trying to be truthful, the surprises feel like surprises for their own sake. The audience can feel when a story is zigging because it doesn't want to zag, rather than because the story's internal logic led somewhere genuine.

The best surprises break the audience's expectations while staying rigorously true to character. The antagonist does something we didn't predict — but in retrospect it's exactly what this person would do. The protagonist makes a choice that goes against genre convention — but it's the only honest choice for someone with their psychology and history.

The constraint is character. When a surprise is grounded in who a character genuinely is — when it emerges from their psychology, their history, their established patterns of behavior under pressure — it satisfies even as it surprises. When it's grounded only in the writer's desire to be unpredictable, it doesn't.

How to weaponize genre expectations

Here's something counterintuitive: the best way to use genre expectations is to fulfill them in unexpected ways.

Genre conventions are promises to the audience. Romances should end with connection. Thrillers should resolve the central threat. Comedies should end in some form of release. These aren't boxes to avoid — they're structures your audience has already agreed to. The question is what happens inside those structures.

Filling a genre promise in an unexpected way is different from breaking it. The romance ends in connection — but not between the two obvious characters, or not in the way either character planned, or through a sacrifice neither expected to make. The thriller resolves the threat — but the resolution reveals something about the protagonist that the genre formula usually leaves unexamined.

The audience gets what they came for — the genre experience they signed up for — and they also get something they didn't see coming. That combination is what makes films feel both satisfying and fresh at once.

The audience is always trying to predict what comes next. Your job is to stay one honest step ahead of them.

Reading your own work as a first-time viewer

The hardest part of writing against predictability is that you know your story too well to experience it fresh. You can't be surprised by a choice you made. The script that feels fresh to you may be deeply predictable to a reader who doesn't know what's coming.

This is why external readers are essential — but even before you show the work to anyone else, there's a useful exercise. Read your script looking specifically for moments where you, as the writer, felt certain what would happen next. Those moments of certainty are your predictability problem areas.

If you knew exactly what would happen in a given scene before you wrote it — if you weren't discovering anything in the writing, just executing the expected version — that scene is a candidate for the second and third option exercise. It doesn't mean the expected version is wrong. It means you owe yourself the discipline to consider whether it's the best version.

Predictability and randomness are both failures of the same thing: the audience's relationship to what's possible in your story. The audience is trying to stay one step ahead of you the whole time. Your job is to stay one honest step ahead of them — not by cheating, not by randomness, but by choosing at every decision point the option that's truest to the story rather than the option that's most familiar. Do that, and they stop being right. They start leaning forward again.

← All articles