Design System Crisis: Rigid Rules Lead to Zero Task Completion in Real-World Tests

Update: A major e-commerce company's internal design system, once hailed as a gold standard, has failed spectacularly in a warehouse setting, achieving a 0% task completion rate. The incident at Shopify, where its flagship Polaris system was used on shared Android scanners in dimly lit aisles, underscores a growing crisis in how digital products are built.

“Task completion with standard Polaris: 0%,” a senior design leader who worked on the project stated. “Every design assumption broke down—thick gloves, limited English, harsh lighting. The system was built for perfect laptops, not reality.”

Background

Design systems were promised as the solution to scaling product experiences. Components, tokens, and patterns were meant to accelerate development and ensure visual unity. However, as systems mature, many have become prisons of consistency.

At Booking.com, a similar lesson emerged: A/B testing everything—including button shapes and logo colors—revealed that visual consistency is not the same as solving user problems. “Consistency isn’t ROI; solved problems are,” the design leader explained.

The concept of design dialects was introduced to address this. A design dialect is a systematic adaptation of a core system that preserves grammar but expands vocabulary for specific contexts—like a regional accent of a language.

What This Means

The warehouse failure is a wake-up call. “Rigid adherence to visual rules creates brittle systems that break under contextual pressure,” he added. “Fluent systems bend without breaking.”

In practice, this means teams must stop treating design systems as fixed libraries and start viewing them as living languages. Tokens are phonemes, components are words, patterns are phrases, layouts are sentences. A language with many accents is more resilient, not weaker.

The cost of ignoring dialects is mounting. Teams file hundreds of “exception” requests. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems. The answer is not to abandon systems, but to build in dialect adaptation from the start.

As one expert put it: “The web has accents. So should our design systems.”

Key Takeaways

• Consistency without context is a trap. Focus on solved problems, not visual uniformity.
• Design systems must support dialects—systematic adaptations for specific environments.
• Real-world constraints (e.g., poor hardware, user language barriers) will break any system not designed for flexibility.

The incident at Shopify is not isolated. Across industries, teams are realizing that a one-size-fits-all approach fails the moment it leaves the ideal conditions. The next generation of design systems will be judged not by their pristine beauty, but by how gracefully they adapt to messy reality.