The 6 fundamental principles that explain how people understand, navigate, and interact with everyday products — physical or digital.
Don Norman, co-founder of the Nielsen Norman Group and the person who coined the term "user experience," introduced these principles in his 1988 book The Design of Everyday Things. They describe the cognitive bridge between a user's intent and a product's response, and have become foundational reading for anyone designing interfaces.
Unlike checklist-style heuristics, Norman's principles work as a diagnostic framework: when a user struggles, you can usually trace the friction back to one of the six. A button no one notices is a visibility problem. A form that gives no confirmation is a feedback problem. A control that doesn't behave the way it looks is a mapping problem.
Use these principles when reviewing a website to surface "why doesn't this make sense?" issues that other heuristics often miss — especially on novel interfaces, dashboards, and complex workflows where users build a mental model from scratch.
The more visible a function is, the more likely users will know how to proceed. When controls, options, and current state are out of sight, users have to remember or guess — and they usually guess wrong. Surface what matters; hide only what truly doesn't.
Feedback communicates the result of an action: did it work, is it processing, did it fail? Loading spinners, toast notifications, button state changes, and form validation messages all close the loop. Without feedback, users repeat actions or assume the system is broken.
Affordance describes the action possibilities an object offers — what a user can do with it. A button affords pressing; a handle affords pulling. On the web, a clickable card affords tapping only if it visually behaves like a target — color, elevation, hover state, and cursor all signal "I can be acted on."
Mapping is the relationship between controls and their effects. The arrangement of stovetop knobs should mirror the arrangement of burners. On the web, a volume slider should grow as it goes up, not down — natural mappings reduce the need to think and the chance of error.
Constraints limit possible actions to prevent errors and guide users toward the correct path. A USB-C connector that fits either way removes a constraint that frustrated users for decades. In digital products, disabled buttons, input masks, date pickers, and step-gated wizards are constraints that protect users from invalid states.
Similar tasks should be done in similar ways. Consistent layout, naming, and interaction patterns let users transfer knowledge from one part of a product to another, dramatically reducing learning cost. Break consistency only when the new pattern is measurably better — and apply the new pattern everywhere it fits.
We use cookies to run this site and, with your permission, to understand how it's used and show relevant ads. Necessary cookies are always on. You can change your choice anytime from the footer. Learn more
