Manage cognitive load — reveal complexity progressively
GDC-L1-UX-000201
Statement
Attention and working memory are limited resources — spend them deliberately. Show the player what they need when they need it and no more, and introduce systems and interface gradually (progressive disclosure) rather than all at once. Complexity revealed over time is depth; complexity dumped at once is overload.
02
Rationale
The brain can only attend to and hold so much at once, and exceeding that budget produces confusion, missed information, and stress rather than mastery [S-hodent-gamers-brain]. The same total complexity feels completely different depending on delivery: metered out as the player is ready, it reads as a game with satisfying depth (easy to learn, hard to master — DESIGN-0005); delivered all at once, it reads as impenetrable. Progressive disclosure — a UI that starts simple and grows, systems introduced one at a time, advanced options tucked until relevant — keeps the player inside their cognitive budget while still building toward real depth. This is also how a legible system (SYS-0006) stays legible even when it's large.
03
Applies when
Any game with substantial systems or interface — RPGs, strategy, sims, and especially deep systemic games. The more total complexity, the more its pacing matters.
04
Does not apply / Exceptions
Some audiences want the full dashboard immediately (expert-facing tools, hardcore sims where mastering the information is the game). And progressive disclosure can be overdone — hiding things players need, or gating information so aggressively it becomes patronizing or obscure. Balance disclosure against the player's genuine need to see.
05
Implementation
Introduce mechanics and UI elements one at a time, unlocking complexity as competence grows (pairs with just-in-time teaching, UX-0001). Use information hierarchy so the most important things dominate attention and secondary detail recedes. Hide advanced options until relevant.
06
Disagreement
Progressive disclosure (start simple, reveal over time) vs. full-transparency (show everything, trust the player) — the latter suits expert audiences and tools; the former suits broad audiences and deep systems. Also overlaps the transparency⇄mystery axis: how much to reveal is partly a UX-clarity question and partly a discovery-design choice.
07
Notes
The attention-budget principle behind good onboarding (UX-0001) and legible large systems (SYS-0006, DESIGN-0005). Confidence 4.
↔
Connected principles
S