great-designers — from Rams to Norman

Design is the craft of making choices that the user never has to think about. The choice of where to put a control, what to call it, how much space to leave around it, and what happens when it is activated — these are all decisions that disappear into the product when they are made well. When they are made poorly, the user feels the friction without knowing why.

Why great-designers is a distinct plugin

The failure mode of mixing design with engineering is that the designer starts making implementation decisions and the engineer starts making aesthetic decisions. Neither craft goes deep enough. The product ships with compromises that feel like limitations rather than choices.

great-designers keeps the design register clean. The plugin does not write code. It does not specify implementation. It produces: wireframes, decision rationales, and design critiques written in the vocabulary of perception and cognition — not of components and APIs.

The personas

Dieter Rams: restraint as a discipline. His ten principles are a decision table — if a feature does not contribute to the product's primary function, it should not exist. The Rams register is architectural: what does this product not do, and is that absence intentional.

Don Norman: cognitive flows and error prevention. The Norman register is psychological — affordances, feedback loops, the gap between the designer's mental model and the user's. A Norman review asks: where will the user go wrong, and what in the design prevents them from recovering.

Edward Tufte: information density without decoration. The Tufte register is editorial — every mark on the surface that does not encode data is noise, and noise degrades signal. A Tufte review of a dashboard asks: how much information is here, and how much of the visual complexity is carrying it.

Susan Kare: icons and pixels at the smallest useful scale. The Kare register is tactile — an icon works when it is recognizable at 16 pixels, not because it is beautiful at 256. The constraint is the design.

Paula Scher: typography and identity at scale. The Scher register is theatrical — what does this say before anyone reads it? The type choice, the color, the hierarchy — these speak before the words do.

What it unlocks

Design review filtered through specific lenses in sequence. Not "make this look better," but: Rams on whether the feature should exist, Norman on whether the user will understand it, Tufte on whether the information is presented efficiently, and Kare on whether the smallest interactive elements are legible.

Each review speaks in its own register. The feedback is not generic. It is specific to the craft lens — which means it is actionable.

If you get stuck

If you are not sure which design persona to route a problem to, describe the problem's primary friction. If the friction is "too many features," Rams. If the friction is "users keep making the wrong choice," Norman. If the friction is "the dashboard is confusing," Tufte. If the friction is "the icons are unclear," Kare. If the friction is "the brand does not read at a distance," Scher.

The friction names the lens.

Cross-reference

Lesson 6 (Why mixed registers fail) gave the general principle. This lesson shows what that principle looks like in the specific case of design — a craft that is particularly vulnerable to contamination from adjacent crafts.

Plugin source

The shipped plugin lives at github.com/sethshoultes/great-minds-constellation/plugins/great-designers. Nine design personas (Norman, Zhuo, Spool, Rams, Kare, Cagan, Scher, Hatfield, Tufte).

Deliverable

Take one interface decision you have made recently — a label, a layout, a control placement. Route it through two design personas from the list above. Write two sentences of critique from each persona. Note where the critiques agree and where they conflict.