Promise, Progress, Payoff

Definition

The frame comes from Brandon Sanderson's BYU classes. Each narrative thread (main plot, romantic subplot, secondary character arc, mystery) runs in three beats: we promise something to the reader, we progress toward that promise, we pay it off. Forgetting any beat breeds frustration or boredom.

What it's for

It's a thread-level diagnostic. For each subplot: What promise did I make (and where)? How is it progressing? Does the payoff answer the exact promise, not a neighboring one? Many manuscripts lose readers because they pay off a promise, just not the one made.

The three beats

Promise

• Set early (first pages, first chapter).
• Implicit (genre, tone, cover) + explicit (opening scene, first conflict).
• Must create a dominant question: who is the murderer? Will the couple end up together? Will Frodo reach Mordor?

Progress

• Each act moves the same question, not a parallel one.
• Mix of gains and losses (Try-fail cycles).
• The reader alternately feels we approach and drift from the answer.
• The rhythm adjusts: progression accelerates toward the end.

Payoff

• Answers the original promise, not another.
• Often larger than expected, never smaller.
• Must be earned (try-fail cycles, consequences, cost).
• Often carries a symbolic cost: nobody reaches the payoff unscathed.

Variants by genre

• Romance: union promise → emotional progress → payoff (HEA/HFN or tragic).
• Mystery: solving promise → investigation progress → payoff (coherent reveal).
• Fantasy quest: goal promise → journey / trials → payoff (mission accomplished, transformed).
• Literary fiction: thematic promise → exploration → often ambiguous payoff (illumination).
• Thriller: survival promise → escalation → payoff (rescue, sacrifice).
• YA / coming of age: transformation promise → attempts → identity payoff.
• Subplots: each subthread has its own P-P-P, closed before or during the main payoff.

Common pitfalls

• Implicit promise (romance cover) not honored by the text (little romance, action focus).
• Progress on one thread when the promise was on another.
• Payoff to the wrong promise: a side thread is resolved, the main one forgotten.
• Payoff smaller than the promise → disappointment ("that was it?").
• Too many competing promises: none gets its payoff.

Examples

• The Lord of the Rings: promise (destroy the Ring) → progress → payoff (Mordor, Scouring of the Shire as bonus).
• The Name of the Wind (Rothfuss): promise of a tragic hero's tale → book 1 progresses → series-delayed payoff.
• Six of Crows (Bardugo): promise (heist + crew) → try-fail progress → double payoff (heist + relationships).
• Farseer (Hobb): promise of loyalty → painful progress → always-costly payoff.
• Murder on the Orient Express: whodunit promise → investigation progress → collective-twist payoff.
• Pride and Prejudice (Austen): Lizzie-Darcy promise → animosity-rapprochement progress → classical payoff.
• Breaking Bad: promise "Mr. Chips becomes Scarface" → 5-season progress → full payoff.

Writing tips

P-P-P isn't a plotting template, it's an audit tool. Apply it thread by thread, in revision, to spot where readers will disengage. Our method.

• Map each thread in 3 lines: "Promise: … (chapter X). Progress: … Payoff: … (chapter Y)." A thread that doesn't hold in 3 sentences is too vague for the reader.
• Chapter-3 rule for the main promise: if the dominant question isn't put to the reader by the end of chapter 3 (or 10 % of text, whichever comes first), 60 % of readers drop off. Flag the exact scene that plants the promise.
• 40/60 gains-to-losses ratio in progress: the reader must lose more often than win across the Try-fail cycles. An 80/20 gains progression goes flat and signals missing Stakes.
• Exact-payoff test: say the original promise aloud, then the payoff. If both don't share the same keywords (character, stake, object), the payoff answers the wrong question — 70 % of "disappointing endings" in beta reads live there.
• Cap of 4 active threads at once: beyond that, none gets the scene count its payoff needs. Excess threads become subplots to close early or defer to the next book.
• Payoff always bigger, never smaller: measure payoff ambition on personal stake + external stake + symbolic cost. If any one is below the promise, the reader feels disappointment before naming it.

Further reading: narrative threads and reader promises provides the per-thread tracking grid we use so no payoff is lost, and narrative tension and suspense covers the progression mechanics that prevent boredom between promise and payoff.

Revision checklist

• For each thread: is the promise set in the first chapters?
• Does the progress work exactly on that promise, not another?
• Does the payoff answer the promise set, not a neighbor?
• Is the payoff earned (try-fail cycles, visible cost)?