Key Principle
Every plot point must be mined from the protagonist's established backstory and then validated through three progressively harder "Why" tests before it enters the blueprint. Plot invented from scratch tends to pull the story off the third rail; plot harvested from backstory arrives pre-connected to the protagonist's internal struggle.
The Three "Why" Tests (Ch. 13):
- "Why does my plot need it to happen?" -- The easiest test. Eliminates random, tempting plot points. If the plot does not need it, discard it.
- "Logistically, why can it happen? Is it actually possible?" -- Tests whether the event is possible given the story's established specifics. Catches assumptions the writer treats as givens.
- "Why would it happen, given your protagonist's inner struggle?" -- The hardest test. Connects the plot point to the protagonist's misbelief. This is what gives insight into the plot point's true meaning.
These tests are not just filters -- they are generators. Each answer produces new specifics the writer did not have before. "Specifics beget specifics." -- Lisa Cron, Chapter 13
Why This Matters
Without these tests, writers run with plot points that sound plausible but contain logic glitches, discovering pages later that everything built on that point is "completely moot." Testing early prevents discarding months of work. Without harvesting from backstory, the plot "gallops off on its own trajectory," creating surface storylines that hijack the story. Once this happens, "meaningless specifics lead to more of the same" -- and the chain reaction can continue for hundreds of pages, all of which must be discarded. (Chapter 12)
Good Examples
Jennie's Nora plot point (Ch. 13): The idea that Nora can force Ruby to leave her house passes Test #1 (the plot needs it). It fails Test #2 -- Ruby is successful, so what gives Nora this power? Solution: Nora owns the house. Test #3 asks why Nora owns it, uncovering that their parents willed it to Nora, that the parents were cold and disconnected, that Nora craved family connection. One "Why?" chain produced the emotional core of the entire novel.
Jennie's dog caper (Ch. 12): Search teams and press conferences made complete external sense but had nothing to do with Ruby's actual problem. The caper was seductive precisely because the external cause-and-effect seemed to write itself -- which is the exact trap.
Secrets and lies as plot engines (Ch. 12): Ruby sabotaged her wedding to Henry by deliberately triggering a migraine -- yielding both the backstory wedding scene and the present-day scene where the deceit surfaces. Secrets planted in backstory detonate in the novel's present.
Counterpoints
Running with an untested plot point: Writers who skip the "Why" tests build scaffolding on a faulty foundation. "Everything built on that point is completely moot." -- Lisa Cron, Chapter 13
Inventing plot from scratch: External events created without connection to established backstory lack organic connection to the protagonist's struggle. "It's the constant laser beam focus on your protagonist's story-specific inner struggle that will keep you from allowing surface storylines to hijack the story you're telling." -- Lisa Cron, Chapter 12
Stopping at Test #1: Passing only the first test (plot need) creates events that are logistically impossible or internally unmotivated. All three tests must be cleared.
Key Quotes
"Specifics beget specifics." -- Lisa Cron, Chapter 13
"It's the constant laser beam focus on your protagonist's story-specific inner struggle that will keep you from allowing surface storylines to hijack the story you're telling." -- Lisa Cron, Chapter 12
"How will this event drive my protagonist's internal journey and so propel my story forward?" -- Lisa Cron, Chapter 12
"Always make it harder for your protagonist. Never give him the benefit of the doubt. If a bad thing could happen, let it happen." -- Lisa Cron, Chapter 13
Rules of Thumb
- Before adding any plot point, ask: "Did I mine this from backstory, or did I invent it from thin air?"
- Apply all three "Why" tests in order -- do not skip to the third
- If a plot point fails any test, do not force it; let the "Why" chain generate a better alternative
- Everything the protagonist does to improve the situation should make it worse
- When large sections of the cause-and-effect chain lack events, find a single specific "What" and begin digging with the three tests
Related References
- Writing Forward: Making the Invisible Visible - Spiral revision catches logic breaks the "Why" tests missed
- Implementation Playbook: The Story Genius Process Step by Step - Where the "Why" tests fit in the full process
- Subplots, Storylines, and Secondary Characters - Subplot events also require "Why" test validation