Case Study 1: Super Mario Bros. and the Invention of Level Design

The single most studied minute in video game history is World 1-1 of Super Mario Bros. (Nintendo, 1985). Designers have been writing about it for forty years. GDC talks have dissected it frame by frame. Miyamoto himself has described, in various interviews, the thinking behind its layout. There is a reason this tiny level — about fifteen seconds of gameplay, maybe forty-five if you die and replay a few times — is the reference point for how to teach a player to play a game without saying a word.

The reason is that World 1-1 does, in under a minute of play, what most modern AAA games take a thirty-minute tutorial to accomplish badly. It teaches Mario's entire core vocabulary — run, jump, stomp, power-up, pipe-as-doorway, flagpole-as-goal — through pure environmental arrangement. There is no text. There is no voice. There is no tutorial NPC. There is no prompt icon. The level is the teacher, and the player is the student, and the curriculum is encoded in where the designer placed the first Goomba.

This case study is the close reading.

The Opening Frame: Right Is Forward

The first thing the player sees when World 1-1 begins is Mario, small, in the lower-left of the screen. The screen is mostly empty. There is a lot of sky on the right, some hills in the background, and — critically — no obstacles to the left.

This is design. The leftmost position of Mario is telling the player: forward is right. The Japanese reading convention is right-to-left; the Western convention is left-to-right. Miyamoto chose left-to-right because he was already thinking about international audiences and because the momentum physics of Mario's jump look better when he moves rightward across the screen. The camera is locked — you cannot scroll left. The game is telling you the direction of progress before you have pressed a button.

You press right. Mario moves. This is the first lesson: right on the D-pad moves Mario forward. It has been taught in under a second, and the player has internalized it through their own input. They did the thing, the thing happened, they learned.

The First Goomba: Threat and Jump

A short distance in, the first Goomba appears. It walks toward Mario. The player, being human, will not stand still and let the Goomba walk into them. They will do one of three things: stop, run backward (but they cannot — no leftward scrolling), or jump.

The designer knows that most players will try to jump. The jump button has been discovered by experimentation or by intuition (the controller has an A button and a B button; one of them does something). The player presses A. Mario jumps. The player's jump arcs over the Goomba — or lands on it, killing it. Either way, the player has now learned the jump button exists and it clears enemies.

Notice what the designer has done. The first enemy appears exactly where the first jump is naturally motivated. The player does not have to be told to jump. The player wants to jump. The level design has manufactured the desire, then made the desire teach a lesson.

There is a variation here that the chapter should mention. If the player does nothing — does not press jump, does not move — the Goomba walks into Mario. Mario dies. Mario respawns. The player has now learned that enemies are dangerous and that standing still is not a strategy. Even the death case is pedagogical. The level teaches even when you fail it.

The Question Block: Power-Up as Reward

Just past the first Goomba, there is a row of blocks with the question-mark indicator on one of them. The blocks hang in the air at a height that is clearly reachable by jumping. The player, now comfortable with jumping, will try jumping into the question block.

A mushroom pops out.

The mushroom is the first power-up and it is the gentlest possible introduction to the power-up system. It appears, it moves in a straight line across the ground, and if the player catches it, Mario grows. The player, still in the left part of the screen, has time to react. The mushroom's pace is slower than Mario's running speed, so intercepting it is easy even for a player who has never seen it before.

But Miyamoto does not trust all players to understand that the mushroom is good. There is a subtler teaching moment. Mushrooms in real life are sometimes poisonous — a player with no context might think this glowing thing is an enemy and try to avoid it. Miyamoto handles this by making the mushroom bounce off a pipe and return toward Mario, forcing the player into collision unless they deliberately jump over it. If the player jumps and misses, the mushroom goes off the screen and is gone. If the player lets the mushroom touch them, Mario grows, and the player learns: this thing made me bigger; bigger is good.

Big Mario can now break bricks with his head. The player will discover this next.

The Brick Wall: Implicit Instruction

After the question block sequence, there is a patch of ordinary bricks. A new player will assume bricks are walls, because bricks are walls in most games and in most real life. But if the player is Big Mario, jumping into a brick breaks the brick.

