Narrative Design: Writing for Games as a Career
Narrative design gets confused with "being a good writer" constantly — but the actual job is closer to systems design that happens to use words, and understanding that distinction is the first real step into the field.
What the job actually involves: narrative designers write dialogue and story content, but they also design how story is *delivered* through gameplay — branching dialogue trees, environmental storytelling (a room that tells a story through what's placed in it, without a single word of dialogue), pacing story beats around gameplay moments, and working closely with level and system designers to ensure narrative and mechanics reinforce each other instead of working against each other.
Why pure writing skill alone isn't enough: a narrative designer needs to think in systems — how does a branching dialogue tree actually get built and tested without becoming unmanageable, how does player choice meaningfully affect outcomes without requiring infinite unique content, how does story pacing work around a player who might explore out of order. This systems-thinking layer is what separates narrative design from writing a novel or screenplay.
Step 1: Study how games actually deliver story, critically. Play games known for strong narrative design and actively analyze *how* the story is delivered — through dialogue, environment, mechanics, player choice — not just whether you enjoyed the story itself.
Step 2: Learn the tools of the trade. Dialogue and narrative scripting tools (Twine is a popular, accessible starting point for branching narrative), and basic familiarity with a game engine (Unity or Unreal) so you understand how narrative content actually gets implemented, not just written in a document.
**Step 3: Practice writing *for* interactivity, not just writing blog-content.** Write a short branching narrative piece — even a simple choose-your-own-path story in Twine — and focus specifically on how choices meaningfully diverge, not just on blog-content quality alone.
Step 4: Understand basic game design principles, even without specializing in them fully. A narrative designer who doesn't understand pacing, player agency, or basic system design struggles to write content that actually works within a game, rather than content that would work equally well as a short story.
Building a portfolio: include at least one interactive narrative piece (a Twine story, a small game with branching dialogue) alongside traditional writing samples — a portfolio of blog-content alone, without any demonstrated interactive or systems thinking, doesn't fully prove narrative design skill to a hiring team, since that's the specific skill the role is built on.
