If you’ve read Parts 1 and 2, you now have a vocabulary for the distinct structures that tend to get lumped together under “branching narrative.” This is the part where I tell you how I actually use that vocabulary — and why the most important conversation about narrative structure usually happens in a budget meeting, not a writers’ room.
What I Mean By a Collapsing Narrative
I want to be upfront about something: a Collapsing Narrative probably looks identical to a branch and bottleneck on a diagram. Draw them both out and I’m not sure you’d be able to tell the difference. So why bother with a new term?
Because I think bottleneck is doing real damage to how people build these structures.
When you call something a bottleneck — even internally, even just in your own head — you’re framing the convergence point as a constraint. Something the story has to squeeze through. And that framing tends to produce exactly what it sounds like: abrupt reconvergence, paths that snap together without ceremony, players who feel the rails lock back into place.
A Collapsing Narrative is the same shape with a different intent. The paths are designed to flow together, not to be forced through a hole. Think of a river delta running back into the ocean — each stream finds its own way there. The convergence is the destination, not the obstacle. You’re building toward it deliberately, and the player’s path should feel like the natural conclusion of the choices they made, even if someone who made completely different choices arrives at the same place.
Maybe that’s just good bottleneck design. Maybe the term is the only thing that’s actually different. But in my experience, what you call something in production affects how your team builds it — and I’d rather my team be thinking about rivers than bottlenecks.
Why This Is My Preferred Approach
I keep coming back to the Collapsing Narrative for a few reasons, and most of them are practical.
The first is the art cost argument, and it’s the one that almost never comes up in narrative design discussions because writers don’t usually run the art budget. But it should come up, because it shapes everything.
Writing is relatively cheap. A writer can produce branching dialogue, alternate scenes, and multiple path variations without dramatically multiplying the production cost. Voice over is more expensive but still manageable — you’re paying for studio time and actor time, which is real money but containable.
Art is a different story. Every environment, every animation, every cinematic sequence, every modeled asset that exists to express a moment in your narrative — those require concept artists, modelers, riggers, animators, technical artists, and significant time from each of them. Every project I’ve ever worked on has looked hard at reducing the overall runtime of cinematics. Even when you’re telling story through gameplay rather than cutscenes, you still need the art to make those moments land.
True branching doesn’t just mean writing twice as much. It means building twice as many environments, twice as many animation sets, twice as many fully realized sequences. And a lot of that content will only be seen by a fraction of your players.
A Collapsing Narrative lets you concentrate your art budget where it matters most — on the convergence points. The branches can be lighter, more dialogue-driven, more gameplay-focused. The moments where paths come together are where you spend the money on the sequence that makes everything feel earned. You’re not fragmenting your art resources across paths most players will never see. You’re investing them in the moments every player will experience, shaped by the path they took to get there.
This also makes it the right structural choice for small and mid-size teams. A small team simply cannot maintain multiple fully-realized visual branches without something suffering — usually quality, sometimes scope, sometimes both. A Collapsing Narrative lets a small team tell a rich, choice-driven story without spreading themselves thin across content that dilutes the experience rather than enriching it.
When It’s Not the Right Tool
The Collapsing Narrative is my preferred approach, not the only approach. There are situations where a different structure is clearly the better choice.
Live service games are the most obvious example. In a live service context, the Collapsing Narrative starts to work against you. You’re shipping content on a regular cadence — seasons, updates, episodes — and your player base is constantly in flux. New players are joining, lapsed players are returning, and nobody has the same save state or story context.
What live service narrative actually needs is closer to what television figured out a long time ago — the monster of the week model. Think X-Files or Buffy: standalone episodes that work on their own, anchored by a consistent world and cast of characters, with a longer arc threading underneath for the players who are paying close attention. That’s hub and spoke, and it’s almost perfectly suited to the format. Each update is a spoke. The hub is the persistent world and the relationships and lore that accumulate over time. The long arc gives invested players something to care about across seasons without requiring new players to have done homework before they can engage.
The gauntlet also has its place — and I want to be clear about that, because I don’t think it’s a lesser structure, just an honest one. If you’re building an action game where the narrative exists to contextualize the gameplay rather than drive it, a gauntlet is often exactly right. The story keeps moving, the player feels propelled forward, and the choices along the way that are dramatic in the moment but don’t alter the path give just enough sense of participation without demanding the production overhead of genuine divergence. The problem with the gauntlet isn’t that it exists — it’s when it gets pitched as something it isn’t.
Choose Before It Chooses For You
Here’s the thing that ties all three parts of this series together: your narrative structure is going to get chosen one way or another. The question is whether you choose it deliberately at the start, or whether it gets chosen for you by your deadline, your art budget, and the realities of production halfway through development.
When you choose deliberately and early, the structure can inform everything downstream — how you scope your writing, how you plan your art production, how you set player expectations, how you talk about the game publicly. You can build toward your convergence points intentionally. You can make sure your branches are the right length for your team to execute well. You can have an honest conversation about what kind of choices your players are actually going to experience.
When the structure gets discovered accidentally — and it happens more than anyone likes to admit — you end up retrofitting. Branches get collapsed abruptly because there wasn’t budget to finish them. Convergence points land badly because they weren’t designed to land, they were just where the money ran out. Players feel the rails snap back into place and they know, even if they can’t name it, that the choices they made didn’t really matter.
The vocabulary from Part 2 exists to help you have that deliberate conversation early. Bring the diagram to the kickoff meeting. Ask which structure you’re actually building. Get everyone in the room looking at the same picture before anyone writes a word or builds a single asset.
Because once production is underway, changing your narrative structure isn’t a writing problem. It’s a budget problem.