You tell the reader, flat out, that a betrayal is coming. Best friend, you write, was going to ruin everything. Now you don't tell them when, and you don't tell them how. Then you write a quiet dinner scene where the two friends laugh over wine, and the reader sits there with their stomach in a knot, because you handed them the knowledge and withheld the moment — and that gap, between knowing and seeing, is where the dread lives.1
That is suspense, and it is not surprise. Surprise is the bomb going off when no one expected it — one jolt, then over. Suspense is the bomb under the table that the audience knows about and the characters don't, ticking through an ordinary conversation. The reader doesn't relax because they know. They tense because they know. The master move of this whole concept is counterintuitive: you build the most dread not by hiding the danger but by revealing it, and then refusing to say when it lands.1
Suspense is the tension that comes from anticipated disaster, and Alpay's key insight is the sequencing: reveal the why before the how.1 Let the reader know a betrayal — or a death, or a fall — is coming. Withhold how and when it will arrive. That withheld timing is the engine. He puts it plainly: the gap between knowledge and confirmation is where suspense thrives.1 [POPULAR SOURCE]
It is not genre-locked. Suspense isn't just for thrillers, Alpay says; it can run under any genre, because the mechanism is structural, not tonal.1 A romance, a literary drama, a cozy mystery — any of them can plant a looming thing and let the reader squirm toward it. The tools are small and concrete: foreshadow the disaster, drop a line like it was the last time they'd ever speak, and seed subtle cues that something is off — a busted lock, a strange smell no one can place, a character who's a little too friendly.1 You give the reader reason to suspect, and then you don't answer right away.1
Why does telling the reader the bad news increase the tension instead of releasing it. Because knowledge without resolution is an itch you can't reach.1 Once the reader knows the betrayal is coming, every calm scene reads double: the surface says dinner, the undertow says not yet, but soon. The reader can't un-know it. So they scan every page for the moment, and the moment doesn't come, and the not-coming is the pressure.
This is the inversion that makes it work. Withholding the fact of the danger gives you one payoff — the surprise, spent in an instant. Withholding only the timing of a known danger gives you a sustained payoff that runs as long as you delay, because the reader is doing the dreading for you, on every page, unpaid labor of anticipation. The cues — the busted lock, the too-friendly smile — keep the dread topped up.1 Each one says here, maybe? and then doesn't deliver, which tightens the spring another turn. You are not building toward a single bang. You are extending the silence before it, and making the silence the loudest thing in the room.
Reveal-why-before-how is a precise application of Suspense as Strategic Exclusion and Inclusion. That page's whole claim is that suspense is built by choosing what to include in the reader's knowledge and what to exclude — and Alpay's sequencing rule is a specific recipe for that choice: include the why (the danger exists), exclude the how and when (its arrival). The handshake gives the broader principle a concrete dial to turn.
It also feeds Foreshadowing and Narrative Setup by setting a tone for the seed. Foreshadowing plants a clue; reveal-why-before-how plants a clue the reader understands as a threat — the busted lock isn't a neutral detail to be recalled later, it's a loaded one felt now. And it sits one notch from Cliffhanger Architecture: a cliffhanger cuts at the moment of maximum not-knowing, while reveal-why-before-how sustains not-knowing across a stretch. The cliffhanger is the spike; this is the plateau the spike rises from.
Take Alpay's own anchor line: it was the last time they'd ever speak.1 Drop that sentence at the top of a chapter and watch what it does to the scene that follows. The chapter is now two friends having a normal conversation — but the reader has been told, before a word of dialogue, that this conversation is terminal. They don't know why it's the last time. They don't know how the rupture comes — a fight, a death, a slow drift, an accident on the way home. The why (this ends them) is on the page; the how is withheld.
Now every line of that ordinary dialogue is charged. A joke lands as poignant. A small irritation reads as the possible seed of the break. The reader studies the scene for the wound, finding none, dreading all of it. That is the entire mechanism in one sentence of setup: the reader knows the outcome and is forbidden the route, so they walk the whole scene braced. Alpay's subtle cues would do the slower version of the same thing — a busted lock at the start of a chapter promises an intrusion without dating it, and the reader carries the lock through every page until something comes through the door.1
It's the afternoon and you're on chapter nineteen, the dinner party, and on the page it's just pleasant — your two leads bantering, a nice scene, dead on arrival. You know one of them betrays the other in chapter twenty-two. Right now the reader doesn't, so the dinner is only a dinner. You reread it and feel nothing pull.
So you go back to the top of chapter nineteen and you add one line before the scene starts. Not the how. Just the why: She would remember this dinner as the last good night before everything broke. You read the banter again and it has completely changed under you — the same jokes now ache, because you've told the reader this is the last good night and let them watch it pass without saying which word, which glance, breaks it. You feel the scene tighten. Then you walk back through and plant one cue: your betrayer refills the other's glass a little too attentively, smiles a little too warmly. You don't explain the smile. You leave it there like the busted lock, a small wrong note the reader will carry into chapter twenty-two, scanning every page for the moment the warmth turns. You resist the urge to foreshadow the method. The reader gets the doom and not the route, and the route is what they'll keep reading to find.
The first way it goes wrong: you withhold the why too. Now there's no looming thing for the reader to dread — just a normal scene that turns out, surprise, to contain a betrayal. You spent the bomb on a single jolt and got none of the slow burn. The page reads flat right up until the bang, which is the signature of a story that confused surprise for suspense.
The second failure is the opposite: you reveal the how along with the why. You tell the reader the betrayal is coming and exactly how it lands, and the gap collapses. There's nothing left to anticipate, only to wait through. The dread leaks out because anticipation needs an unknown to point at, and you removed it. The diagnostic is the busted-lock test: after your setup, does the reader know that danger is coming but not when or how? If they know all three, you've over-revealed; if they know none, you've under-revealed and you're writing surprise. The sweet spot — known threat, unknown arrival — is the only configuration where the silence does the work.
This is craft advice from a list-format video, and the claim that suspense lives in the knowledge-confirmation gap is the source's craft observation, not a measured result.1 [POPULAR SOURCE] It echoes the long-noted idea, associated with Hitchcock, that suspense beats surprise because shared knowledge with the audience generates sustained tension — but Alpay doesn't cite it and the principle stands on its own as practitioner wisdom.
The open tension is duration. The gap generates dread, but a gap held too long curdles into impatience — the reader who has been promised a betrayal for two hundred pages stops dreading and starts resenting. Alpay says withhold and don't answer right away, but "right away" has no upper bound in his telling.1 How long can a known-but-undelivered threat stay charged before the reader gives up on it? An open question the video doesn't touch: does the reveal-why-before-how move require periodic re-priming — fresh cues, near-misses — to keep a long-delayed threat alive, or does the original setup carry it indefinitely?
Alpay's reveal-why-before-how lives in productive friction with the surprise-loving instinct most beginning writers bring to suspense. The intuitive move is to hide the danger and spring it — the twist, the gotcha. Alpay is telling writers to do almost the reverse: give the danger away and ration only its timing. The two are not contradictory so much as differently scaled, and a strong scene often wants both — the reader knows a betrayal is coming (suspense) but the specific form it takes still lands as a small surprise. Where Alpay leans hard toward the shared-knowledge model, a twist-first writer would argue that some of fiction's biggest emotional hits come precisely from the danger the reader didn't see — and that pre-loading every threat can drain a story of its capacity to shock. The convergence is that surprise and suspense are tools for different jobs, not rivals: suspense for the sustained ache of a known doom, surprise for the spike of an unforeseen one. The tension is in the dial. Alpay, correcting writers who over-hide, pushes toward reveal; pushed too far, his own advice would produce stories with no shocks left, every danger telegraphed, the reader never once caught off guard.
The Zeigarnik Effect. The Zeigarnik effect describes how the mind holds an unfinished task in active memory and won't let it go until it's complete. Reveal-why-before-how opens exactly such a task in the reader and then deliberately leaves it open: a betrayal is coming is an uncompleted expectation, filed and nagging, and every page that passes without delivering it keeps the file active. The structural parallel is precise — an announced-but-unresolved event behaves like an interrupted task that the mind refuses to close. Hold the two together and you see why the sequencing matters so much. The effect needs a defined, anticipated completion to nag toward; that's why you must reveal the why. A vague sense that "something bad might happen" doesn't open a clean task — there's nothing specific to leave unfinished. But "the betrayal is coming" is a sharply defined expected outcome, and a sharply defined outcome left undelivered is precisely what the Zeigarnik dynamic clamps onto. The craft rule (reveal the why) and the behavioral mechanism (open a specific, completable task) are the same instruction stated in two vocabularies. The writer who tells the reader what is coming but not when has, in behavioral terms, installed a maximally clingy unfinished task — known endpoint, withheld completion, the exact recipe for something the mind can't put down. It also explains the second failure mode from a fresh angle. Reveal the how along with the why and you have, in effect, handed the reader a way to mentally pre-complete the task: if they can already picture exactly how the betrayal lands, the mind files it as good-as-finished and stops nagging. The dread leaks out not because the event happened but because the brain quietly closed the loop on its own, in imagination. So the craft instruction to withhold the method is, behaviorally, an instruction to keep the task genuinely un-completable in advance — to deny the reader the materials they'd need to resolve it privately and let go.
Information-Gap Curiosity. Information-gap theory holds that curiosity ignites when a person becomes aware of a specific hole in their knowledge. Reveal-why-before-how engineers a very particular hole: the reader knows the outcome (betrayal) and lacks the timing and method (how, when). This is a different gap from a mystery's. A whodunit hides the outcome — the gap is "what happened." Suspense via this technique hides only the path — the gap is "how does the known thing arrive." The insight the two together produce is that not all curiosity gaps feel the same, and the suspense gap is distinctively anxious rather than merely inquisitive. A whodunit reader is curious in a pleasant, puzzle-solving way. A suspense reader who knows the betrayal is coming is curious in a dreadful way, because the missing information is about a bad thing they can't prevent. Same underlying mechanism — an aware, specific knowledge gap driving attention — but the emotional color is set by what kind of fact is missing. Hide a neutral fact and you get inquiry; hide the arrival-route of a known disaster and you get dread. The craft of reveal-why-before-how is, in effect, a way of aiming information-gap curiosity at the reader's threat-anticipation rather than their problem-solving, which is why it reads as tension and not as a fun puzzle to chew on.
Sharpest implication. The strongest dread in fiction may come from generosity, not concealment — from telling the reader the worst, and then making them live every ordinary page on the way to it. That reframes a lot of beginner instinct, which equates withholding with tension. The move here is to withhold less (give away the threat) and ration more precisely (hide only the arrival), and the precision of what you hide matters more than the amount.
Generative questions.