
I want to tell you about the most technically correct novel I ever wrote.
Inciting incident on page twelve. First plot point at the 25% mark, to the paragraph. Midpoint reversal precisely at the halfway line. Dark night of the soul exactly where the spreadsheet promised it should go. I had the beat sheet taped to the wall and I hit every single beat like a man landing a gymnastics routine.
And the book was dead.
Not bad. That’s the thing. It wasn’t bad — it was competent, which is worse, because bad is fixable and competent just sits there. Beta readers all said a version of the same sentence, in the apologetic voice people use when they can’t articulate what’s wrong: “I don’t know. It just… didn’t grab me.”
Save the Cat didn’t do that to me. Treating it like a filing cabinet did.
Every story framework you’ve ever encountered, three-act, the hero’s journey, the beat sheet, the story circle, the seven-point, all of them, was built the same way. Somebody looked at a large pile of stories that worked, noticed the patterns they shared, and wrote the patterns down.
That makes these frameworks descriptive. They describe what stories that succeed tend to have in common.
We then use them prescriptively. We treat the description as a set of build instructions, generate a story that satisfies the description, and then act surprised when it has all the parts of a living thing and none of the life.
It’s the difference between a description of a face and a face. You can list the features: two eyes, symmetrical, mouth below nose, and follow the list perfectly and still produce something no one wants to look at. The list was never the point. It was a record of what faces have in common, written by someone who was looking at real ones.
Here’s the tour nobody gives you. Not what each framework is — you can Google that in eight seconds — but what each one is genuinely useful for.
Don’t choose a framework by genre. Choose it by asking one question about your specific book:
What is the engine of change in this story?
There are basically four answers, and each one points somewhere different.
Answer that question honestly and half your structural problems evaporate, because most structural problems are actually a mismatch — a revelation story wearing a goal story’s skeleton, limping.
Here’s my actual practice, offered without any claim that it’s the only way.
Draft toward the story. Not toward the framework — toward the story, following the thing that’s alive in it, letting it be misshapen. Then, when you have a draft, hold a framework up against it and look for the places where the tension slackens, where the middle sags, where a promise got made and never paid.
The framework is at its best when it’s a diagnostic instrument. It’s at its worst when it’s a straitjacket. Same tool. Entirely different results depending on when in the process you pick it up.
Structure applied early gives you a book that hits its marks. Structure applied late gives you a book that hits its marks and has a pulse, because the pulse got to come first.
I hear this objection every time I make this argument, and it’s a fair one, so let me take it seriously.
Some writers genuinely cannot finish a draft without scaffolding. They’ve got four abandoned manuscripts in a drawer and the beat sheet is the only thing that ever got them to the end. Telling that writer to “draft toward the story” is telling them to go back to not finishing.
Fine. Use the scaffolding. Finish the book. A finished mediocre draft is worth infinitely more than an unfinished brilliant one, because you can revise the first one and you cannot revise a feeling you had in the shower.
But know what you’re doing, and — this is the part people skip — know that you’re not done when you hit the last beat. If you drafted on rails, your revision has a specific job that other people’s revisions don’t: go find the places where the story wanted to do something else and you overruled it because the sheet said turn left. You’ll remember them. There’s always a moment around the midpoint where the draft went quiet and you pushed through it. Go back there. That’s where your book is hiding.
The scaffolding gets you a building. It doesn’t get you a home. Somebody still has to move in.
If you take one practical thing from this piece, take this.
Get a draft — yours, or a novel you love — and map it against two frameworks, not one. Say, three-act and Kishōtenketsu. Or the beat sheet and the story circle.
They will disagree. That’s guaranteed, and that’s the whole exercise.
The places where two frameworks disagree about what should happen next are the places where your story is most alive. They’re the moments that aren’t determined by convention — where the book could go either way, and you, the actual author, have to make a real decision instead of a default one.
Mapping against one framework tells you what the convention wants. Mapping against two shows you where you have freedom, and freedom is where books get interesting.
Answer the engine question on an index card: goal, wound, relationship, or revelation? One word.
Then look at the framework you’ve been using and ask whether it was built for that engine. If it wasn’t — if you’ve been running a revelation story on a beat sheet built for escalation — you’ve just found the reason the draft feels like it’s fighting you.
Learn all of the frameworks. They’re all describing the same animal from different angles: a person who wants something, is prevented, and is changed by the prevention. Every one of them is a partial truth about that animal.
Learn all of them. Marry none of them.

Copyright 2025, Troy "the Plot Dude" Lambert, All Rights Reserved
“Plot Nihilists believe in nothing. Don’t be like them.”