Why Tim Cain thinks “less” actually wins
Tim Cain — one of the brains behind Fallout and a veteran with decades in the industry — says the real trap in game design isn’t flashy tech or big budgets, it’s a lack of purpose. After you build the world, write the story, and set up systems, you’ve still got to know what all of it is for. If a game doesn’t have a clear chain of goals or a reason for the player to care, all that content just becomes noise.
Cain has been designing and programming RPGs for over 40 years, has worked on classics like Vampire: The Masquerade – Bloodlines, Pillars of Eternity and the original The Outer Worlds, and now sits back at Obsidian. He also runs a popular YouTube channel about RPG design, where he breaks this stuff down into plain English for other devs and curious players.
Design potholes (and why you should care)
He calls the common mistakes “design potholes” — little problems that can wreck a game if you hit them at the wrong speed. Examples: stuffing a story full of every genre trope possible, or plopping in popular mechanics like base-building or survival just because they’re trending. Those choices can turn a focused game into a scattershot mess unless they exist for a specific reason.
Another pet peeve: vague design notes that say things like “and then the player does something.” Cain argues you need to design around player-driven outcomes — what happens if the player does X, and why would they want to? Locking someone in a room until they perform a forced action is a lazy shortcut, not design.
He also warns against trying to predict player emotions in design docs. Instead of writing “this will make the player feel [X],” a useful document should describe the visible bits: what will be shown, NPC dialogue, available actions, music, and other concrete elements that teams can actually build and test.
For players, this philosophy matters because it stops developers from slapping on mechanics or story beats that don’t belong. The result: tighter pacing, more meaningful choices, fewer half-finished features, and a game that actually knows what it’s trying to be.
Bottom line? If you’re making a game, ask “why” at every step. If you’re buying one, favor games that clearly know their purpose — fewer distractions, more punch.
