Don Norman, 1988

“Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating.”

Norman framed usable objects as conversations conducted through shape, feedback, constraints, mapping, and the user's mental model. Reading Don Norman in the setting of “The Design of Everyday Things” changes how the quotation lands. The year 1988 identifies the documented source, while April 22 is only this series' calendar position. That distinction protects Don Norman's words from a familiar problem: a compact sentence can travel farther than the reasoning that supported it. The original audience faced particular tools, constraints, and expectations; later readers bring different ones. Returning to “The Design of Everyday Things” therefore does more than verify authorship. It clarifies the problem under discussion, shows what the speaker actually claimed, and marks where modern interpretation begins.

A design succeeds when its structure makes intended actions and system responses understandable to the people using it. For a present-day team, Don Norman's idea becomes useful when it changes a decision instead of decorating a slide. A reviewer might use it to question an interface, architecture, dataset, workflow, or governance rule. The next step is to name the desired outcome, identify the people who experience the system, and choose evidence that could disprove the team's preferred story. This approach treats “The Design of Everyday Things” as an argument to examine rather than authority to borrow. It also turns a memorable line into a practical test: what would builders do differently if they took its central insight seriously?

Understanding users is not permission to manipulate them; communication should preserve agency, accessibility, privacy, and the ability to refuse. That qualification keeps Don Norman's sentence from becoming a universal slogan. Technical results live inside organizations, markets, laws, and communities, where a narrow benchmark rarely settles the whole question. A responsible reading of “The Design of Everyday Things” makes assumptions visible, records tradeoffs, and asks who gains convenience and who inherits risk. It also leaves room for contrary evidence and affected people to change the conclusion. Preserving limits is not hostility to innovation; it connects ambition to accountability and makes correction possible before an elegant idea hardens into an expensive or harmful system.

Onboarding, consent flows, dashboards, devices, and AI interfaces reveal whether a product explains itself or shifts confusion onto users. The enduring value of Don Norman's quotation is therefore a method, not a formula. Individuals can use it to sharpen the next question, while organizations can use it to assign ownership, improve measurement, and explain why a design deserves trust. The strongest modern application of “The Design of Everyday Things” combines historical accuracy with present evidence: understand the source, test the claim in its new environment, disclose important limits, and revise the implementation when real conditions disagree. Admiration for a famous technologist is optional; what matters is whether the idea helps people make technology more understandable, dependable, useful, and answerable to those it affects.