This is taught by accident — the player jumps for some other reason (a second Goomba, another question block), hits a brick with their head, the brick breaks, pieces fly away. The player sees it. They file it away. Later, when they need to break a brick to reach a hidden space, they remember.

This is the invisible-teaching pattern at its clearest. The game did not announce "bricks break when Big Mario jumps into them." The game let the player discover it incidentally, through an action they took for another reason. The lesson is stronger because the player discovered it — they own the lesson in a way they would not if they had been told.

The Pit: Death and Caution

Some distance in, there is the first pit. The camera scrolls rightward and reveals a gap in the ground. The ground ends. If Mario walks off the edge, he falls into the pit and dies.

The pit is the first teaching moment that threatens the player without the hint of a friendly introduction. Unlike the Goomba, which gives you time to react because it walks toward you, the pit gives you nothing. You are the one who has to stop or jump.

The player either makes it across or dies. If they die, they respawn at the start of 1-1, and they have learned gaps are fatal; look before you leap. This lesson is now permanent for the rest of the game. They will approach every subsequent gap with appropriate caution.

The pit is also the first time the game asks the player to use a longer jump — the gap is wider than any previous jumping requirement. The player learns that holding the jump button longer makes Mario jump higher and farther. They learn this because the pit forces them to experiment.

The Pipe: A Door

After the pit, Mario encounters a green pipe sticking up from the ground. It is short — jumpable. The player jumps on top of it. Nothing happens except that they are standing on a pipe now.

The pipe is a doorway, but the game does not say so. The player learns this in a subsequent level (World 1-2, traditionally) where pressing down on a pipe causes Mario to descend into a bonus area. By the time the player has seen two or three pipes, they have hypothesized — without being told — that pipes are doorways, and testing the hypothesis reinforces it.

World 1-1 also contains a hidden block that reveals itself only when Big Mario jumps in a specific empty-looking spot. Most first-time players miss it. That is fine. The hidden block is not required content; it is a reward for the curious player who experiments. The game is layered: the beginner completes the level in forty-five seconds; the explorer finds the hidden block and the warp pipe and spends longer.

The Flagpole: The Goal

At the end of the level, the screen scrolls to reveal a flagpole. There is no instruction. The player, having played some arcade games perhaps, understands that reaching the rightmost point is the goal. They jump to the flagpole. Mario slides down. A flag waves. Music plays.

The player has finished their first level. They have learned Mario's entire vocabulary — movement, jumping, stomping, power-up acquisition, brick-breaking, gap-crossing, pipe-as-platform, flag-as-goal — in about a minute. They have learned all of this through doing, not through being told.

Miyamoto's Methodology

The design-history twist that deserves emphasis: Miyamoto and his team explicitly designed World 1-1 last. They built the rest of the game first, determined what the player would need to know to play it, and then reverse-engineered a tutorial level that would teach those skills without saying so.

This is the opposite of the usual design approach, which is to start at the beginning and build out. Miyamoto started at the question "what does the player need to know by the end of this level?" and then designed the level to answer that question through pure environmental arrangement.

This methodology is not unique to Miyamoto; many of the best tutorial levels in games are built last, after the rest of the game is playable enough to identify which skills the player must have internalized. But Miyamoto articulated the practice, and his articulation has influenced every subsequent designer who thinks about teaching through play. Portal's first few chambers (designed by Kim Swift and her team, who were explicitly influenced by 1-1) use the same reverse-engineered approach: build the puzzles first, then build the tutorial that teaches what the puzzles require.

The Ripple

World 1-1 is referenced in:

• Every GDC talk on level design (it is the canonical example).
• Every undergraduate game design syllabus.
• Super Mario Odyssey's Cascade Kingdom opening, which is a direct homage.
• Celeste's Chapter 1 opening, which teaches dash, jump, and climb through pure environmental arrangement.
• Hollow Knight's King's Pass, which teaches movement through similarly silent means.
• Portal's Test Chamber 00, which teaches button, cube, and portal through spatial affordance.
• Braid's World 2, which teaches time-rewind through an unavoidable death scenario.
• Your progressive project's opening area, if you are doing it right.

