What narrative design actually involves

Storytelling in games has to accommodate a player who acts, which changes the craft fundamentally.

Branching and its cost

Every choice multiplying the content required.

Which is why branches usually reconverge.

Environmental storytelling

Narrative delivered through space and objects.

Which is efficient and specific to the medium.

Ludonarrative tension

Story and mechanics saying different things.

Which is a real design problem rather than a critical fashion.

Writing for systems

Text generated or assembled from parts.

Which requires a different kind of writing entirely.

Why branching is so expensive

Each meaningful choice doubles what has to be written, recorded, animated and tested, and choices compound.

Which is why games that advertise consequence usually funnel branches back together within a scene or two.

That is not deception so much as arithmetic: fully branching narrative is unaffordable at any commercial scale.

The illusion of choice

Techniques that make constrained options feel consequential.

Which is a legitimate craft and is resented when noticed.

Player character voice

Silent, defined or player-authored protagonists.

Which is a foundational decision affecting everything else.

Optional content

Narrative players may never see.

Which teams have to justify budgeting.

Collaboration

Writers working with level and systems designers throughout.

What the discipline is actually solving

How to tell a story to someone who will not necessarily do what the story needs them to do, in an order the writer did not choose.

Which is a structural problem that prose and film do not face.

Most of the craft consists of building narrative that survives player agency rather than fighting it.

Pacing in an interactive medium

Players spending unpredictable time between story beats.

Which is why games use triggers rather than timing.

Cutscenes and their cost

Expensive to produce and disliked when overused.

Which pushes narrative into gameplay where possible.

Systemic storytelling

Simulation producing events players narrativise themselves.

Collaboration with audio and art

Story carried by things other than words.

What distinguishes it as a discipline

Deciding how story is delivered, not only what the story is.

Which means choosing between cutscenes, dialogue, environment, systems and player action for every beat.

A narrative designer and a writer are related roles, and the first is closer to design than to writing.

Working with constraints

Budget for voice, animation and scene construction.

Which shapes what stories can be told at all.

Player-authored stories

Games where the memorable narrative was not written.

Which is a design achievement of a different kind.

Localisation implications

Writing that translates well.

Which is worth considering during drafting.

Reading in the field

Practitioners writing and speaking about the craft publicly.

A note on how this industry reports itself

Games is an unusually opaque business for one with such a visible product. Budgets are rarely disclosed, sales figures are announced selectively, player numbers are quoted in whichever metric flatters, and profitability is almost never stated at all.

Most of what is publicly known comes from court filings, leaked documents, regulatory submissions and former employees speaking after the fact. That material is reliable when it exists and covers a small fraction of the industry, which means any general claim about how games perform commercially rests on a limited and non-random sample.

Why the production side is worth understanding

A great deal of frustration with games comes from decisions that look inexplicable from outside and are entirely predictable once the structure is visible. Why a game shipped unfinished, why a beloved studio was closed after a successful release, why a sequel dropped features the previous game had, why a service shut down two years in.

None of these are mysteries. They are the outcomes of funding structures, platform economics, portfolio decisions and the fact that games are made by people working to schedules set before anyone knew what the game would be. Knowing that does not make the outcomes better; it does make them legible.

Where the better information is

Developer conference archives are the single best public source on how games are actually made, and a large number of talks are freely available. Regulatory filings during acquisitions have disclosed more real financial detail than a decade of press releases. Trade publications with named industry sources are considerably more informative than consumer coverage on business questions.

One thing worth remembering

Games are made by people, mostly people who care a great deal about them, working inside commercial structures they did not design and frequently cannot change.

Criticism of a game is fair. Criticism of the decisions behind it is usually aimed at the wrong floor of the building, and the people who take it are rarely the people who made them.