Scene and Sequel
Scene and sequel is a two-beat pattern for structuring prose fiction, set out by Dwight V. Swain in Techniques of the Selling Writer (1965). A scene is a unit of action built from a goal, the conflict that obstructs it, and a disaster — an outcome that leaves the character worse off or facing a new problem. A sequel is the unit that follows: the character's reaction, the dilemma the disaster has created, and the decision that sets the next goal. The decision hands off to the next scene, and the cycle runs again.
The value of the model is not that stories must be built this way. It is that it gives you two named things to look for, and most drafts that feel wrong are missing one of them.
The scene half: goal, conflict, disaster
A scene in Swain's sense starts with a character wanting something specific and reachable within these pages — not "wants to be loved" but "wants the address." The goal should be legible to the reader early, because it is what turns reading into watching: once you know what someone is trying to do, you can tell whether it is going well.
Conflict is whatever stands between them and it. The important word is between — opposition that arrives after the goal is achieved is not conflict, it is the next scene.
The disaster is the part writers soften. It does not mean catastrophe; it means the scene does not simply deliver what was wanted. The three usable outcomes are no, no — and worse, and yes — but. A run of scenes that end in plain yes is the most common cause of a middle that reads as competent and inert.
The sequel half: reaction, dilemma, decision
The sequel is where readers catch up emotionally, and it is the half that gets cut.
- Reaction is the involuntary part: the physical and emotional response before thought arrives. It buys the disaster its weight. Skip it and readers register the event without feeling it.
- Dilemma is the reasoning: the options, all of them bad, examined. This is where a character reveals what they actually value, because a choice between two goods reveals nothing.
- Decision is the turn back outward, and it is the load-bearing beat — it produces the next goal, which is why a book made only of scenes eventually feels like it is happening to a character rather than being driven by them.
Sequels are also your pace control. They are the only legitimate place to slow down: exposition, reflection and interiority all sit here without stalling the book, because the reader is waiting for a decision.
How to use it as a diagnostic
The pattern earns its keep in revision more than in planning. Two symptoms, two readings:
| What readers say | Usual cause | Fix |
|---|---|---|
| "It's exhausting" / "I couldn't care about anyone" | Scenes with no sequels between them | Add reaction and decision beats; let one disaster land before the next arrives |
| "It drags" / "Nothing happens" | Sequels with no scenes — reflection without new goals | Cut the dilemma to its sharpest option and get the decision on the page sooner |
| "I don't know what they want" | Scenes opening without a goal | State the goal in the first half-page, even obliquely |
| "The ending felt unearned" | Disasters that were really successes | Audit outcomes: how many end in plain yes? |
Two cautions. The first is that this is a rhythm, not a rule — a great deal of excellent fiction interleaves the two halves, hides sequels inside dialogue, or runs a sequel for one viewpoint character while another's scene is still going. The second is the naming collision: Swain's sequel has nothing to do with a follow-up book, and the confusion is common enough to be worth flagging when you use the term with a critique partner.
How to track this in Writer Studio
The awkward part of applying this model is that Swain's "scene" and a manuscript's scene are not the same object — his is a pattern, and it can span one section, half of one, or spill across two. Writer Studio does not resolve that for you, but it does make the pattern visible where you write.
Every scene in a Writer Studio project carries its own properties, and three of them line up almost exactly with the first half of the model: Goal, Conflict and Outcome, alongside fields like status, POV character, emotional tone and private author notes. Filling those three in for a scene you have already drafted is the fastest audit available — a scene whose Conflict field you cannot fill in is usually the flat one, and a run of Outcomes that all read as success is the sagging middle, visible as text rather than as a feeling. Sequel passages behave differently on purpose: their Goal and Conflict fields will often be empty, which is diagnostic rather than a defect, and the Emotional tone field is the one that carries information there. This is alpha software; nothing scores your rhythm or counts your disasters. The properties are just a place to write down what each section is doing, so the shape of the draft stops being something you have to hold in your head.
Most sagging middles are a run of scenes that end in yes — fill in goal, conflict and outcome for twenty scenes in Writer Studio and the run becomes obvious. Free, offline, and filling in properties never touches the scene text itself.
Related
Scene and sequel is the smallest structural unit, so it pairs naturally with the pages above and below it in scale:
- Every craft term: writer's glossary
- Story structures — the book-scale frameworks this rhythm runs underneath
- Internal conflict — what the dilemma beat is actually dramatizing
- Stakes — why a disaster registers as a disaster
- Cliffhanger — what happens when you break between the disaster and the reaction on purpose
- In the app: scene properties, manuscript structure