Design teams rarely set out to create confusing systems. Most designers genuinely want their products to feel clear and supportive, and yet misunderstanding appears again and again. Interfaces launch after careful design reviews, usability testing and accessibility checks, and still people misinterpret workflows, misread terminology, or rely on memorized steps instead of understanding.
These signs suggest that the problem does not come from isolated mistakes. It comes from deeper assumptions embedded in the way systems are conceived and built. Those assumptions shape how teams interpret user behavior, how they structure information and how they define success, and over time they create conditions in which cognitive distance becomes almost inevitable. This chapter examines four of them.
7.1 The Assumption of Rational Navigation
Designers assume users think hierarchically
Many systems are organized as hierarchies. Information is grouped into categories, categories contain subcategories, and users move downward until they find what they need. From a design perspective this looks logical and orderly. Hierarchies are easy to diagram and provide clear boundaries between sections. But people do not always reason about tasks hierarchically. They think in terms of goals and situations. Someone visiting a government website may not know which department handles a service; they simply want to get something done. If the system forces them to interpret administrative categories before they can proceed, they must adapt to the system’s conceptual structure, and that adaptation is cognitive distance.
Real-world goals rarely map cleanly to interface categories
A single goal often cuts across several organizational categories. A small business owner updating licensing information on a government platform may be dealing at once with regulatory compliance, financial reporting and local administrative requirements. Internally, these belong to separate departments, so the system organizes information along those lines. For the owner, it is one task. When a system splits that task across several categories, people must reconstruct the path through trial and interpretation, and the interface ends up reflecting institutional logic rather than human intention.
Hierarchies create fragile navigation
Hierarchical navigation works best when people can predict where information will be. When categories overlap, or terminology differs from everyday language, they hesitate. They choose one category only to discover that the option they need is somewhere else, and repeated misclassification erodes their confidence in the structure. Eventually they stop reasoning about the hierarchy and start exploring at random. At that point the navigation no longer works as a conceptual guide; it has become a collection of possible paths.
7.2 The Assumption of Shared Vocabulary
Designers often speak a different language than users
Language is one of the most powerful tools in interface design. Labels guide navigation, instructions explain actions and feedback messages clarify responses. Yet the vocabulary in these elements often reflects internal organizational language rather than everyday speech. Engineers and product teams become deeply familiar with technical terms during development, the terms start to feel natural, and when they appear in the interface the team assumes they are self-explanatory. People meeting the system for the first time may read them very differently, and even small differences in wording reshape how they understand what the system does.
Terminology influences mental models
Words do more than name functions; they shape how people conceptualize what the system is doing. If a financial application calls a feature “account reconciliation”, users may imagine a complex accounting process. If the same function is labeled “check your balance records”, the mental model becomes far more approachable. Both labels refer to the same operation, but they signal different conceptual structures. When terminology reflects internal processes rather than user goals, people must translate the system’s language into their own, and the distance grows.
Misinterpretation accumulates over time
A single unfamiliar term rarely causes serious problems, but systems never rely on one label alone. Interfaces contain dozens or hundreds of textual elements, and if several require interpretation, the effort adds up. People start second-guessing their understanding and hesitate before choosing options, because they cannot confidently predict what each term means. Language becomes one more layer of translation between human reasoning and system logic.
7.3 The Assumption of Linear Workflows
Many systems assume tasks occur in fixed sequences
Teams often structure workflows as a series of sequential steps: the user starts on one screen, completes an action and moves to the next. The structure simplifies development and testing, since each stage can be evaluated independently and progress is easy to track. Real tasks rarely unfold that neatly. People gather information, reconsider decisions and adjust their plans as new information appears. When a system enforces a rigid sequence, they cannot move between steps to refine their understanding, and the interface dictates a process that may not match the way they reason.
Exploration becomes difficult
Linear workflows also reduce opportunities for exploration. If people cannot preview later steps or revisit earlier ones without starting over, they see only one piece of the process at a time and struggle to build a model of the whole. They may complete the workflow without understanding its structure, following instructions step by step without integrating them into a coherent picture.
Rigid workflows amplify uncertainty
When people cannot anticipate what comes next, uncertainty increases and each step becomes a moment of interpretation. If the process involves important decisions or irreversible actions, that uncertainty can turn into anxiety, and people proceed cautiously or abandon the process altogether. The system functions, yet the relationship between person and interface remains fragile.
7.4 The Assumption of Static Understanding
Designers assume users eventually learn the system
A common assumption is that early confusion disappears with experience: people will learn where features are and how workflows operate. There is some truth in this, since repeated exposure does improve performance. But familiarity does not always produce understanding. People can memorize procedures without forming a coherent model, knowing which buttons to press but not why. If the interface changes even slightly, their strategy collapses, because what they learned was procedural rather than conceptual.
Organizational turnover reveals hidden problems
The effect is especially visible in large organizations. Long-serving employees navigate internal systems efficiently, while new employees struggle. Training sessions tend to teach specific procedures rather than the conceptual structure of the system, so each new group must memorize the same steps. The system never becomes understandable; it simply accumulates layers of learned routine.
Systems that require training signal cognitive distance
When a system needs extensive training just for routine tasks, that is often a sign that its conceptual model differs significantly from how people reason. Training can compensate for the difference, but it does not remove it. It teaches people to operate within the system’s framework, and the underlying distance remains, quietly shaping every interaction.
7.5 Recognizing the Pattern
Each of these assumptions feels reasonable during design. Hierarchies look organized, technical terminology feels precise, linear workflows simplify implementation and training seems a practical fix. None of them necessarily causes a serious problem on its own. Together, though, they gradually shift a system away from the structure of human reasoning, until the interface reflects internal logic rather than user understanding. People adapt by memorizing procedures, relying on external instructions and learning to navigate without understanding, and that adaptation hides the distance from the very metrics meant to find it. The system appears functional while the relationship between person and machine remains fragile.