Mental Model

A mental model is the structure a user brings to a task: what they think the objects are, what actions are possible, what order things should happen in, and what language feels natural. Interfaces work better when their labels, grouping, and sequence match that model closely enough that users can predict the next step.

Inside-out design breaks that match. The user thinks “send notification email,” “share with a contractor,” or “make the TV use the soundbar.” The product asks them to choose SMTP, Entra ID, Route 53 aliases, ARC, or some other implementation category first. Those concepts may be real, but they are not always the user’s first model of the task.

The practical move is to design from the user’s goal outward: name the task, show the recommended route, and disclose the underlying model only when it helps the next decision.

Used in

• Affordance HijackingReusing a familiar control for a stronger or different action than users expect.
• Inside-Out DesignOrganizing navigation, setup, and labels around internal systems before user goals.

Related

• Information ArchitectureThe structure, labels, and navigation paths that determine how users find, understand, and move through information or tasks.
• System-Centered DesignDesigning the interface around the system's objects, processes, and architecture before the user's language and goals.
• Cognitive LoadTotal mental effort a user spends to complete a task — split between intrinsic difficulty, extraneous interface noise, and learning.