Branching design
Keep a cost ledger for your branching design
Evaluate each branch through state, performance, location, and audience-reach costs. Keep choices that change the experience and remove expensive paths without feedback.
Branches in interactive work are not free. Every additional path can add writing, performance, filming, editing, state testing, and costs associated with making produced content reach an audience.
Before designing options, keep a cost ledger. It brings you closer to a producible plan than pursuing a large branch count.
Four common costs
| Cost | Questions to check |
|---|---|
| State | Does this add a variable? How often will it be read? |
| Performance | Must an actor film an entire section again? |
| Location | Does this introduce a place or prop used only once? |
| Audience reach | Will enough players have a chance to see the branch? |
A high cost is not a reason to delete a branch. Ask whether it delivers equally important experiential value.
Distinguish path changes from state changes
A path change takes the player into different content, making its production cost obvious. A state change may reuse a scene while changing dialogue, attitudes, available options, or the interpretation of an ending.
Live-action interactive films can combine the two: a few important paths create structural differences, while more state changes provide personal feedback in reusable scenes.
Deciding whether a choice earns its place
Ask these questions in order:
- Does the player understand what they are judging?
- Do the options represent genuinely different intentions?
- Will the result be visible to the player or read later?
- Would removing this choice damage the core experience?
The fourth question is especially useful. A branch whose removal changes nothing is usually decorative interaction.
Build nodes that can converge
Convergence does not invalidate a choice. Two paths can return to the same location with different relationships, known information, and available resources. This controls location count while preserving consequences.
Avoid false convergence: every action receives the same response, and its state never matters again.
Branching design should not simply make the tree larger. It should make players increasingly certain that the story remembers what they did.