Don't Make Me Read: How to Design Onboarding That Doesn't Suck

Why 'Obvious' Isn't Obvious and how games like Dishonored and The Witcher 3 teach without lecturing.

February 5, 2026 · 6 min read · Game UX, Onboarding, Tutorials

Imagine: a player launches your game. Downloaded, installed, ready for adventure. And what happens in the first five minutes? The game pauses, locks the controls, and throws up a wall of text about an inventory system they won't need for another two hours.

The result is predictable: the player clicks through without reading. And when it's time to use that mechanic, they have no idea what to do.

Onboarding is the first impression you can't make twice. In this article, I'll break down why tutorials frustrate even experienced gamers and what mistakes industry giants keep making.

Why "Obvious" Isn't Obvious

The main trap is the "Curse of Knowledge." When you've been developing a project for two years, it seems obvious how to open the map or switch weapons. But for a new player, it's not.

The situation is complicated by gaps in "Gamer Literacy." Experienced gamers speak the unspoken language fluently: red barrels explode, Shift means run, yellow paint marks the way up. But newcomers don't know this language.

And here's the paradox: even if your audience is hardcore gamers, you can still break them. Just dump everything on them at once.

Good onboarding doesn't teach "how to press buttons", it teaches the rules of the world. Let the player hammer the nail, not read the hammer's manual.

Cyberpunk 2077: When the City Is Louder Than the Interface

Cyberpunk 2077 is an example of how ambition can overwhelm newcomers. In the first minutes, the player receives multiple layers of load simultaneously.

Instead of smooth immersion, the player gets stress. They're fighting the interface just to understand what's happening.

Perhaps Night City's sensory chaos is intentional. It's cyberpunk: information noise as aesthetic. But even if overload is part of the atmosphere, the learning UI should be an island of clarity. The player isn't ready to drown in chaos, they're still learning to swim.

Root of the problem, the principle of Progressive Disclosure is violated. The game should have introduced systems in layers, giving time to master each one before adding the next.

The clearest example is Braindance. The pace breaks sharply: the player is thrown into a separate mode with a timeline, layer switching (video/audio/thermal), and clue searching. Working memory load spikes. Even experienced players lose their bearings, what exactly counts as "success"?

Cognitive Load Analysis: 7 UI elements compete for attention

How it could have been better: first Braindance, only one layer (video). Second, add audio. Third, full set. Same mechanic, no shock.

Elden Ring: When Poetry Gets in the Way

If Cyberpunk is information overload, Elden Ring is its deficit. A conflict between artistic style and usability.

The tutorial "Cave of Knowledge" is hidden in a pit. The developers tried to guide the player there diegetically: near the edge sits a ghost whispering "Brave Tarnished... Take the plunge."

The problem: the signal is too weak. Souls-game fans spent years learning that jumping into pits = death. The ghost's words were perceived as metaphor ("dive into adventure"), not literal instruction. Many skipped the tutorial and suffered.

Patch band-aid: a couple months later, FromSoftware added a system popup: "Jump down to reach the tutorial." It helped newcomers, purists revolted. The popup "broke the fourth wall." A text popup is an admission of level design defeat. But what else?

Possible solution: a beam of light falling into the pit. Dust particles drifting down. Echo of sounds from below. Visual cues that don't break atmosphere but guide the eye. The player jumps on their own, and feels like a discoverer.

Left: original. Right: visual cue concept, same atmosphere, clearer direction

How to Do It Right: Dishonored

Dishonored: Learning Through Hide-and-Seek

Stealth is a tough genre. Sight lines, noise levels, patrol timing. How do you teach this without killing the hero every five seconds?

Dishonored weaves learning into the prologue. Before Corvo ends up in prison, the game offers... a game of hide-and-seek with little Emily.

Brilliantly simple: you learn crouching, cover, and peeking, with no risk of Game Over. If a guard spots you, death. If Emily spots you, laughter. Anxiety removed, mechanic learned.

And it's narratively justified: Corvo is a bodyguard. Of course he knows how to hide. The game doesn't "teach buttons", it shows who your character is.

The Witcher 3: Quest as Tutorial

White Orchard is the perfect sandbox. But the magic isn't in the location, it's in the Griffin quest.

The game doesn't say "press I for inventory." It creates a situation you can't solve without the interface.

To kill the Griffin, you need to: find herbs (map mechanic), brew oil (alchemy), read about weaknesses (bestiary). Each UI layer is introduced through necessity, not text prompts.

The Bestiary here isn't a lore library, it's a survival tool. The game teaches the core rule of its world: knowledge is a weapon. You can't just button-mash a monster. You need to prepare.

By the time of the fight, the player knows three systems, and doesn't feel like they sat through a lecture. They feel like a Witcher.

When the Best Tutorial Is No Tutorial

Sometimes the boldest choice is to remove hints and trust the player.

The Vanishing of Ethan Carter honestly warns at the start: "This game is a narrative experience that does not hold your hand." Expectations set: you're a detective, not a tourist. No markers after that. Find the clues yourself.

Journey goes further: not a single line of text. Learning happens through light in the distance, dune geometry, visual dominants. You understand where to go because that's where you want to look.

This works when the genre allows: narrative games, meditative adventures, exploration. If the cost of failure is low, give the player the joy of discovery.

Rules of Good Onboarding

Philosophy

Delivery

Respect for the player

Onboarding isn't about "how to press buttons." It's about how the player becomes part of your world. Make them feel like a discoverer, and they'll stay.

Read the full case study in the portfolio →