All resources

Resources

Find Your Story's Argument

Theme is rarely something the writer brings to the story. It is something the story produces when its characters and world collide correctly. Stage the collision. Read off what it generates

Someone asks what your novel is about. You can describe it. You give them the protagonist, the genre, the inciting situation, possibly a few of the central conflicts. They follow. They are interested. Then they ask the second question — what's it about, though? — and you find that you don't have an answer. Or you have an answer that sounds like the back of a paperback. Love. Power. The cost of ambition. The asker nods politely. Both of you know the question wasn't really answered.

This is one of the most common, and most under-discussed, places to be stuck. The reason it is under-discussed is that the writers in it usually have no language for the problem. They suspect the problem is that they don't know what their story is about. They are right and wrong at once. They know what their story is about. They don't know what it argues about that subject. The two are very different, and the difference is the entire reason the second question feels unanswerable.

Theme is rarely something a writer brings to the story. It is something the story produces — but only if the architecture beneath it is correct. Love conquers all is not a theme; it is an aphorism. This story argues that love requires the surrender of the need to be right is a thematic argument, and you will notice immediately that it has properties the aphorism does not. It implies a specific value shift (from "needing to be right" to "willing to surrender"). It implies a specific climax (the moment the protagonist surrenders, or refuses to). It implies what the dark night before the climax is testing (the protagonist's last attempt to be right). The thematic argument is structural. The aphorism is decorative.

You cannot assert your way to the argument. You have to generate it. And generation requires staging the right collision.

The collision is between a specific character's specific Misbelief and a specific world's specific demands. Not a character carrying generic flaws; a character carrying a specific false belief about how the world works. ("Love is a transaction." "Trust is weakness." "Power is the only thing that keeps you safe.") Not a world built for atmosphere; a world engineered to refuse that exact belief. ("This world is one where transactional love costs the protagonist the only person they actually need to be loved by." "This world is one where the people who treat trust as weakness become the loneliest figures in their own families." "This world is one where the protagonist's power has bought them a kingdom they cannot stand to live in alone.") Stage that collision. Watch what it produces. The argument is what it produces.

This is the move that distinguishes theme work from theme assertion. Theme assertion sounds like the writer announcing the story's moral. Theme generation sounds like the writer reporting a finding. The story tested something; here is what it found. The first sounds like a sermon. The second sounds like a story.

The discovery is mechanical, once the collision is staged. Write down, in plain language:

- What the protagonist's specific Misbelief is, before the story begins. (Not "trust issues." Specifically what false belief about the world they operate by.)

- What the world's specific demands are, that this Misbelief cannot meet.

- What happens, in the climax, when the Misbelief is finally tested and either surrendered or doubled down on.

The thematic argument is the sentence that completes: This story argues that — and continues with what the climax actually demonstrates. You are not inventing the argument; you are reading off what your collision generates. If the collision is not specific enough to generate a sentence, the issue is not theme — the issue is that the protagonist's Misbelief, or the world's demands, were not committed precisely enough. (Most often it is the Misbelief. Misbeliefs that are too vague — "she's afraid of being hurt" — produce themes that are too vague. "She believes that anyone who has hurt her once cannot be trusted again" produces a theme that knows what it is doing.)

Once the argument is in your hands, every downstream decision starts to settle. The structure clarifies — every act break has to advance some part of the proof, and now you know what is being proved. The midpoint reversal reverses something specific. The all-is-lost moment loses something specific. The climax demonstrates the value shift, not generic dramatic resolution. Subplots can now be tested for inclusion: a subplot that complicates, illuminates, or contrasts the central argument earns its place; a subplot that does none of these is a detour, even if it's well-written. (This is also where the subplot you've been carrying for affection but couldn't justify often gets its severance notice. The argument is the test. If the subplot doesn't speak to it, it goes.)

And the question you couldn't answer at the dinner party becomes answerable in a sentence. It's about love, but what it argues is that love requires the surrender of the need to be right. Eight more words than you had before. They are the right eight words. The asker nods, and this time it means something.

A few practical notes. Do not commit the argument before you have staged the collision. Themes asserted without collision become things the structure tries to prove without ever having generated the question. The audience feels the difference, even when they cannot name it. Do not commit the argument once and stop interrogating it. The argument refines as the draft develops, often becoming sharper — love requires the surrender of the need to be right, in the specific case where the protagonist's idea of being right has cost them the people who could have shown them what love actually was. That sharpening is the story telling you what it is about, more precisely, the longer you spend with it.

And do not be alarmed if the argument that emerges is unfashionable, or unflattering, or strange. The argument the story generates is the argument the story generates. Asking the story to produce a different one — one closer to what you'd hoped to be writing — produces work that is, in the technical sense, dishonest. The reader notices, even when they cannot name it. Trust the collision. Write what it produces.

The story you couldn't say what it was about can be said. It just hadn't finished its experiment yet.