Introduction
New editors, and most writers editing their own work, tend to read a scene the way a reader does — for what happens. That instinct is exactly right for a first read and exactly wrong for a diagnostic one. This lesson teaches the first move every working editor learns to make: reading a scene for what it changes, not for what occurs in it. It's the entry point to the Framework's first pillar, Structural Clarity, and the foundation every later lesson builds on.
Learning Objectives
- Distinguish between what a scene depicts and what a scene changes.
- Apply a three-question diagnostic to any scene in a manuscript.
- Identify scenes that generate incident without advancing structural stakes.
- Begin building a personal vocabulary for describing structural problems precisely.
Core Lesson: Diagramming Causality, Not Plot
Ask a writer what happens in their opening chapter and you'll get a fluent, confident answer: a character wakes up, receives a phone call, argues with a sibling, leaves the house. Ask what changes by the end of that chapter, and the answer usually gets much less confident. That gap is the whole problem this lesson addresses.
Plot is a sequence of events. Structure is a sequence of consequences. A scene can be full of events and contain almost no structure — and readers, even readers who can't articulate why, feel the difference immediately. They call structureless scenes “slow,” even when a great deal is technically happening in them.
The diagnostic we teach is simple to state and genuinely difficult to apply honestly:
For any scene, ask: what did a character know, want, or believe at the start that is different by the end — and who else in the story is now forced to react to that difference?
Notice what the question does not ask. It doesn't ask whether the scene was well-written, whether the dialogue was sharp, or whether the setting was vivid. Those are real craft questions, but they belong to a different pillar (Sentence-Level Craft) and a later lesson. This question only cares about one thing: did this scene move a lever that the rest of the story now has to account for?
Scenes that pass this test — even quiet, uneventful-seeming ones — earn their place structurally. Scenes that fail it are candidates for cutting, compression, or a rewrite that gives them an actual job to do. Most manuscripts we assess have somewhere between three and six scenes in the first act that fail this test outright. Finding them is most of the work of a developmental pass.
Practical Exercise
Take any scene from a manuscript you're currently working on — ideally one you have a nagging feeling about. Answer these three questions in writing, as specifically as you can:
- What does a character know, want, or believe at the start of this scene?
- What is different about that knowledge, want, or belief by the end of the scene?
- Which other character, or which future scene, is now forced to react to that difference?
If you can't answer question 3 with something specific, you've found a scene worth reconsidering — not necessarily deleting, but interrogating. Sometimes a scene earns its place for texture, pacing, or character voice even without a structural change. That's a legitimate reason to keep it. What's not legitimate is keeping it by default, without ever asking the question.
Reflection Questions
- Which of your own scenes surprised you when you applied the diagnostic — either by passing when you expected it to fail, or the reverse?
- Is there a scene you've been reluctant to cut, even though you suspect it fails the test? What is it actually doing for you, if not structure?
- How would you explain the difference between “what happens” and “what changes” to another writer, in one sentence?
Completion
That's the full arc of Lesson One: a diagnostic question, applied honestly, is worth more than a shelf of style rules. Craft Specializations — including a full course on Structural Editing — will build directly on this lesson when they open.
Mark this lesson as complete for your own records.