Nobody Reads the Tutorial. Miyamoto Deleted It in 1985.
July 9, 2026 · Casey Brooks, A Theory of Fun for Game Design~8 min read
Third playtester in a row, same couch, same game: tutorial popup appears, thumb hits A before the first sentence loads. Skip. Skip. Skip. Then they get to the actual level and stall at the first mechanic the popup just "explained." I've watched this scene maybe a hundred times, and every time I think about the same thing: a plumber from 1985. Super Mario Bros. shipped in a cartridge too small for even one line of instructions — and nobody who picked it up ever got lost. That's not luck. Shigeru Miyamoto designed the level itself to be the tutorial, and in a 2015 Eurogamer interview with Takashi Tezuka, he walked through exactly how. The rule underneath it fits on one line: every element in your starting area must teach the player one thing.
30-second read
Text tutorials fail because reading isn't doing. Miyamoto's answer in 1985: delete the tutorial and make World 1-1 teach through play — the approach Nintendo later summed up as "learning through play."
The opening screens of 1-1 are a precision chain: the Goomba teaches "enemies die," the ? blocks teach "hit blocks, get rewards," the mushroom teaches "this world rewards courage," and four rising pipes silently teach "hold the button to jump higher."
One idea gets used four times — a place to learn it, use it, apply it, master it. That's Miyamoto's teaching arc for every mechanic.
The audit is brutal and simple: for every element in your first level, finish the sentence "→ this teaches ___." Can't finish it? Cut the element.
1The problem
Reading a rule and learning a rule are different organs
Every game faces the same contradiction: players must learn your rules, and players will not read your rules.
Here's the tell: watch anyone open a mobile game with a lovingly written popup tutorial. The eyes don't track the text. The thumb finds the dismiss button by muscle memory. Whatever your onboarding doc says, the observed behavior is skip, skip, stall. Text explains; it doesn't teach. There's a layer of glass between reading "press and hold to jump higher" and your hands knowing it.
Miyamoto had a harder version of this problem and a smaller budget for it. In 1985 there was no such genre convention as a "tutorial," and the cartridge couldn't spare bytes for instructions anyway. His answer wasn't a cleverer popup. It was: the level is the tutorial. Nintendo has run on that philosophy ever since.
⚡
Why this matters beyond Mario: Raph Koster's A Theory of Fun for Game Design argues that fun is learning — the good feeling in a game is your brain enjoying a pattern being mastered. If fun is learning, then teaching isn't a chore before the game. Teaching is the game.
Popup tutorial
Explains the rule in text. Player skips, then stalls at the first real use. The knowledge lives in a paragraph nobody read.
Level as tutorial
The layout forces the discovery. Player acts, sees the consequence, owns the rule. Someone watching over their shoulder understands the game too.
2The case
The first screens of 1-1 are a psychological chain, not a level
In the Eurogamer interview, Miyamoto walks the opening placements one by one. The trick isn't that each is well-made — it's that each reaction sets up the next element.
First, one Goomba. Slow, alone, walking straight at you. Your gut says dodge, you panic-jump, and — because its speed was tuned for exactly this — you land on it, and it dies. In three seconds you've learned: enemies exist, touching them is bad, jumping dodges them and kills them.
Then the ? blocks. A box with a question mark begs to be hit. A coin pops out with that chime and a score tick. You're happy, so you hit the next one. That habit is the setup: the third block releases a mushroom. You just learned mushroom-shaped things are enemies, so you try to dodge — but the brick row overhead blocks your escape jump. The collision is forced by geometry. You brace for damage, and instead you grow twice the size.
The pivot
The best thing happens at the worst moment. "You hit it and you get bigger — players are delighted," Miyamoto says of that mushroom. "They go off hitting bricks and blocks, and by then they basically understand the game." Fear of new things flips into wanting to try things. That single reversal converts a defensive new player into an explorer.
The opening of World 1-1 as a teaching chain (top) and Miyamoto's four-stage arc for any single idea (bottom): a place to learn it, use it, apply it, master it. Diagram is a schematic reconstruction from the interviews, not screen-accurate. Sources: Miyamoto × Tezuka, Eurogamer (2015); the "one idea, four uses" line as cited in Hiroshi Yoshida's University of Tokyo game-studies primer. Framing: Raph Koster, A Theory of Fun for Game Design — fun is the brain enjoying learning.
And the pipes. Four of them, each taller than the last. The short one you clear on a tap. The tall one won't clear until you hold the button longer. No text ever says "jump height is pressure-sensitive." The geometry says it, and your thumb learns it. That's a parameter tutorial with zero words.
Element
Player's reaction
→ Teaches
Goomba
Panic jump lands on it (speed tuned for this)
Enemies die; touch hurts; jump dodges and kills
? blocks
Hit it → coin, chime, points → hit the next
Blocks reward; repeat the motion (sets up the mushroom)
Mushroom
Tries to dodge; ceiling forces the hit; grows big
Power-ups exist; this world rewards courage
Rising pipes
Short ones clear easily; tall ones demand a longer press
Hold the button, jump higher — wordless parameter teaching
3The arc
One idea, four appearances: learn, use, apply, master
The rule says every element teaches one thing. Miyamoto's fuller skeleton says each idea then needs four appearances.
As cited in Hiroshi Yoshida's University of Tokyo game-studies primer, Miyamoto puts it roughly like this: when you build an idea, there must be a place to learn it, a place to actually use it, a place to apply it, and a place to master it — so one idea gets used four times. First meeting: zero risk, failure costs nothing. Second: light risk, you must genuinely use it to progress. Third: it combines with something you already know and produces an "oh, it also works like this" jump. Fourth: an optional expert test — hidden route, high-score trick — for players who want depth.
Look at 1-1's pits with that lens: the early pits have floors — fall in and you climb out, no death, no restart. Later pits widen and grow obstacles. Even the punishment has a designed slope.
Put it Koster's way
In A Theory of Fun for Game Design, boredom is what happens when the brain runs out of new patterns to chew on, and fun is the chewing. The four-stage arc is a feeding schedule: each appearance of the idea hands the brain the same pattern at a new depth, so mastery keeps tasting like play instead of homework.
4The proof
The over-the-shoulder gaze: you are not your player, so stop guessing
The rule assumes you know what each element teaches. How do you know the player actually learned it?
Not a survey. Satoru Iwata described Miyamoto's method in Ask Iwata: grab someone who knows nothing about the game, hand them the controller, say "here, try it" — then say absolutely nothing and watch from behind. Iwata called it Miyamoto's "over-the-shoulder gaze." The silence is the instrument. The moment you explain, you've contaminated the experiment. What you're measuring is exactly where they stall with no outside help — and every stall point is a spot where your teaching layout failed.
I run playtests for a living and this is still the whole job. Not the analytics dashboard. A stranger, a controller, and you keeping your mouth shut. The player will tell you — with their thumbs, not their mouth.
5Your move
What this means for whatever you're building
You don't need to ship a platformer for this to bite. Anything with a first-hour applies.
Run the audit. List every element in your starting area — every enemy, item, button, screen. For each one, finish the sentence "→ this teaches ___." Can't finish it? Cut it, or move it past the opening. Then check the order: does each element's reaction set up the next one, like the block-habit delivering the mushroom? Then give your core mechanic its four appearances — learn, use, apply, master — and check which stage is missing. Finally, grab someone who's never seen it, hand it over, shut up, and write down where they stall. Fix the layout at the stall point. Adding a text hint there is bandaging a level that failed — text is the last resort, not the first.
Honest edges: the 1-1 walkthrough follows the designers' own retrospective interviews, thirty years after the fact; direct-style quotes are paraphrased, not verbatim; the diagram is a schematic, not screen-accurate. "Fun = learning" is Koster's framing of play, not a claim that all fun reduces to tutorials. And "apply" means a new use, not just more enemies — difficulty is not depth.
Sources: Shigeru Miyamoto × Takashi Tezuka, Eurogamer interview on the making of Super Mario Bros. (2015); the "one idea, four uses" structure as cited in Hiroshi Yoshida's University of Tokyo game-studies primer; Satoru Iwata on the "over-the-shoulder gaze" in Ask Iwata; Iwata Asks: New Super Mario Bros. Wii. Framing from Raph Koster, A Theory of Fun for Game Design (fun as the brain enjoying learning). Quotes are minimal paraphrased excerpts; the level diagram is a schematic reconstruction. This is a design read, not a Nintendo-endorsed document.