Every narrative designer I’ve met has, at some point, opened their branching diagram, zoomed out, and felt the specific vertigo of a person who has built 400 doors and no house. Fourteen endings. Sixty flags. A romance path that somehow softlocks if the player was rude to a fisherman in act one. And underneath it all, a nagging question nobody on the team wants to say out loud: what is this story actually about?
Here’s the load-bearing secret of interactive writing: branching is not a replacement for structure. It’s structure asked to do pushups. The more choices you offer, the stronger your spine has to be — because every branch is a promise that the story still means something over there.
The spine comes first (yes, even in your genre)
Before the flowchart, answer like a novelist: who wants what, what’s in the way, what does it cost. Your player can choose the route. They should never be able to choose their way out of the story mattering. The Witcher didn’t move people because it had endings — it moved people because every ending was still about the same wound.
What actually needs to branch
| Element | Branch it? | Why |
|---|---|---|
| The theme / central wound | Never | This is the house. Doors go in the house. |
| The load-bearing beats (7 or so) | No — re-flavor, don’t remove | Every route should hit them; the how is where choice lives. |
| Relationships & tone | Yes, generously | Cheap to build, rich to feel. Players remember who was cold to them forever. |
| Endings | Yes — but as verdicts, not variety | Each ending should answer the central question differently, not just recolor the credits. |
The pruning pass
- Collapse false choices. If two branches reconverge in ninety seconds with no scar, make it one branch with a line of reactive dialogue. Players feel remembered, you save a month.
- Give every major branch a scar. A choice that changes nothing later isn’t a choice; it’s a doorbell.
- Test routes like drafts. Play the critical path as if it’s the only story. If it sags, no amount of optional content saves it — side doors can’t fix a broken hallway.
- Kill your fifteenth ending. Four endings players argue about beat fourteen they shrug at.
Players don’t fall in love with your flowchart. They fall in love with the one hallway you built strong enough to hold every door.
The dare
Write your game’s story in three sentences with zero branches — just the spine. If you can’t, the flowchart isn’t complexity. It’s avoidance with nodes. Find the spine first, then reopen the doors.
Blueprints available: the audiobook “The Seven Load-Bearing Beats You Probably Skipped,” “The Plot Architecture Planner,” and the 4-week “Build The Damn Plot” cohort — bring the flowchart, we’ll bring the chainsaw.
