Why design systems fail to resolve disagreements

How design lost the ability to evaluate work

We built design systems to bring order, yet we spend more time arguing over button variants than ever before.

Every design lead knows the feeling: a meeting about a single button variant that drags on for an hour because “it just doesn’t feel right.” We have the components, the tokens, and the documentation — but we’ve lost the one thing that actually makes them work.

In 1983, Massimo Vignelli — fresh from receiving the AIGA Gold Medal and at the peak of his professional authority — published a warning in the Graphis Annual that now reads like prophecy. Design, he argued, was about to lose something essential.

Non-members can read this full story for free **via this link. If you enjoy this article, consider [becoming a Medium member for just $5 a month](https://medium.com/membership)** to support writers directly — or follow for more stories like this.

Not a tool. Not a technique. Something more fundamental: the capacity to distinguish good work from bad work with reasons that transcend personal preference.

Vignelli called for criticism. Not cruelty. Not gatekeeping. Criticism as rigorous evaluation: the ability to say this works because… and this fails because… in ways others could follow, test, and debate.

His claim was not that standards should be stricter, but that without criticism, standards cannot exist at all. And without standards, a field cannot accumulate knowledge. It can only produce work.

That warning was ignored — not because it was wrong, but because the conditions required to process it were already dissolving.

What changed in the early 1980s

To understand why Vignelli’s warning failed to land, we need to understand what was happening around him.

In December 1980, the Memphis Group was formed at a meeting in Ettore Sottsass’s Milan apartment. Nine months later, on September 18, 1981, Memphis detonated onto the design world at the Arc ’74 gallery during Milan’s Furniture Fair.² Led by Sottsass, Memphis positioned itself in explicit opposition to modernist design.

1980s design movement started in 1981 by Ettore Sottsass and a group of young designers who wanted to challenge the established notions of good design at the time. By Zanone — Own work. CC BY-SA 3.0

Where modernism emphasized form follows function, Memphis elevated appearance, symbolism, and emotional provocation. Where modernism sought universal principles, Memphis celebrated total rule-breaking. Where modernism treated design as a systematic problem-solving discipline, Memphis framed it as expressive communication.

This was not merely an aesthetic disagreement. It was an epistemological one: a rejection of the idea that design could — or should — be evaluated against shared principles.

But Memphis was not alone.

Around the same moment, postmodern architecture was undergoing a similar shift. Michael Graves reintroduced classical forms not as systems governed by proportional logic, but as visual quotations — symbols detached from the evaluative frameworks that once structured them.³ Robert A. M. Stern institutionalized pluralism, arguing for contextual “appropriateness” without providing criteria that could be tested across cases.⁴

*These movements differed stylistically, but they shared a premise: *That shared evaluative frameworks were either impossible or undesirable.**

Standards were reframed as constraints on creativity. Judgment was reframed as exclusion. Rule-breaking became not a method for discovering better rules, but a terminal position.

By the time Vignelli wrote his essay in 1983, this premise had already won cultural legitimacy.

Why evaluation became impossible

Once you accept the idea that standards constrain rather than enable — that evaluation itself is a form of gatekeeping — Vignelli’s call for criticism becomes structurally incoherent.

Not wrong. Unprocessable.

How do you evaluate work when applying standards is the very thing being challenged? What criteria can be used when criteria themselves are treated as ideological artifacts?

The result was not chaos, but something subtler: structural indeterminacy.

Without shared evaluative frameworks:

• Principles cannot compound
• Knowledge cannot transfer
• Expertise cannot be distinguished from preference
• Disagreement has no resolution mechanism beyond time or power

This was not a failure of individuals to argue well. It was a failure of the system to permit argument at all.

When knowledge lost its inheritance

When a field loses the ability to evaluate work, it simultaneously loses the ability to transmit knowledge.

A Vignelli-style system sheet with structurally meaningless feedback.

“Inheritable” work is not work that was popular or admired. It is work whose logic can be passed forward intact — principles that others can test, apply, refine, or reject with reasons.

Memphis dominated the 1980s. Its influence was enormous. And yet within a generation, it became professionally illegible.

Most practitioners today cannot:

• Name multiple Memphis designers beyond Sottsass
• Articulate what principles Memphis stood for, rather than what it rejected
• Explain which aspects of its approach succeeded, which failed, and why

This is not because Memphis lacked sophistication. It is because its epistemological premise made its principles non-extractable.

And here’s the crucial point: the same thing happened to Vignelli.

Vignelli articulated systematic principles — semantic clarity, syntactic consistency, pragmatic usability — that could have been taught, tested, and extended. But once evaluation itself lost legitimacy, systematic thinking became indistinguishable from personal taste expressed with confidence.

Both positions became professionally uninheritable — not as a value judgment, but as a structural outcome.

The inheritance problem in design systems

Here’s a diagnostic question for design systems practitioners:

Who are your professional ancestors?

Not whose work you admire — but whose principles guide your judgment. Whose reasoning you study. Whose positions do you test your own ideas against?

In software engineering, practitioners can reference Alan Kay, Fred Brooks, or Rich Hickey — not as heroes, but as sources of transferable reasoning. Architects inherit pattern languages, formal principles, and explicit debates.

Design systems work rarely has this.

Instead, every team starts from zero. Every decision is renegotiated. Every pattern is provisional. Not because people are careless, but because there is no inherited framework that establishes what would count as better or worse.

This is why meetings never end.

A concrete example of criticism

To make this tangible, here is the kind of criticism Vignelli was calling for — and the kind that has largely disappeared.

A critique grounded in history and theory

Consider a transit map — precisely the kind of problem Vignelli worked on.

Photo by Etienne Girardet on Unsplash

A Vignelli-style critique would sound like this:

This map prioritizes geographic fidelity over navigational clarity. Riders do not need to know the exact curvature of the river; they need to understand sequence, transfer points, and relative direction. By enforcing consistent angles and spacing, the system reduces cognitive load, improves scanability under stress, and allows the logic of the network to be grasped at a glance. The cost is local accuracy, but the benefit is global intelligibility — which is the primary function of a transit diagram.

Notice what makes this criticism operative:

• A clear definition of purpose (navigation under cognitive load)
• An explicit tradeoff (geographic accuracy vs. intelligibility)
• Principles drawn from precedent (diagrammatic abstraction)
• A claim that can be tested against use cases

You can disagree with this critique. But to do so, you must argue with counter-principles: that spatial accuracy improves trust, that riders rely on landmarks, that the cost to intelligibility is overstated. The disagreement advances understanding.

A critique without evaluation

Now contrast that with a critique common today:

This feels a bit rigid and overly constrained. It doesn’t really reflect the character of the city, and some users might find it alienating. We should explore something more expressive and inclusive.

This sounds thoughtful — but it cannot be built upon.

There is no stated purpose. No articulated tradeoff. No principle to test. No way to determine what would count as better or worse. An agreement ends the conversation; a disagreement escalates it into a negotiation or a power struggle.

This is not criticism. It is affective response dressed as evaluation.

Why this matters

The first critique produces inheritable knowledge. You can teach it. Apply it to other systems. Refine it when it fails. The second produces only local consensus.

This is what Vignelli meant by criticism as creative interpretation: examination that reveals the logic behind decisions so future practitioners can extend or contest them.

When this kind of criticism disappears, work does not just lose rigor — it loses memory.

What Monday morning looks like…

This all becomes concrete the moment someone asks for seventeen button variants.

A component variant table with no evaluative justification. Decisions are recorded, but not explained — leaving disagreement unresolved and complexity free to accumulate.

You know it fragments the system. You know it increases maintenance cost. But without evaluative principles, the conversation has no resolution mechanism.

• Appeal to concern: “This might be hard to maintain.”
• Appeal to counter-concern: “Our users need flexibility.”

Both positions are legitimate. Neither can be evaluated. Time expands. Power decides.

Now compare that to an evaluable position:

A design system exists to constrain variability in service of coherence. Variants are justified when standardization reduces overall complexity across teams, not when they localize convenience. Project-specific variation transfers cost from one team to the entire organization.

That position can be tested. Challenged. Refined. Or rejected with a counter-framework.

Disagreement becomes dialectic instead of negotiation.

What evaluation enables

When evaluative frameworks exist:

• Expertise becomes legible
• Judgment can be taught and developed
• Disagreement becomes productive
• Knowledge compounds instead of resetting

Criticism, in Vignelli’s sense, is not destructive. It is generative. It exposes the limits of principles so better ones can emerge.⁵ That is how professions mature.

What went wrong

Postmodernism’s critique of modernism was not wrong. Modernist standards did become rigid. They did exclude. They did need revision.

But the fatal error was rejecting the existence of standards rather than defending better ones.

When standards fail, the answer is not liberation from evaluation — it is improved evaluation.

Design systems will not mature through comfort, consensus, or facilitation alone. They mature through defensible positions, tested principles, and criticism that makes knowledge transmissible.

Start here

The next time someone challenges your design system decision, don’t defend the artifact — articulate the principle.

Say what would have to be true for you to be wrong.

Invite someone to test it.

That is criticism.

That is how professional memory returns.

That is what Vignelli was asking for forty years ago.

It’s time we listened.

Sources & references

1. Massimo Vignelli, “Call For Criticism,” Graphis Annual 83/84, edited by Walter Herdeg (Zurich: Graphis Press Corp., 1983). Available at: https://archive.org/details/graphisannual8380000walt
2. Memphis Milano, “History,” Memphis Milano official website, accessed January 2026, https://memphis.it/en/history/. The Memphis Group was formed on December 11, 1980, at Ettore Sottsass’s apartment in Milan, with its first public exhibition opening September 18, 1981.
3. Michael Graves’s Portland Building (1982) is widely considered the first major built example of postmodern architecture in a tall office building. See: Paul Goldberger, “Architecture View,” The New York Times; and “Michael Graves,” Wikipedia, accessed January 2026, https://en.wikipedia.org/wiki/Michael_Graves. Graves’s postmodern work was characterized by “Cubist interpretations of classical elements” used as symbolic quotation rather than systematic application of proportional logic.
4. Robert A.M. Stern, quoted in “What is Postmodernism?” Architect Michael Graves: A Grand Tour, WTTW, accessed January 2026, https://www.wttw.com/main.taf?p=88,5: “Gray buildings have facades which tell stories. These facades are not the diaphanous veil of orthodox Modern architecture.”
5. This conception of criticism as generative aligns with Karl Popper’s falsificationist framework: evaluation doesn’t destroy knowledge but refines it through systematic testing. See: Karl Popper, The Logic of Scientific Discovery (London: Routledge, 1959); and Karl Popper, Realism and the Aim of Science (London: Routledge, 1983). As Popper argued, “A theory is falsifiable if the class of its potential falsifiers is not empty” — a principle that applies to design evaluation as much as scientific method.

A Note on Terminology: Vignelli uses “criticism” to mean evaluative interpretation — judgment that reveals principles, not just applies them. This is broader than academic “critique” (systematic analysis using established frameworks) and more rigorous than casual “criticism” (thumbs up/down). He’s calling for a practice that generates standards through “creative interpretation,” not just defends existing ones. The article follows his usage.