How do you tell whether a design is dated or just unfamiliar to you?

A design is genuinely dated when it uses patterns that have since been superseded for a real usability or aesthetic reason, and merely unfamiliar when it simply differs from your current taste or the work you have been looking at lately. The test is whether your judgment rests on evidence of a better current approach or only on personal habit. Separating the two is harder than it sounds, because both arrive as the same gut reaction, a quiet “this looks old,” and that reaction is no more trustworthy when it is right than when it is wrong.

The reason you cannot trust the instinct alone is that exposure shapes taste, and taste masquerades as judgment. If you spend your days inside a particular visual language, anything outside it reads as off, and your brain helpfully relabels “different from what I usually see” as “behind the times.” But novelty of exposure is not the same as obsolescence. A pattern can be unfamiliar to you because it belongs to a different domain, a different audience, or simply a corner of the field you do not frequent, while remaining perfectly current and effective for the people it serves. The only way to get past the reflex is to demand evidence: can you point to a specific reason the newer approach is better, a usability gain, an accessibility improvement, a measured outcome, a problem the old pattern actually causes. If you can, the design is dated. If all you have is that it does not match your recent diet of work, you are looking at unfamiliarity wearing the costume of expertise.

Consider a content-heavy interface built around dense tables, tight spacing, and small type, the kind of layout that looks nothing like the airy, generous design that dominates current portfolios. A designer steeped in that airier style will glance at it and feel certain it is dated. But if the users are analysts who scan thousands of rows a day and rely on seeing as much data per screen as possible, the dense layout is not behind the times; it is fit to its purpose, and the “modern” airy version would force them to scroll endlessly for information they need at a glance. That is unfamiliarity, not datedness. Now contrast it with an interface that hides every primary action behind a hamburger menu on desktop where there is ample room, a pattern the field moved away from precisely because it buried navigation and measurably hurt discoverability. That one is genuinely dated, and you can say exactly why: a better current approach exists and the reason it is better is documented in how people actually behave.

This flips when evidence cuts both ways and the two categories overlap. A design can be both unfamiliar to you and genuinely dated, and your unfamiliarity does not make the datedness false; you still have to check for the real reason rather than dismissing your reaction outright. Conversely, a pattern can feel current simply because it is everywhere right now, and ubiquity is not evidence of quality either, it is just a louder version of the same exposure trap. The discipline is the same in both directions: do not let what you happen to see often, or rarely, stand in for whether an approach actually serves users better. Familiarity and quality are independent, and the whole skill is keeping them apart.

So when a design strikes you as dated, stop before you act on the feeling and ask for the receipt: name the superseded pattern and the concrete reason the current approach beats it, in terms of how users behave or what they can do. If you can produce that, treat it as dated and fix it. If you cannot get past “it looks old to me,” treat it as your own unfamiliarity and leave it alone. Decide by evidence over habit, not by the era your eye happens to belong to.