The End of the Tutorial: When Games Should Stop Teaching

Theres a moment in every game where the tutorial stops being helpful and starts being annoying. The line is harder to spot than developers think it is. I want to talk about where the line is and what crossing it costs.

I noticed this most recently while reviewing Mechanic Bot on this site. The game has four robot types with distinct abilities, and the tutorial spends maybe twenty minutes walking you through each one in turn. Each robot got its own tutorial sequence. By robot four I was muting the audio and clicking through prompts to get to the actual game. The tutorial was doing its job up to about robot two. After that it was just delaying the part I wanted to play.

What the tutorial is for

Teach the player the mechanics they need to enjoy the game. Thats the whole job. Once the player understands those mechanics, the tutorials work is done. Continuing past that point isnt helpful. Its a tax on the players patience.

The mechanics that need teaching depend on the genre and the players background. A platformer needs to teach the jump arc. A puzzle game needs to teach the core rule. A shooter needs to teach the aiming model. An adventure game needs to teach the inventory system. These are the foundational mechanics without which the game doesnt work.

Once these foundations are in place, the player can learn the rest through play. New enemies. New items. New environmental hazards. New movement abilities the player picks up along the way. These dont need explicit tutorial. The player figures them out by encountering them in safe-enough contexts.

The common over-teaching patterns

A few specific patterns show up repeatedly in browser games.

First, teaching mechanics that havent appeared yet. You unlock a new ability in chapter three. The chapter-three intro spends five minutes explaining the ability before letting you use it. By the time you can actually try the ability, the explanation has faded from memory. Better to let you try it and have the explanation pop up if you struggle.

Second, teaching mechanics the player already understands. The first inventory pickup is explained. The second one is also explained. The tenth one is still being explained. After the first or second pickup, the player knows what an inventory pickup is. Explaining the eleventh wastes their attention.

Third, teaching mechanics through pop-ups that block gameplay. The player is in the middle of a section. A tutorial pop-up appears. The game pauses. The player has to read or skip the pop-up. Then the game resumes. The interruption breaks flow and feels patronising. Better to teach inline with environmental cues or short animated overlays that dont block play.

Fourth, teaching mechanics in the wrong order. The tutorial covers everything in chapter one, including mechanics that wont be relevant for several chapters. Information density is overwhelming up front and forgotten by the time it matters. Better to teach mechanics just before they become relevant.

When the tutorial should end

A rule of thumb. The tutorial should end when the player can describe what theyre doing in their own words. Up to that point, the player needs guidance. Past it, they dont.

For a browser game, this is usually within the first five to ten minutes of play. The mechanics that need teaching are usually small in number and learnable in that window. Longer tutorials are signaling either an unusually complex game or a tutorial thats over-teaching.

Five-to-ten-minute window also fits the browser-game session structure. Players who cant tell what the game is doing in their first session usually close the tab. The tutorial has to finish quickly enough that the player gets to the actual game while their attention is still available.

The optional-extended-tutorial option

Theres a design pattern that handles this well. The mandatory tutorial covers the basics quickly. After that, theres an optional extended tutorial available from a menu for players who want more help. Most players skip it. Players who need more help find it. Both audiences are served.

Minesweeper Classic on this site does something like this. The basic tutorial is 90 seconds. The detailed strategy guide is available from a help menu but doesnt interrupt play. Players who want the deeper explanation can find it. Players who dont are unbothered.

This is the right pattern. Mandatory teaching for the minimum. Optional teaching for the rest.

The mobile context makes this worse

I want to flag the mobile-specific problem. Tutorials on mobile are interruptions during play sessions that are already fragmented. A five-minute tutorial in the middle of a bus ride consumes the whole session. The player gets off the bus having only seen the tutorial, not the game.

Mobile browser games should respect this. Tutorials should be the shortest they can be while still teaching the foundations. Five minutes is too long. Two minutes is better. Inline-only teaching is best when possible.

Mobile games on this site that get this right are the ones that became my regular bus-rotation games. Pixel Runner taught me the controls in the first thirty seconds. Mini Golf Pro has no real tutorial because the mechanics are visually obvious. Number 2048 has no tutorial because the rules are explained in two sentences when you load the game. And Stack Tower puts the rules on a single screen between rounds, so you can re-read them mid-session if you want. These games respect my time.

Games that over-teach often get a star knocked off in my reviews. Mechanic Bot at 4.5 stars would be a 5 if the tutorial were half as long. Knight Adventure at 4 stars has a tutorial sequence that I find tedious even on the desktop replay; on mobile its a deal-breaker.

What developers should consider

If youre designing a tutorial, ask whether each minute of it is teaching something the player wont figure out on their own within the first hour of play. If the answer is no, cut that minute. Most tutorials can be cut to a third of their current length without harming new-player onboarding.

If youre worried that some players will struggle without the cut tutorial content, put it in an optional menu. Players who need it can find it. Players who dont arent punished by it.

If your tutorial includes ten or more pop-up interruptions in the first session, you have a problem. Two or three pop-ups for really critical information is appropriate. Ten is over-teaching.

If your tutorial explains the same concept multiple times because you dont trust the player to remember, the problem is the tutorial. Make the explanation clearer the first time. Trust the player to retain it.

What this means for you

When you start a browser game and the tutorial feels too long, youre probably right. Most browser-game tutorials are over-teaching for fear of losing players who dont understand. The fear is real but the solution is wrong. Players are more often lost to overlong tutorials than to too-brief ones.

If a games tutorial feels patronising, thats a real signal about how the developer thinks about players. They dont trust you to figure things out. They are wrong to not trust you. Other games will. Move on.

Games on this site that I rate highest tend to have short, respectful tutorials or no tutorials at all. The connection is not coincidental. Tutorial discipline correlates with broader design discipline. Games that respect your time in the tutorial tend to respect your time throughout.