| name | therefore-but-not-and-then |
| description | Connect every beat to the next by causation (therefore) or disruption (but), never by mere sequence (and then). The momentum rule for scenes, campaigns, chapters, and arguments. Load when writing a narrative session, a campaign arc, or any prose that lists when it should drive. |
Therefore / But, Not "And Then"
Why This Exists
Trey Parker and Matt Stone gave the cleanest test for whether a story has momentum. Take your beats and read them aloud with the connective word between them. If the honest word is and then — "this happens, and then this happens, and then this happens" — the story is a list, and a list has no pull. If the honest word is therefore or but — "this happens, therefore this happens, but this happens" — every beat is caused by or colliding with the one before it, and the audience is carried.
This is not a storytelling gimmick. It's how consequence works. A scene where each moment earns the next has gravity. A scene that just accumulates events is something you watch from outside.
The Rule
Between any two beats, exactly one of these should be true:
- Therefore — beat B happens because of beat A. The party freed the prisoner; therefore the warden now hunts them.
- But — beat B complicates or reverses beat A. The party freed the prisoner; but he was the one who betrayed them.
If the only honest connective is and then (or also, next, meanwhile, the first thing… the second thing), the beat is sequence, not story. Three options:
- Cut it. If a beat doesn't cause or complicate, the scene rarely misses it.
- Find its causation. Often the therefore is there and you hid it under a spatial transition. Surface it.
- Make it a "but." Introduce the friction that turns a step into a turn.
In Practice
A campaign arc is a therefore/but chain at the macro scale: the players' choice in session 3 therefore the faction's reprisal in session 5; the reprisal but an unexpected ally. Map the chain before the session — if two sessions connect only by "and then they traveled to the next town," the campaign has gone slack.
A combat or scene is the same at the micro scale. Not "the orc attacks, and then the rogue attacks, and then the wizard casts." Rather: the orc drops the fighter (therefore the cleric breaks formation to heal, but that opens the flank). Initiative order is and then; consequence is therefore/but. Narrate the consequence, summarize the sequence.
Dialogue turns on the same hinge. A character makes a claim; the reply should follow from it (therefore) or cut against it (but) — not just take the next conversational turn.
What This Is Not
- Not a ban on the words "and then" in prose — it's a test for whether your structure is causal. You can write the sentence "and then the door opened" if the door opening is a therefore of what came before.
- Not an excuse to over-explain. The causation can be felt without being stated. The reader supplies the therefore if you've set it up; you don't always narrate it.
The Quick Audit
Before you ship a scene or session, read its beats in order with the connective spoken aloud:
Beat 1 — [therefore / but / and-then] — Beat 2 — [therefore / but / and-then] — Beat 3 …
Every and then is a flag. Cut it, cause it, or complicate it. Zero and thens between major beats means the scene drives instead of lists.
