Cognitive overhead

The mental burden imposed by unnecessary complexity, state, or syntax that doesn't directly serve a user's goal. When a programming language, interface, or system forces you to hold too many irrelevant details in working memory, you experience cognitive overhead—the difference between what you actually need to think about and what you're forced to think about.

A classic example: remembering array indices in Imperative programming versus iterating directly in Functional programming. Both accomplish the same expression of intent, but one taxes your attention differently.

Cognitive overhead exists across domains. A seating chart with redundant information, a clinical form with confusing fields, or an infographic with poor visual hierarchy all raise the cognitive cost of understanding or completing a task. Blaise Pascal famously wrote that he'd have written a shorter letter if he had more time—brevity demands eliminating overhead.

Designers and architects reduce cognitive overhead through simplification, clear logic, and thoughtful composition. It's not about making things simple for their own sake, but about respecting the limits of human attention and engagement.

Related

User experience design, Abstraction (computing), Information architecture, Flow state, Minimalism