Map a Scene Idea Into a Working Conflict
A scene without conflict is a description. The engine is three parts — what the character wants, what's in the way, and what it costs if they fail. This maps those three into a beat sheet, then offers three ways to twist the obstacle so the scene has somewhere to go. Local only; nothing leaves the tab.
- Mapping
- Goal → obstacle → stakes → turning point
- local
- What it replaces
- The 'add conflict' note with no mechanism
- $0.00
- Input
- Goal, obstacle, and stakes in three fields
- no card
- Output
- A beat sheet plus three twists
- recomputed
What you pay otherwise
| Route | What you get | Cost |
|---|---|---|
| Writing workshop | Scene feedback, in a class you have to join | $200+ |
| Story-plotting software | Structure tools, plus a subscription | $10+/mo |
| Deleting the scene | The idea abandoned for lack of an engine | lost |
| This page | Your conflict, mapped and twisted three ways | $0 |
The workflow
Name the want as a verb
'Wants to tell her boss' beats 'wants closure'. The goal has to be something the character can do in the scene — a verb, not a mood. If you can't verb it, the scene doesn't have an engine yet.
Make the obstacle a person or a rule, not a feeling
'The boss won't look up from his phone' is an obstacle; 'she's nervous' is a mood. The obstacle is the thing that pushes back, and the stronger it pushes, the more the scene moves.
Raise the stakes until failing actually costs
Stakes are the 'or else'. 'Or else she stays silent another year' is stakes; 'or else it's awkward' is not. If the stakes don't hurt, the scene can be cut — and the map tells you so.
Pick one twist and write the turning point
The three twists each move a different piece — the goal, the obstacle, or the stakes. Pick one, and the beat sheet's turning point is the moment the push-back forces a choice.
Worked example
Sample: a scene about asking for a raise Goal to make the ask before the meeting ends Obstacle the boss keeps redirecting to the budget Stakes another year at the same salary, or leaving Turning point she interrupts the redirect with a number Uploaded nothing — mapped in the tab
Numbers above are sample data produced by the tool's own pre-loaded example, run in the browser — not averages or measured benchmarks.
What breaks this
A goal that's a feeling ('wants to be understood') can't drive a scene — verb it. An obstacle that never pushes back makes the turning point flat; the obstacle has to win a round first. Stakes that don't hurt are the real tell: if the reader wouldn't care either way, the scene is a description, and no twist will fix that.
Try it now
A raise-scene conflict is loaded. Replace the goal, obstacle, and stakes with your own scene and re-map it.
Open the conflict map →Go deeper: the beat-sheet export
The conflict map is free forever. The $4 one-time tier adds:
- Beat-sheet export — the map and twists as a clean document — estimate: ~15 min saved versus retyping it.
- Saved scenes shelf — keep the maps for a whole draft — estimate: ~12 min saved per project.
- Twist log — track which twist you used and why — estimate: ~8 min saved.