How to set a scene goal — and why it changes everything
A scene goal isn't a plot summary. It's a compass. Writers who learn to write one before every scene — even a rough one — draft faster, revise less, and cut fewer words they loved but couldn't keep.
What is a scene goal, exactly?
A scene goal is a single sentence that answers the question: what does this scene exist to do?
Not what happens in it. Not who's in it. Not where it's set. What it does — its function in the story at this particular moment.
This is a subtle but important distinction. "Elena confronts her father about the missing letter" describes what happens. "Establish that Elena's relationship with her father is built on careful silence, not trust" describes what the scene does. The first is a plot summary. The second is a goal.
You can write a scene without a goal. Most first drafts are full of scenes written without one. The problem shows up in revision — scenes that feel purposeless, chapters that drag, whole sections that could be cut without losing anything. In almost every case, a missing scene goal is somewhere in the diagnosis.
Weak scene goals vs. strong ones
Not all scene goals are equal. Weak goals are vague, plot-focused, or describe a single function when good scenes do two or three things simultaneously.
- Elena and her father argue
- Introduce the village elder
- Marcus finds the key
- Show that winter has arrived
- Show that Elena's silence with her father is a learned survival skill, not indifference — and crack it for the first time
- Establish the elder as someone whose authority depends on others not asking questions
- Let Marcus find the key — but make the reader understand he doesn't know what it opens
- Use the first frost to show how differently Elena and Cora relate to the passage of time
Notice that the strong goals are longer. That's fine — a scene goal isn't a headline, it's a working note to yourself. It should be specific enough that when you finish drafting the scene, you can honestly assess whether you achieved it.
Notice also that the strong goals often contain a tension or a complication. "Marcus finds the key — but doesn't know what it opens" sets up a scene that can do two things: give the reader information and withhold it simultaneously. That's interesting. "Marcus finds the key" is just an event.
A simple formula to get started
If you're new to writing scene goals, this formula will get you unstuck:
"In this scene, [character] will [attempt / discover / confront / reveal], which will [change / complicate / deepen / establish] [relationship / belief / situation / reader's understanding]."
You don't have to use these exact words. The structure is what matters — action plus consequence. Something happens, and it matters in a specific way.
"In this scene, Cora will attempt to convince the council to delay the vote, which will reveal that two members she trusted have already been bought."
This goal tells you what Cora wants, what she does, and what the scene delivers to the reader that Cora doesn't get. The tension between Cora's attempt and the scene's actual outcome is built into the goal itself.
The three outcomes every scene goal should consider
A scene goal isn't just about what you intend to write. It should also tell you how the scene ends — specifically, which of three outcomes the character's attempt meets.
- Yes — the character achieves their goal. This should be rare in Act Two, and always cost something.
- No — the character fails. The most common outcome, and the engine of most plot momentum.
- Yes, but — the character succeeds, but a new complication arrives with the success. Often the most interesting outcome of the three.
When you're writing your scene goal, sketching which outcome you're aiming for focuses your drafting considerably. A scene heading toward "yes, but" is written differently than one heading toward "no." The character's internal experience, the pacing, the ending beat — all of it shifts depending on which outcome you're building toward.
One of the most common revision problems is a scene that ends on "yes" when it should end on "no, but" — or worse, a scene that doesn't clearly land on any outcome at all. When you have the outcome written in your goal, you can check the scene's ending against it in thirty seconds. Did you actually write what you intended? If not, is the deviation intentional or accidental?
What if you write without a goal first?
Many discovery writers — pantsers — won't write a scene goal before drafting. That's fine. The goal doesn't have to come first. It just has to exist somewhere.
The retroactive approach: after you've drafted a scene, write the goal for what you actually wrote. "What did this scene turn out to be doing?" Then ask whether that's what you needed from it at this point in the story.
This is often how pantsers find their structural problems in revision. They map their actual scenes against the story's needs, scene by scene, and identify the gaps — the scenes that are doing something redundant, the scenes that are doing nothing at all, and the scenes that are doing two things when one would be stronger.
"I wrote this scene as Mira arriving at the market and noticing the new vendor. What it actually did: established that Mira notices people others overlook. That's character work — good. But I'm in Chapter 9 and I've already established this three times. This scene might be a cut."
The retroactive goal made the problem visible. Without it, this scene might have survived three more drafts.
Three ways to start using scene goals today
- Before your next scene, write one sentence. Don't overthink it. "In this scene, X will attempt Y, and Z will result." Even a rough goal is better than none. You can revise the goal if the scene takes you somewhere unexpected — the point is to start with intention.
- Audit your last three scenes retroactively. Read each one and write one sentence describing what it actually does. Then ask: does the story need that, at this point? Is it being done better elsewhere?
- Check your outcomes. Go through your scene goals and note whether each one ends on yes, no, or yes/no-but. If you have five consecutive "yes" outcomes in Act Two, that's worth examining. Stories that keep handing characters what they want tend to lose tension quietly.
The scene planner has a goal field for every scene card. Write your goal there before drafting — or retroactively after. When you run an analysis on that chapter, WolfScribed cross-references your stated goal against what the prose actually delivers, flagging gaps between intention and execution.
Set a scene goal
Define the goal, stakes, and opening of a scene you're working on — then write its first 200 words with that intention locked in.
Try this challenge →Up next in this series
How to plan your story (plotters, pantsers, and everyone between)
Two legitimate ways to approach a novel — and how to find the method that actually fits the way you think.
Try it in WolfScribed
Open a project and use the Scene Planner to put these ideas into practice.