The ripple is not that every game copies 1-1 directly. The ripple is that the methodology — teach through environmental arrangement, build the tutorial last by reverse-engineering, trust the player to learn through doing — is now the default expectation for well-designed games. Games that still teach through text tutorials and NPC instructions are increasingly seen as not having done the design work.

The Broader Lesson

The reason World 1-1 matters to you, as a designer working on your own game, is not that you should copy it. It is that its methodology is transferable.

When you sit down to design your own opening level, ask Miyamoto's questions:

1. What does the player need to know by the end of this level to continue the game?
2. What sequence of environmental arrangements would cause the player to try each of those actions, in an order where each action becomes motivated by the previous one?
3. What is the failure mode for each teaching moment, and is the failure itself pedagogical?
4. Is there a layer of optional content (hidden blocks, shortcuts) that rewards the experimental player without punishing the straightforward one?

Then build it. Playtest it. Watch players. If a player does not jump at the Goomba, your Goomba is in the wrong place. If a player walks off the pit, your pit is too sudden. If a player ignores the mushroom, your mushroom is positioned wrong. Adjust.

Super Mario Bros. World 1-1 is the proof, in forty-five seconds, that teaching through play is the most efficient instructional medium in games. It has been imitated, studied, and honored for forty years. It will outlive us. The lesson it encodes — trust the player; make the environment the teacher; build the tutorial last — is as close to universal as game design gets.

You owe Miyamoto a minute of study. Play 1-1 again, with attention. Notice what the level is doing. Then go design your own first level with the same discipline.

A Counter-Reading: What 1-1 Does Not Teach

An honest case study should acknowledge limits. Super Mario Bros. World 1-1 is a teaching level, but it is not a complete teaching level — and the gap between what 1-1 teaches and what the rest of the game requires is instructive.

The level does not teach the running jump — holding the run button to cross longer gaps. That lesson arrives in World 1-2, and players who rely only on the standing jump will struggle at certain later gaps. The level does not teach the wall-clip or the fireball arc or the swimming controls. It does not teach that the end-of-level flagpole can be grabbed at different heights for different point values. These omissions are not failures; they are evidence that Miyamoto distributed his teaching across levels rather than cramming it into one.

The design lesson is subtle and often missed: teaching through play is not the same as teaching everything in the first level. A good tutorial level teaches what the player needs to enjoy the next level. The rest can wait. Designers who try to front-load every mechanic in their opening level produce overwhelming tutorials that feel like homework. Miyamoto's restraint — teach three things in Level 1, four more in Level 2, three more in Level 3 — is the harder craft.

Playtesting and the Dead End

One more historical detail the GDC literature tends to omit. World 1-1 as shipped was not Miyamoto's first draft. The team iterated it many times during development, watching new players play, revising. The famous story that Miyamoto designed 1-1 "last, after testing the rest of the game" is partially true and partially simplified. The actual process was iterative playtesting — the Nintendo team at the time did not have a formal playtest lab, but Miyamoto tested the levels on colleagues, family, and visitors, and he watched where they got stuck.

One apocryphal but widely-repeated detail: the first Goomba's position was adjusted multiple times based on whether testers would try to jump on it or run past it. In earlier drafts, the Goomba appeared too close to the player's spawn; testers had not yet understood the jump button and would run into the Goomba and die, repeatedly, before learning to jump. Miyamoto moved the Goomba farther right, giving players time to experiment with the buttons in safety before facing a threat. The shipped placement is calibrated within pixels.

This is the part of the design process that case studies tend to lose. World 1-1 looks, in its shipped form, like a composition. It is a composition — but it is a composition that was produced through repeated iteration based on watching players, not through pure authorial insight. The lesson generalizes: your best tutorial level will also be iterated into shape through playtesting. Plan for the iteration. Allocate time for it.

The same pattern holds for every great teaching level in the medium's history. Valve's playtest practices on Portal are legendary — they had testers play through every chamber with an observer recording every confusion. Celeste's Chapter 1 was rebuilt several times during Maddy Thorson's development. Hollow Knight's King's Pass went through many iterations. The myth of the designer who "just knew" is usually a misleading cover for the reality of patient iterative craft. Miyamoto was a brilliant designer. He was also a disciplined playtester. Both are true.