When Design Systems Fail: Lessons from Architecture, Industry, and UI

Design systems have become the go‑to solution for UI designers seeking to streamline workflows, reuse components, and ensure visual consistency across products and teams. While they promise speed, cost‑effectiveness, and a unified design language, the article questions whether such systems are universally beneficial.

Historical examples show that systematic design is not new: Henry Dreyfuss created a manual based on average male body dimensions; Le Corbusier developed the Modulor system using human proportions; Karl Gerstner described mathematical visual design systems; and Henry Ford’s assembly line demonstrated the power of standardization.

These precedents reveal both advantages—low‑risk, high‑efficiency production—and drawbacks, such as neglecting individual needs, fostering homogenization, and creating environments that can become oppressive when the system is treated as immutable.

Modern urban planning projects, like Le Corbusier’s “Radiant City” and the Swedish “Million Programme,” illustrate how rationalist, component‑based approaches can lead to social and economic segregation, monotony, and reduced livability.

In transportation, the Braess paradox shows that adding capacity (more roads) can worsen congestion, highlighting the danger of solving problems solely within the system’s framework without considering human behavior.

The article argues that design systems, like any system, can only explain known variables and may fail when faced with novel challenges. Over‑reliance on them can stifle innovation, obscure broader systemic thinking, and reduce users to quantifiable variables.

Ultimately, the author does not dismiss design systems outright but calls for continuous critical reflection, reminding designers that users are living individuals with diverse needs, and that the best design system might be no system at all.