Simplicity is not deleting functions but clarifying structure
Aliases: structural simplicity · information architecture · meaningful simplification
What it is
Structural simplicity does not aim for few functions. It makes the relationships among objects, tasks, states, and actions understandable. A product can have rich capability when related capabilities are integrated, names are consistent, hierarchy is predictable, default paths are clear, and exceptions can be explained. Conversely, a product with few functions remains complex if concepts are confused, entries hidden, or rules contradictory. Simplicity addresses understanding and decision burden.
Why it happens
People do not perceive feature count directly. They perceive how many concepts they must distinguish, paths they must choose between, and exceptions they must remember to meet a goal. Clear structure can organize several operations under an understandable object model, transferring prior knowledge to new capability. Removing surface controls without improving the model only moves choice into menus, memory, or help. Merging duplicate concepts, removing meaningless difference, and clarifying hierarchy reduce real cognitive burden.
Studying it
Ask people to explain core objects, primary tasks, and relations among functions, checking whether their mental model aligns with system structure. Observe conceptual confusion, mistaken categorization, entry search, and exception memory in tasks rather than simply counting interface elements. Compare deletion, restructuring, and naming changes for comprehension, discovery, efficiency, and durable transfer to see whether simplification actually occurs for users.
Where it stops holding
Structuring does not mean making everything a hierarchy tree: cross-object tasks may need multiple entries, search, automation, or contextual aggregation. Excessive abstraction can also hide concrete action. For infrequent or specialized capability, complete understanding may be unrealistic, requiring retrievable help and safe paths. Simplicity does not demand one model for everyone; it gives each key task a sufficiently clear local model.
Applying it
- Organize information architecture around user objects and goals rather than internal modules; merge synonymous functions, unify language, and remove meaningless parallel entries.
- Use default paths, adjacent actions, stable hierarchy, and explicit exceptions to help people construct rather than memorize structure.
- Before and after restructuring, test whether people can explain what something is, what it can do, and where next is; use explanation quality as a simplicity measure.