What is Cognitive Load?

Cognitive load is the mental effort required for a player to understand, process, and act within a game’s systems at any given moment.

It is not about difficulty in a mechanical sense — it is about how much the player’s working memory can handle before clarity collapses.

🔗

Game Map Linkage

Cognitive load is a part in Player layer, and it is determined by Readability & Clarity framework:

Readability & Clarity framework →→ Cognitive Load

Cognitive load determines and affects:

→ Frustration: how readability and comprehensibility of game information affect player experience in a negative way.

→→ Flow: how readability and comprehensibility of game information affect player experience in a positive way.

📍Cognitive load is the bridge between design complexity and player comprehension.

If it is too high, frustration spikes. If balanced, players enter flow.

1️⃣ Definition

Cognitive Load in game design is the total mental processing required for:

Understanding the current state of the game,
Selecting an action,
Predicting the outcome,
And integrating feedback into strategy.

Type	Description	Example
Intrinsic Load	Complexity of the core task itself	Calculating DPS in an RPG
Extraneous Load	Confusion from poor design or UI	Hidden stats, unclear icons
Germane Load	Mental effort that aids learning	Discovering combos in Hades

📍Good design manages intrinsic load, removes extraneous load, and fosters germane load.

2️⃣ Why Cognitive Load Matters

Impact	Result in Play
Too high	Player feels overwhelmed, frustrated, stops experimenting
Too low	Player feels bored, disengaged
Balanced	Player feels challenged but capable, enters flow

📍Games aren’t fun when they’re “hard to think about” — they’re fun when thinking feels rewarding.

3️⃣ Signs of Excessive Cognitive Load

Symptom	Player Behavior
UI clutter	Constantly pausing or missing cues
Too many simultaneous mechanics	Tunnel vision, ignoring features
Poorly paced tutorials	Skipping prompts, forgetting systems
Unclear feedback	Repeating actions blindly
Overwhelming decisions	Analysis paralysis, long idle moments

4️⃣ Techniques to Manage Cognitive Load

Technique	How It Helps	Example
Progressive Disclosure	Introduce mechanics gradually	Celeste unlocks dash variants over time
Clear UI Hierarchy	Reduce visual clutter	Minimal HUD in Hades
Spatial Affordances	Guide attention naturally	Lighted paths in Dark Souls
Chunking Information	Group related actions	Hotbars, radial menus
Adaptive Tutorials	Teach only what’s relevant	Contextual hints in Zelda: BOTW

📍Less is not always more — structured presentation is key.

5️⃣ Cognitive Load and Flow

Relationship	Design Implication
Load Too High	Flow breaks → frustration → churn
Load Too Low	Flow breaks → boredom → disengagement
Balanced Load	Player feels mastery, time distortion, deep focus

📍Flow is not just about challenge — it’s about the right amount of mental demand.

6️⃣ Comparative Profiles: Cognitive Load Sensitivity

Attribute	Player A: Hardcore Optimizer	Player B: Casual Explorer
Tolerance	High, enjoys complexity	Low, prefers simplicity
UI Preference	Dense with data	Minimal, icon‑driven
Response to Load	Slows down, calculates	Avoids, seeks intuitive paths
Ideal Systems	Deep skill trees, meta layers	Clear verbs, visual cues

📍Offer optional depth so both profiles can thrive.

✅ Designer’s Checklist

Is the player only processing relevant information at each moment?

Are new mechanics introduced with enough space to learn?

Does UI hierarchy match action priority?

Are feedback loops simple and clear?

Is there room for the player to focus, not just react?

Summary

Concept	Role
Cognitive Load	The mental effort required to act and adapt in a game

Cognitive Load:

Shapes how quickly players learn and trust systems
Links directly to flow and frustration
Can be tuned by pacing, UI, tutorials, and level design

A well‑balanced cognitive load makes games feel challenging, fair, and deeply engaging.

🧪

Mini-Challenge

Pick a critical gameplay moment (e.g., boss fight, crafting screen):

List every piece of information the player must track.
Identify which are essential and which are clutter.
Remove one element and playtest:

Is clarity improved?
Is mastery still intact?

💡 Bonus constraint: Test on a new player and ask: “What were you thinking about while playing?”

📚

In-depth

Cognitive load (Wiki)
Cognitive Load Theory (Sweller)
Flow Theory (Csikszentmihalyi)