Teaching Without a Tutorial: How Good Games Explain Themselves
The best game tutorials are invisible. We look at how level design teaches players to play, the introduce-test-combine-twist pattern, and when text prompts are fine.
Here is an uncomfortable truth: most players skip your tutorial. They mash through the text, ignore the tooltips, and start poking at buttons to see what happens. This is not laziness — it is how people learn games. They want to do, not read. The studios that understand this stop fighting it and start designing around it.
Why do players skip the tutorial?
A wall of instructions arrives before the player has any context for it. They do not yet know what an energy core is or why they would want one, so the explanation slides straight off. Worse, reading feels like the opposite of playing — and they came here to play.
The information is not wrong. It is just badly timed. Teaching someone the rules of a system before they have any reason to care about that system is the fastest way to be ignored.
Can a game teach without telling?
It can, and the best ones do it constantly. The trick is to let the space itself do the teaching, so the player discovers a rule rather than being lectured on it.
The classic example is the opening of the original Super Mario Bros. Within seconds, without a single word, you learn that you move right, that enemies hurt you, that jumping is your tool, and that the blocks above are worth hitting — because the level is arranged so that the most natural thing to do is also the thing that teaches you. The lesson is built into the architecture, not pasted on top of it.
The four-step teaching pattern
A reliable structure underpins a lot of great onboarding, and we lean on it heavily.
1. Introduce the new idea somewhere completely safe, where the player cannot fail.
2. Test it with a low-stakes challenge that requires actually using it.
3. Combine it with something the player already knows, so the two ideas reinforce each other.
4. Twist it — present the idea in a context that subverts their assumptions and proves they have understood it.
By the time players reach the twist, the mechanic is second nature and you never had to write “this is how this works.” They learned by doing, in the right order, at the right moment — which is the only kind of learning that actually sticks.
When is a text prompt actually fine?
Pragmatism matters here — purity for its own sake helps nobody. Some things genuinely are clearer as plain text: the control mappings, an accessibility setting, the name of a button on a specific controller. Trying to elegantly teach which physical button does what is often just friction dressed up as design.
So the rule we use is simple. Teach concepts through play, but do not be precious about stating facts. A quick on-screen prompt for the controls is a kindness. A paragraph explaining a mechanic the level could have taught is a missed opportunity.
What do we learn from watching first-timers?
Nothing humbles a designer faster than watching someone play their game for the first time with no help. The thing you thought was obvious? They walk straight past it. The button you were sure they would find? Untouched for ten minutes.
Those silent, confused moments are gold — they show you exactly where your game failed to explain itself. We watch a lot of first-timers, and we resist the urge to reach over and point. The fix is almost never to add a tooltip. It is to redesign the moment so the player teaches themselves, and then never notices that they were taught.