A beta reader tells you the middle third of your book is slow. You go back and count: there's a heist, a betrayal, a car chase, and a breakup. Objectively, a lot happens. So why does it read like nothing does?
Because "slow" is almost never about event density. It's about motivation. Readers aren't bored by a lack of things happening — they're bored by not knowing why the character bothers to do any of it. Take away a clear want and even a car chase turns into choreography.
Here's a fast way to check your own work. For any scene, try to finish this sentence: she does X because she wants Y, and if she doesn't get it, Z happens. If you can fill in all three blanks without stalling, the scene has an engine. If you're stuck after "because she wants," you've found your slow part — and it's not the pacing, it's the plumbing underneath it.
Want vs. Need: The Two Engines Running Under Every Scene
Every well-built character runs on two different fuels, and they usually point in opposite directions.
Want is the conscious goal — the thing the character would tell you if you asked. It's plot-shaped: get the promotion, win back the ex, find the killer, steal the artifact. It's what drives scene-level decisions and gives the plot its forward motion.
Need is the thing the character doesn't know they're missing, or knows and refuses to deal with. It's internal, usually uncomfortable, and often the opposite of the want. It's what the story is actually about, even if the character spends 300 pages avoiding it.
Take a character who wants revenge against the man who ruined her family. That's a clean, plot-friendly want — it can drive heists, confrontations, alliances, betrayals. But say her actual need is to forgive, or at least to stop organizing her whole identity around the wound. Now every scene where she gets closer to revenge is quietly pulling her further from what she needs. That gap — want in one hand, need in the other — is where real conflict lives. Not villain-shaped conflict. Character-shaped conflict, which is the kind that makes readers feel a book rather than just follow it.
Without a need, a want is just a task list. With one, every step toward the goal costs the character something, and cost is what turns a plot into a story.
Why Motivation Has to Survive Contact with Every Scene
Once you've got a want and a need established, the job isn't done at chapter one — it has to survive contact with every single scene after that. Call it motivation-to-scene traceability: for any scene in the book, you should be able to point at it and say whose want or need it's serving, and how.
This sounds obvious until you audit an actual draft. Writers build scenes for plot mechanics constantly — we need the characters in this location, we need this piece of information delivered, we need the reader to meet this side character before Act Three — without checking whether anyone in the scene actually wants something. The information gets delivered. The reader meets the side character. Nothing happens emotionally, because nobody in the scene is pushing toward or away from anything they care about.
Readers can feel the difference even when they can't name it. A scene where the plot needs to advance reads as filler. A scene where a character's want is on the line reads as necessary, even if the plot barely moves. Motivation is what makes events feel like they matter, independent of how large the events are.
The Traceability Test: A Scene-by-Scene Audit
Here's the actual method, and it takes about an hour for a full manuscript if you're not precious about it.
- List every scene, in order, one line each.
- Next to each one, write a single sentence: [Character] wants [X] because [Y], and is blocked by [Z]. Or, for internal scenes, name the need being confronted or avoided.
- Flag any line you can't finish.
You'll usually find three kinds of blanks:
- The scene is genuinely dead weight. It exists to move a character from A to B or deliver information that could arrive another way. Cut it or fold it into a scene that does have motivation attached.
- The scene has a want but it's borrowed from the plot, not the character. ("She goes to the meeting because the plot needs her there.") Fix this by asking what she'd actually want out of walking into that room — even if it's small.
- The scene is fine, but the want or need just isn't visible on the page. This is the good kind of blank. It doesn't mean cut — it means you found a spot where a beat of internal motivation should have been reinforced and wasn't. Add a line of interiority, a gesture, a choice that shows what she's after, and the scene earns its keep.
That last category is the one writers skip past, assuming a blank always means "delete." Sometimes a blank is telling you exactly where to add, not subtract. If you're doing this audit off a fresh draft, it pairs well with a broader structural pass — see our piece on outlining a novel fast if you want a system for catching these gaps before you're 200 pages deep.
When Want and Need Collide (This Is Your Climax)
The strongest climaxes aren't the ones with the biggest external obstacle. They're the ones that force a character to choose between the want and the need — where getting the thing they've been chasing the whole book would mean betraying the thing they actually need to become.
Go back to the revenge example. Say the climax puts her in a room alone with the man who ruined her family, no witnesses, a plausible way to make him disappear. The want says take it — this is the payoff the whole book has been building toward. The need says something else: that killing him won't undo anything, that she's spent years being loyal to a wound instead of to the people still alive who need her. The scene isn't tense because he might fight back. It's tense because she might choose wrong, and either choice will cost her something real.
That's why an external obstacle alone — a lock she can't pick, a guard she can't get past — rarely lands as hard as it should. It tests competence. A want/need collision tests identity. Readers stay up late for the second kind, because they're not asking "will she succeed," they're asking "who is she going to decide to be."
If you're building toward one of these moments and want to check that it's landing, our post on writing a plot twist covers a related idea: the best reveals recontextualize motivation the reader thought they understood, which is exactly the mechanism at work in a good want/need climax.
Motivation Drift: How Characters Quietly Lose Their Reason to Act
Here's the failure mode that sneaks past even careful writers: motivation is crystal clear in chapter one and then just evaporates by chapter ten. The character keeps doing plot-shaped things, but the why stopped being reinforced pages ago, and by the midpoint the reader is running on fumes, half-remembering a motivation they haven't seen evidence of in fifty pages.
This happens because writers front-load motivation in the setup and assume it'll carry itself. It won't. Wants need to be reaffirmed, complicated, or paid a cost against periodically, or they go stale in the reader's memory even if they're technically still "true" in the story.
Build in checkpoints. At each act break, the midpoint, and the climax, ask: does the original want/need still apply, unchanged? If yes, has it been reinforced recently, on the page, or is the reader just supposed to remember it from chapter two? If the motivation has evolved — which is often good and realistic — has that evolution been shown, or did it just quietly happen off-page between drafts?
A character whose revenge-want curdles into something closer to grief by the midpoint is a stronger character than one whose want never moves. But the reader needs to see the curdling happen. Motivation drift becomes a problem only when it's accidental — when you, the writer, drifted along with the character without noticing, and now the ending doesn't match the setup you built.
Building the Habit: Tools for Keeping Motivation Visible
The audit works, but only if you actually run it, which means the easiest fix is making motivation visible while you're drafting, not just during revision.
Some options that don't require new software:
- A spreadsheet with one row per scene and a column for want/need — ugly, fast, effective.
- Index cards, one per scene, with the motivation line written on the back so you can flip through and spot-check without re-reading the scene itself.
- An outlining tool that lets you attach a note to each scene card as you build the structure, so motivation gets set before you draft rather than reverse-engineered after.
If you're outlining in Just Write, this is basically what the scene-card fields are for — a place to pin the want/need line right next to the beat, so it travels with the scene instead of living only in your head. It's a small habit that saves a large revision later.
If you haven't nailed down your overall structure yet, our story structure for beginners post is a good companion to this one — it covers the shape motivation needs to move through across three acts, which pairs naturally with the scene-level audit here.
Try This Now
Pull up your current chapter and run the test cold:
- For each scene, write one line: [Character] wants ___ because ___, blocked by ___.
- Circle any line you can't finish in under ten seconds.
- For each circled scene, decide: cut it, reroute its purpose to serve an existing want/need, or add the missing beat of motivation that should've been there.
- Check your last chapter break — is the original want/need still active, evolved on purpose, or just quietly abandoned?
If the audit turns up more gaps than you expected, that's information you didn't have an hour ago. And if it reveals a structural hole big enough that you're not sure how to rebuild the scene around it, that's exactly the kind of problem Just Write is built to help with when you're ready to draft the fix rather than just diagnose it.