Before tutorials
The first commercial arcade games had no tutorials because they had no documentation medium accessible to the player. A cabinet could display instructions on a screen panel or a printed card, and most did — "Use joystick to aim. Fire button shoots. Avoid enemy fire." These were not tutorials in any meaningful sense. They described the controls. They could not convey strategy, demonstrate advanced techniques, or teach the game's deeper systems.
The solution that early game designers found was structural rather than documentary: make the first moments of the game demonstrably survivable while revealing the core mechanic immediately. Space Invaders's opening screen is a tutorial without announcing itself as one. The aliens move slowly. They are numerous but manageable. The player must discover that they can shoot (the fire button) and move (the joystick) under conditions that allow discovery without immediate death. The first wave teaches the controls. The second wave teaches escalation. The game has explained itself through play before the player consciously realises they have been learning.
The explicit tutorial and why it fails
As games became more complex through the 1980s and 1990s, the implicit teaching through structure became harder to sustain. Games with deep inventory systems, complex dialogue trees, multiple character statistics, and layered ability interactions couldn't communicate all their mechanics through the first few minutes of play. The explicit tutorial emerged as the solution: a dedicated section of the game that isolated individual mechanics and walked the player through them before the real game began.
Explicit tutorials have well-documented failure modes. Players who already understand the mechanic being demonstrated are bored. Players who don't understand the mechanic in the tutorial's context often don't understand why it's important and forget it before they need to apply it. The information is presented at the wrong time — before the player has experienced the context that makes the information meaningful. A tutorial that explains the dodge mechanic before the player has ever been in a situation that requires dodging teaches the button press but not the judgment about when to press it.
The tutorial skip option — widely implemented from the 2000s onward — acknowledges this problem but doesn't solve it. Players who skip tutorials and then don't understand a mechanic have no way to revisit the tutorial. Players who sit through tutorials they don't need have wasted time. The explicit tutorial is an inherently awkward solution to the teaching problem because it separates teaching from the context that makes teaching effective.
The integrated approach
The most acclaimed examples of game teaching in the post-arcade era share a common approach: mechanics are introduced in low-stakes contexts, demonstrated through the player's own experience rather than through instruction, and combined gradually as the player develops competence. Half-Life (1998) introduced its gravity gun in a scenario that made experimentation natural and low-risk, allowing players to discover the mechanic's properties through play rather than through instruction. Dark Souls (2011) used the player's deaths as learning opportunities — each death revealed information about an enemy's attack patterns, the range of a hazard, the stamina cost of specific actions. The tutorial was the experience of failing and learning from failure.
Nintendo's approach, developed through Miyamoto's insistence on watching uninstructed players and designing in response to their confusion, treated every element of a game's opening as a teaching opportunity. The coin in the first breakable block of Super Mario Bros. teaches that blocks contain items. The Goomba at the bottom of the first staircase teaches that touching enemies costs a life. The first mushroom, appearing from a brick the player is likely to hit while running, teaches that blocks can contain power-ups. Each lesson is taught through a single encounter, in sequence, under conditions that make survival likely and the lesson clear. The game never says "hit this block to discover what's inside." It makes hitting the block natural, and the discovery follows from the action.
The current state
Contemporary game design has developed a rich vocabulary for teaching without explicit tutorials: onboarding sequences that introduce mechanics sequentially in environments with limited threat, contextual tooltips that appear when a mechanic becomes relevant rather than before play begins, NPC characters who explain things in narrative-justified ways, and practice arenas where players can experiment without consequences. None of these approaches is universally successful, and all of them have failure modes.
The fundamental insight that makes the best game teaching work remains the one that arcade games demonstrated before anyone theorised it: people learn by doing, in contexts where doing is meaningful. A player who encounters a mechanic in a situation that requires it, fails because they didn't understand it, and tries again having seen the consequence of not understanding — that player learns the mechanic in a way that no textbox or tutorial video can replicate. The designer's job is to create the situation, ensure the consequence is instructive rather than merely punishing, and trust that the player will make the connection. When that trust is rewarded, the game feels like it's teaching you something real.