You know the feeling. You pick something up - a novel, a game, a serialised story - fully intending to dip in for twenty minutes. An hour and a half later, the battery on your phone is dying and you've missed dinner. You weren't even sure you liked it that much. So what happened?
And then there's the other kind. Something everyone recommends, beautifully written, critically adored. You read thirty pages, put it down to make a cup of tea, and somehow never go back. It sits on the nightstand for three weeks. You feel vaguely guilty every time you see it.
The gap between those two experiences isn't really about quality. It's about something more mechanical - and once you see it, you can't unsee it.
The engine underneath every page-turner
Stories that pull you forward share a structural trick: they end almost every scene or chapter with something unresolved. Not a cliffhanger in the cheap, contrived sense. Just an open loop. A question the reader is now holding. A situation that hasn't landed yet.
The brain, apparently, doesn't like open loops. It keeps returning to them. It treats an unanswered question the same way it treats an itch - not dangerous, but persistently there. So you turn the page not because you've decided to, but because some quieter part of you simply isn't done yet.
Stories that stall tend to do the opposite. They close each scene neatly. Everything is resolved, explained, tidied. The reader puts the book down feeling satisfied - which is precisely the problem. Satisfied readers stop. Restless ones don't.
Stakes are what make a choice feel real
Here's the other half of it: momentum isn't just about what happens next. It's about whether what just happened mattered.
Think about the last time you played a game - or read a story - where your decisions felt genuinely consequential. Where you paused before choosing, because you knew the choice would stick. That pause is the reader (or player) feeling the weight of the moment. It's the opposite of breezing through.
Stories lose readers not just when they're slow, but when they're weightless. When a character makes a dramatic choice and the world shrugs. When something is destroyed and reappears two chapters later, quietly undone. When the narrator is too kind, too eager to smooth things over, too reluctant to let a bad decision land badly. You stop trusting the story. And once you stop trusting it, you stop caring what happens next.
We've written a bit about this from the angle of interactive fiction - what stories teach us about consequence - but it applies just as much to novels and films. The mechanism is the same. Stakes are what make a choice a choice.
Why does pacing feel so hard to get right?
Part of the difficulty is that good pacing is almost invisible when it's working. You only notice it when it isn't. A scene that lingers two pages too long, a revelation dropped too early, a subplot that never quite connects - these register as vague dissatisfaction, a sense that the story is somehow... not quite earning your attention, even if you can't say why.
Writers talk a lot about pacing as if it's a single thing, but it's really several things at once. There's scene-level pacing - how quickly individual moments move. There's structural pacing - how the story distributes its peaks and valleys across the whole. And there's what you might call informational pacing - how much the reader knows versus how much they're still waiting to find out.
Get all three right simultaneously and you have a page-turner. Get one wrong and the whole thing can feel off, even if the writing itself is excellent. Spot on craft at the sentence level can't rescue a structure that's fundamentally stalled.
What interactive stories reveal about this
Interactive fiction makes all of this unusually visible, because the reader is also a participant. When a story forgets what happened earlier - when a character ignores something you did two chapters ago, or a consequence quietly evaporates - you feel it immediately. The illusion breaks. The open loops you were holding suddenly feel pointless, because you've learned the story isn't actually keeping track.
That's one of the real reasons AI-driven text adventures have struggled to hold players. It's not that the prose is bad or the premise is weak. It's that the story keeps dropping its threads. The tension that pulls you forward depends on trusting that the story remembers what you're both doing - and that trust is surprisingly fragile.
It's something we think about a lot with Wordfarer, our interactive text adventure in development for Android and iOS. The whole point of giving a story a real shape - chapters that build, characters who remember how you've treated them, a genuine ending rather than an infinite wander - is that it earns the reader's trust back. A tale that holds together is a tale you can actually be pulled through, rather than one you're perpetually sliding off the side of.
We've looked at how rare it is for characters to genuinely remember you across a story, and the effect on momentum when they do is striking. It turns out that consistency isn't just a technical nicety. It's load-bearing structure.
The stories that stick
The books you couldn't put down probably had all of this working quietly in the background. Open loops. Stakes that held. A structure that knew where it was going and let you feel the approach of the ending without giving it away too soon.
The ones that stalled probably had at least one of those things missing - and it didn't matter how beautiful the sentences were. Momentum is its own craft. And it's the part that keeps the light on past midnight.