BigDesign

BigDesign is BigCommerce's design language. Its structural flaw was one of ownership: it was maintained by an individual contributor with no authority over the code that implemented it. Every change to the system required waiting in another team's queue. A system that cannot change at the pace its consumers need is a system they cannot depend on.

Bypassed because compliance was slower

Teams worked around the system because reaching for it cost more than rebuilding locally: components lagged, ownership was ambiguous, and updates waited elsewhere. When the compliant path is the slower path, adoption erodes regardless of advocacy.

Ownership with authority over the code

The remedy was structural: found the Platform Design team and give the system an owner with direct authority over its implementation: the Figma component library, the developer playground, the pattern library and sandbox, UX-writing tooling, the Catalyst storefront, and the documentation binding them together. The system could now change at the pace product teams required.

A service, not a gate

The team was built to accelerate delivery, not to police it. Success was measured by teams choosing the system because it was the fastest route to a quality result, consistency as a by-product of good tooling rather than enforcement.