When content is inherently complex, forcing a simpler appearance shifts that complexity onto the user's own mental processing

What it is

The amount of judgment a task requires, the amount of information a user has to process, does not shrink just because the interface looks tidier. Collapse several openly displayed options into a folded menu, merge a handful of parameters that need weighing into one blanket toggle, and the screen does look cleaner — but the judgment the user originally had to make has not gone away. It has only moved from "visible and directly comparable" to "either guess from memory, or click through to see it." This shift can be called conservation of complexity: the complexity a system has to handle is roughly a fixed quantity, and whatever gets deleted from the surface does not really disappear — it gets pushed into the user's own mental processing, usually at a higher cost than displaying it directly would have been, not a lower one.

Why it happens

Interface complexity and content complexity sit at two different levels: the former is how much is sitting on the screen, the latter is how many steps of judging, comparing, and remembering a user needs to complete a task. Simplifying the appearance only touches the first. If the content's own complexity has not dropped along with it, the user still has to work through the same number of judgment steps — just without the external support that used to make it easy (options side by side can be compared directly; options folded away either have to be judged from memory, or require an extra open-and-close action just to compare them). The visual complexity saved is paid for by extra load on the user's working memory and extra operating steps — the two trade off against each other rather than dropping together.

Where it stops holding

When the folded or merged options are genuinely few, differ little from each other, and the user has no strong preference among them anyway, folding them away really is low-cost, and a simpler appearance and lower overall complexity move together. But when there are many options, the differences between them materially affect the outcome, and users typically need to go back and forth comparing before deciding, folding or merging noticeably adds steps and memory load to completing the task. In that situation, "the surface looks simpler" and "the task is easier to complete" pull in opposite directions, and the first cannot be assumed to bring the second along with it.

Applying it

• Before deciding whether to fold or merge a group of options, judge the complexity of that group itself: how many options, and whether the differences between them require comparison to decide. Options that are few and barely differ can be folded away with confidence; options with large, comparison-worthy differences need a clear answer for how much effort it will cost the user to reopen and compare them before you fold them.
• If folding is genuinely needed to free up space, keep at least one low-cost way to preview — a hover reveal, or an expanded view that shows all options without switching back and forth — rather than making the user click once per option just to compare.
• To verify: measure time on task, click count, and wrong-choice rate for the same decision task under a fully-displayed version and a folded version. If the folded version is noticeably slower, requires more clicks, or produces more wrong choices, this simplification only hid the complexity — it did not actually reduce it.

Related

• Same group: A2.12.1 The visual system reads ambiguous figures as the simplest possible structure — the perceptual basis of the pull toward simplicity · A2.12.2 Visual minimalism as a style is not the same as perceptual-processing simplicity · A2.12.3 Stripping visual cues for a cleaner look can raise the cost of discovering an interaction · A2.12.5 The pull toward simplicity works on figure recognition and does not automatically extend to information-architecture simplification · A2.12.6 Fewer visual elements does not mean less cognitive load — the two need to be verified separately
• Nearby: A9 Cognitive load · H1 Forms
• Search terms: conservation of complexity · progressive disclosure · cognitive offloading