Here's something I've come to believe after years of playing and building games: most game stories are mediocre, and that's okay. Not every game needs a good story. Tetris doesn't have one and nobody cares. But when a game tries to tell a story and fails, the failure is more damaging than if it had never tried at all. The player feels misled. They invested hours expecting narrative payoff and got a cutscene that could have been a loading screen.
The problem, I think, isn't primarily bad writing. There are plenty of game writers who could write compelling fiction or screenplays. The problem is structural. In most games, the story and the gameplay are two separate things that get bolted together, and the bolts show.
The Cutscene Problem Nobody Talks About
Think about the last story-heavy game you played. Chances are the narrative was delivered through cutscenes — video sequences where the characters talk, emote, and advance the plot while you watch. Then the cutscene ends and you're back in gameplay mode, running around and shooting or jumping or whatever the game asks you to do.
This creates a weird dissonance. The cutscene tells you the world is dangerous, your character is desperate, time is running out. Then gameplay drops you into an open area with 47 side quests to complete at your leisure. The story says "urgency" but the gameplay says "take your time, there's a fishing minigame over here."
I remember playing through a well-known action RPG — I won't name it, but you probably know which one — where a cutscene showed my character mourning a dead ally. Sad music, rain, the whole thing. Then the cutscene ended and I immediately did a celebratory dance emote because the button was right there. The game didn't care. The story layer and the gameplay layer didn't communicate.
This isn't a new observation. Game designers have discussed ludonarrative dissonance since at least 2007, when Clint Hocking coined the term in reference to BioShock. But knowing about a problem and solving it are very different things, and most studios still ship games with the same structural gap.
What the Good Ones Do Differently
The games that get narrative right share a common trait: they don't separate story from play. The story emerges from what you do, not from what you're told between doing things.
Mechanics as metaphor
Take Brothers: A Tale of Two Sons, directed by Josef Fares. The game has you controlling two brothers simultaneously — one with each analog stick. The older brother swims, carries, and protects. The younger brother can't swim and depends on his older sibling. This isn't explained through dialogue. It's expressed through the controller. When the story requires the younger brother to swim alone near the end, the player physically feels the absence on the stick that used to control the older brother.
That moment works because the narrative isn't layered on top of the mechanic — the mechanic IS the narrative. You don't watch a cutscene about loss; you experience a mechanical absence that produces the feeling of loss in your hands.
Fares discussed this approach in several talks, including his presentation at GDC 2014, where he described the intentional mapping between controller input and emotional experience. Whether you agree with all his conclusions, the method is instructive.
Consequence systems that actually bite
Another approach: games where your choices have consequences that you can't undo or predict. Most "choice-driven" games fail at this because the consequences are cosmetic. You pick dialogue option A or B, and the game shows a slightly different cutscene, then converges back to the same plot point. Players catch on quickly. They learn that their choices don't matter, and once they learn that, the narrative tension evaporates.
The games that work are the ones where choices genuinely close doors. This War of Mine, by 11 bit studios, forces you into resource decisions where every option has a cost. Stealing medicine from an elderly couple keeps your people alive but changes how your characters behave afterward. Not through a morality meter — through visible, mechanical changes in what those characters can do. The story isn't a branching dialogue tree. It's a web of systemic consequences that your actions create.
11 bit studios published a detailed post-mortem on their development process that's worth reading if you're interested in how they structured those systems. The UN's documentation on civilian experiences in conflict also informed their research approach, which they've discussed in interviews.
Environmental storytelling that trusts the player
Then there's environmental narrative — games that tell stories through the space you move through rather than through dialogue or text. What Remains of Edith Finch, by Giant Sparrow, is a strong example. Each room in the Finch house tells the story of a family member through its physical arrangement: the objects on shelves, the height of the furniture, the way light comes through windows. The game never stops to explain. It trusts you to piece things together.
This works because humans are natural pattern-seekers. We look at a child's room and see the crayon drawings, the nightlight, the bed that's too big for the small body that slept in it. We don't need a text box saying "a child lived here." The environment communicates faster and more viscerally than prose.
| Technique | Story-game integration | Player agency | Production cost |
|---|---|---|---|
| Cutscene-driven | Low (separate layers) | Passive during story | High (animation, voice) |
| Branching dialogue | Medium | Choice within scenes | Medium (writing volume) |
| Mechanical narrative | High (gameplay = story) | Continuous | Varies (design-intensive) |
| Environmental | High (space = story) | Exploration-driven | Medium (art + level design) |
| Systemic consequence | High (systems = story) | Long-term impact | High (system complexity) |
Why This Is Harder Than It Sounds
If integrating narrative and gameplay is so clearly better, why don't more games do it? Because it's genuinely difficult, and the difficulty isn't just technical — it's organizational.
In most studios, writers and designers work in separate silos. The writers produce scripts, dialogue, and lore. The designers build mechanics and systems. The two teams coordinate through documents and meetings, but they're fundamentally working on different things. The writer doesn't have access to the mechanic being prototyped. The designer doesn't read the narrative design doc in detail. The integration happens late, under deadline pressure, and it shows.
Small teams have a structural advantage here, which is one reason indie games often punch above their weight on narrative. When the writer and the designer are the same person — or two people sitting next to each other — integration happens naturally. You don't need a document to coordinate between your own brain. At SkyLine Corp, this is something we've thought about a lot, and it's part of why we stay small. The coordination cost of a larger team would force us back into the silo model that produces the problems we're trying to avoid.
There's also the uncomfortable reality that integrated narrative design means more iteration. If your story lives in the mechanics, then every time you change a mechanic — which happens constantly during development — you're also changing the story. This makes the process slower and less predictable, which is a hard sell to anyone managing a budget or a release schedule.
A Practical Starting Point
If you're building a game and want to improve the relationship between your story and your gameplay, here's where I'd start:
- Identify your game's core emotion. What should the player feel at the most important moment? Not what should happen in the plot — what should the player feel?
- Map that emotion to a mechanic. Is there a gameplay system that already produces something close to that feeling? Can you modify one to get closer?
- Remove any narrative element that contradicts your gameplay. If your mechanics say "you're powerful" but your story says "you're helpless," one of them has to change. Usually it should be the story.
- Playtest for emotional response, not just comprehension. Don't just ask testers if they understood the story. Ask them how they felt during specific moments. If the answer doesn't match your intent, the integration isn't working yet.
This isn't a formula. It won't guarantee a good story. But it's a way of thinking about narrative that starts from the gameplay rather than bolting onto it after the fact, and in my experience that shift in starting point makes a bigger difference than any specific writing technique.
For a broader look at how interactive narratives work across media, the Library of Congress has archived research on digital storytelling that provides useful historical context. And if you want to see how other developers are wrestling with these questions, the r/gamedesign community has honest, ongoing discussions that go deeper than most conference talks.
The honest truth is that most games will never achieve the level of narrative-gameplay integration that titles like Brothers or Edith Finch reached. Those games are exceptional for a reason. But even moving a small distance in that direction — making your story a little more connected to what the player actually does rather than what they watch — produces a noticeably better experience. The gap between "game with a story" and "story that is a game" is smaller than most developers think. It just requires starting from a different place.