7 Essential UI Design Principles from The Design of Everyday Things Every Product Manager Must Know
Your product's interface is not broken. Your thinking about design is.
Most product managers believe good UI design is the designer's responsibility. They outsource design thinking to the design team, focus on features and roadmaps, and wonder why users churn despite having all the "right" functionality.
Here is the uncomfortable truth: users do not read tooltips, do not watch onboarding videos, and do not care about your innovative interface. They want to complete their tasks without feeling stupid or confused.
The principles in Don Norman's groundbreaking book "The Design of Everyday Things" provide a framework that every product manager needs to understand. These are not just design principles. They are product principles that determine whether users succeed or fail with your product.
Understanding Don Norman's Design Framework
Don Norman's design principles emerged from studying how people interact with everyday objects like doors, faucets, and stoves. The same principles that make a door handle intuitive apply directly to UI design principles for digital products.
Norman identified that good design makes the correct action obvious and the incorrect action difficult or impossible. Bad design requires explanations, documentation, and extensive training.
When you need to add a label that says "push" or "pull" on a door, the door design has failed. When you need extensive onboarding to explain how your interface works, your UI design has failed.
Product managers who understand these UX design principles can evaluate designs, provide meaningful feedback to designers, and make better product decisions. This is not about making things pretty. It is about making things work.
Affordances: Making Actions Obvious
Affordances are the perceived and actual properties of an object that determine how it can be used. In UI design, affordances signal to users what actions are possible.
A button should look clickable. A text field should look editable. A slider should look draggable.
Bad product managers ask: "Can users figure this out if they try hard enough?"
Great product managers ask: "Does this interface element clearly communicate its function at first glance?"
Example of Poor Affordances: Flat design trends created buttons that do not look clickable. They appear as text labels rather than interactive elements. Users hesitate, unsure whether they can click. This is not minimal design. This is bad affordance design.
Example of Good Affordances: Apple's iOS buttons use subtle shadows, borders, and colors that clearly distinguish them from static text. Users know immediately what is clickable and what is not.
For product managers, evaluating affordances means examining every interface element and asking: "Would a new user understand this object's purpose without explanation?"
If the answer is no, you have an affordance problem, not a user problem.
Signifiers: Guiding Users to Success
While affordances indicate what actions are possible, signifiers are explicit signals that guide users toward the correct action. Think of signifiers as design breadcrumbs that lead users to success.
In the real world, a door handle is an affordance. A "Push" sign is a signifier. The handle shows you can open the door. The sign tells you how.
Poor Signifier Example: Generic text that says "Click here" provides no context about what happens next or why the user should click.
Strong Signifier Example: A prominent plus sign button placed in the context where users would want to add something. The icon, placement, and context all signal the action clearly.
Signifiers in design work best when they combine visual cues, placement, and context. A "Save" button at the bottom of a form is a strong signifier because users expect to find save actions in that location.
Product managers should evaluate designs by identifying where users might get stuck. Then ensure signifiers exist at those decision points to guide users forward.
Mapping: Aligning Design with Mental Models
Mapping refers to the relationship between controls and their effects. Good mapping aligns with how users already think about the world.
Example from Don Norman's Design Principles: On a stovetop with four burners arranged in a square, the control knobs should also be arranged in a square pattern matching the burner layout. If the knobs are arranged in a straight line, users must guess which knob controls which burner.
Digital Product Example: In a music application equalizer, vertical position should match volume. Higher position equals louder sound. Lower position equals quieter sound. This matches user mental models from physical equalizers and volume controls.
When mapping aligns with existing mental models, interfaces need zero explanation. Users transfer knowledge from other experiences directly to your product.
Product managers should identify the mental models users bring to your product. What similar tools or experiences have they used? How can your interface mapping leverage those existing models?
Poor mapping forces users to build entirely new mental models. Good mapping lets users apply models they already have.
Feedback: The 100-Millisecond Rule
Every user action needs a clear reaction within 100 milliseconds. This is not a suggestion. It is a requirement based on human perception.
When users click, tap, or interact with your interface, they should never wonder:
- Did that click register?
- Was my file saved?
- Did my message send?
- Is the system processing my request?
Common Feedback Failures:
- Submit buttons that do not show a loading state
- File uploads with no progress indicator
- Actions that complete silently without confirmation
- Delayed responses with no intermediate feedback
Effective Feedback Examples:
- Button changes color or shows a spinner when clicked
- Progress bars for operations that take time
- Success messages with specific confirmation details
- Toast notifications for background processes
Product managers should test every user action in your product and verify that feedback exists. If you can find any action where users might wonder "did that work," you have identified a critical UX problem.
The design feedback principle is simple: users should always know the current system status.
Constraints: Preventing Errors Before They Happen
Good design constraints make incorrect actions impossible rather than relying on error messages to fix mistakes after they happen.
Prevention is always better than recovery.
Poor Constraint Design: A free text field for dates that accepts any input and then displays "Invalid date format" when users type "12-15-2024" instead of "12/15/2024."
Strong Constraint Design: A date picker that only allows valid date selections. Users cannot make formatting mistakes because the interface constrains their choices to valid options only.
Other Constraint Examples:
- Dropdown menus instead of free text for predefined options
- Disabled buttons that prevent impossible actions
- Input fields that only accept numbers when numeric input is required
- Character limits that prevent text overflow
Product managers should review error messages in their analytics. Each common error represents a design failure that constraints could prevent.
Ask: Could we make this error impossible rather than catching it after the fact?
This shift in thinking from error handling to error prevention is a hallmark of mature product thinking.
Consistency: Building User Muscle Memory
Users build muscle memory through repeated interactions. UI design consistency principles honor this muscle memory rather than forcing users to relearn patterns constantly.
Your submit button cannot be blue on page one, green on page two, and labeled "Submit" in one place but "Save" in another.
Types of Consistency to Maintain:
Visual Consistency:
- Colors mean the same thing throughout the product
- Button styles remain uniform
- Icon usage is predictable
- Layout patterns repeat
Functional Consistency:
- Similar actions work the same way everywhere
- Keyboard shortcuts remain constant
- Navigation patterns are predictable
- Interaction patterns transfer across features
External Consistency:
- Following platform conventions (iOS, Android, Web)
- Matching user expectations from similar products
- Using standard icons and patterns
Breaking consistency forces users to think. Maintaining consistency lets users operate on autopilot, focusing on their tasks rather than your interface.
Product managers should establish design systems that enforce consistency across teams and features. Inconsistency often emerges when different teams work in isolation.
Discoverability: Making Features Visible
Discoverability means users can find features without extensive searching, documentation, or hidden gestures.
If users need tutorials to find basic features, your design has failed. If power users know secret gestures that normal users never discover, your design has failed.
Common Discoverability Failures:
- Important features hidden in hamburger menus
- Gestures with no visual indication they exist
- Features accessible only through keyboard shortcuts
- Actions buried three levels deep in menus
Improving Discoverability:
- Progressive disclosure (showing options when relevant)
- Contextual help and hints
- Clear navigation hierarchy
- Visual cues for hidden actions
Product managers should conduct regular user testing with new users. Watch where they get stuck. Note which features they never discover. These observations reveal discoverability problems.
The best features are useless if users cannot find them.
The Truth About User Errors
Here is the harsh reality about so-called "user errors": they are almost always design errors.
If users need extensive onboarding, the design failed. If users keep making the same mistakes, the design failed. If users cannot find features, the design failed.
This is not about blaming designers. This is about product managers taking responsibility for design thinking.
Stop calling them "user errors." Start calling them "design opportunities."
When you see patterns in user behavior that differ from your intentions, the gap is not in user intelligence. The gap is in your design's communication.
Reframing Common "User Errors":
Instead of: "Users aren't reading the instructions" Think: "Our interface requires instructions, which means it lacks clear affordances and signifiers"
Instead of: "Users keep clicking the wrong button" Think: "Our button placement, labeling, or visual hierarchy is misleading users"
Instead of: "Users don't understand our innovative interface" Think: "Our interface breaks users' mental models and lacks adequate mapping"
Product managers who adopt this mindset create better products because they focus on fixing design rather than "fixing" users.
How to Apply These Principles as a Product Manager
Understanding UI design principles is valuable only if you apply them to your daily product decisions. Here is how to integrate these principles into your workflow:
During Design Reviews:
- Evaluate affordances: Can users tell what is clickable without hovering?
- Check signifiers: Are there clear visual guides at decision points?
- Test mapping: Does the interface align with user mental models?
- Verify feedback: Does every action produce immediate, clear feedback?
- Examine constraints: Could we prevent errors instead of catching them?
- Assess consistency: Do similar actions work similarly across the product?
- Measure discoverability: Can new users find features without help?
When Reviewing Analytics: Look for patterns that indicate design principle violations:
- High error rates suggest missing constraints
- Low feature adoption indicates discoverability problems
- Support tickets about "how do I" questions reveal affordance failures
- Complaints about unexpected behavior show mapping mismatches
In User Testing: Watch for moments when users:
- Hesitate before taking action (affordance problem)
- Look confused about what to do next (signifier problem)
- Make the same mistake repeatedly (constraint problem)
- Express surprise at outcomes (mapping problem)
- Wonder if their action worked (feedback problem)
Working with Designers: Use these principles as a shared language. Instead of saying "make it prettier," say "this button lacks clear affordances" or "we need stronger signifiers here."
Designers will respect product managers who speak their language and understand fundamental design principles.
You can access 100+ AI prompts specifically for design thinking and user research that help PMs apply these principles in real scenarios. These prompts help you evaluate designs, conduct user research, and make better product decisions using Don Norman's framework.
Conclusion: Design Thinking Is Your Job Too
Many product managers believe design is the designer's job. They are wrong.
Design is not about making things pretty. Design is about making things work.
As a product manager, you make decisions every day that impact design:
- Which features to prioritize
- How to structure information
- What workflows to support
- Where to add friction or remove it
These are design decisions whether you call them that or not.
The seven UI design principles from The Design of Everyday Things provide a framework for making better decisions:
- Affordances show users what actions are possible
- Signifiers guide users toward correct actions
- Mapping aligns interfaces with mental models
- Feedback confirms that actions succeeded
- Constraints prevent errors before they happen
- Consistency builds reliable muscle memory
- Discoverability makes features findable without help
Master these UX design principles and you will build products that users can actually use. Ignore them and you will build products that require constant explanation, generate support tickets, and drive users to competitors.
The choice is yours. But remember: your users will not read the manual. They will not watch the tutorial. They will not attend your webinar about the new feature.
They will simply try to use your product. And if your design principles are sound, they will succeed.
If not, they will leave.
Stop outsourcing design thinking. Start applying these principles to every product decision. Your users, your team, and your business metrics will thank you.