Susan Kare describes designing the original Macintosh icons, fonts, and symbols under severe technical constraints and with little prior computer experience. Her central argument is that effective interface graphics depend less on visual detail than on meaningful metaphors, memorable forms, and rapid recognition. She also emphasizes iterative design, close collaboration with programmers, showing multiple alternatives, and preserving constraints as a source of creativity.
- Meaningful metaphors outperform decorative detail: Kare argues that an icon should communicate through one or two salient details rather than accumulate realism. She contrasts a simple pencil with a highly rendered pen and points to street signs as examples of designs optimized for instant recognition. Her broader design principle, attributed to Paul Rand, is to make things meaningful and memorable so that the form follows the idea.
Why it matters: For interface, product, and brand decisions, recognizability is often more valuable than visual richness. Extra detail can narrow interpretation, slow scanning, and make symbols less universal.
- Low-resolution constraints can sharpen design judgment: The original Macintosh graphics were designed in black and white at 16-by-16 or 32-by-32 pixel scales. Kare treated the limited grid as a creative constraint, using simple geometry, metaphors, and iteration to make icons understandable without relying on text. She also designed the Chicago typeface at a very small pixel height and used horizontal, vertical, and 45-degree forms to improve legibility.
Why it matters: Design systems should be evaluated at their actual operating scale and under their real constraints. A concept that works only through detail, color, or explanation may fail in compact, international, or low-attention contexts.
- Universality comes from leaving room for the user: Kare cites the idea that highly detailed faces look like specific people, while simplified faces allow viewers to project themselves onto the image. She applied the same logic to the Happy Mac and other symbols: reducing detail can make a graphic more broadly relatable and easier to interpret.
Why it matters: Products intended for large or diverse audiences should avoid unnecessary specificity when the goal is shared recognition. Abstraction is useful when it preserves the core action or emotional signal.
- Interface symbols need conceptual reinforcement, not just visual neatness: The Command key symbol was selected partly because it was easy to draw in a 16-by-16 grid and resembled a cloverleaf or feature marker. Kare later acknowledged that abstract symbols can be harder to remember when they lack a supporting metaphor, even though this symbol had an independent historical meaning in Swedish signage.
Why it matters: A symbol can be technically elegant and visually distinctive yet still impose a learning cost. Teams should test whether users can infer or retain its meaning, rather than evaluating only consistency and aesthetics.
- Iteration benefits from imperfect starting points: Kare says she often likes to see what a client requests or what a programmer uses as a placeholder because those rough versions can generate useful directions. Her Swatch alarm-clock examples show repeated movement from literal concepts toward simpler or more suggestive forms rather than treating the first idea as a final answer.
Why it matters: Early artifacts are valuable inputs to exploration. Product teams should make alternatives visible, preserve rough experiments, and use comparison to improve concepts instead of waiting for a single polished proposal.
- Small teams and concrete artifacts accelerate decisions: Kare describes working in a compact Macintosh software group, collaborating closely with programmers such as Andy Hertzfeld and Bill Atkinson. She also relays advice to show several options when presenting work to a strong decision-maker, allowing critique while preserving a meaningful choice. Elsewhere she notes that consensus becomes harder as teams grow beyond a size where everyone can remain aligned in one room.
Why it matters: Creative velocity depends on short communication paths and tangible alternatives. As teams expand, decision quality and speed may require clearer ownership, smaller working groups, and more visual decision-making.