A game studio does more than produce code, art, levels, and documents. It produces shared memory. This article explores how institutional knowledge, team continuity, and the history behind thousands of small decisions shape coherent games - and why losing that memory changes a project long before players ever see the consequences.
A lot of modern games look immersive before they actually feel immersive. The lighting is expensive. The animations are polished. The worlds are huge. Characters blink, breathe, sweat, stumble, and stare dramatically into the middle distance. Everything looks like it should pull the player in, but somehow the experience can still feel strangely hollow. That is the problem with modern immersion...
A lot of games give players choices. The problem is that not all choices ask the player to think. Some choices are simply buttons attached to pre-designed outcomes. Press this to distract. Press that to persuade. Select this option to set a trap. Choose this dialogue line to resolve the scene. These interactions can be useful, readable, and satisfying, but they are not the same as letting the player construct an outcome through the world. This is the difference between activation and construction. Activation is when the player triggers a designed outcome. Construction is when the player builds an outcome through interacting systems. Both can look like agency from the outside because both involve player input, but the player’s relationship to the result is completely different. One asks the player to select a solution. The other asks the player to understand the world well enough to create one...
Most games tell players who they are. You are a detective, a soldier, a thief, a hunter, a wizard, or a survivor. The problem is that being told something and feeling something are not the same thing. A game can spend hours explaining who your character is through dialogue, cutscenes, lore entries, and exposition, but if the player’s behaviour never changes, the fantasy remains superficial. They are controlling the character, not inhabiting them...
One of the biggest myths in game design is that player freedom automatically creates immersion. It doesn't. Freedom only matters when players understand what they can actually do with it. This is where many systemic games fail. Designers spend months building interconnected mechanics, emergent interactions, and multiple solution paths. The systems are there. The depth is there. The possibilities are there. The player never sees them. Instead, they walk into a space, identify the most obvious solution, and move on. Not because they don't want to experiment, but because the game never taught them how to recognise opportunity. This is what the Simulation Compass solves...
Most games want players to feel like their choices matter, immersing them in a world where every decision has weight and significance. The problem is that many of those choices don't actually change anything meaningful within the game. You pick dialogue option A or dialogue option B, often leading to interactions that feel strikingly similar despite the initial differences in choice. You choose one path over another, venturing into distinct story arcs that ultimately converge at the same destination. You spend resources one way instead of another, believing that your strategy will yield varied outcomes. Yet somehow, the game quietly bends itself back into the same shape, leaving players questioning the impact of their decisions...
