Design systems live and die by culture, not components
Tokens, components, and documentation are table stakes for any serious design system. But the organizations that successfully scale their systems over years share something less visible: a culture that lets the system take root. Ben Callahan explores this thesis in Maturing Design Systems, forthcoming from Smashing Press, and the excerpt below gets at the heart of why culture is decisive.
Culture is personal before it is organizational
Everyone has an intuition about workplace culture. Most of us can say whether we want to work in a given environment or avoid it. But naming what culture is gets slippery quickly. The difficulty is amplified by the fact that a company rarely has a single culture. It holds many subcultures, because culture emerges when the same group of people assemble repeatedly over time. Teams clustered around goals, products, disciplines, and even Thursday lunch Zoom calls each grow their own micro-culture. That fragmentation is normal—and it matters for design system work because adoption always happens inside those smaller groups.
When culture is off, the symptoms appear in human behavior. One culture gives an individual room to deliver tough feedback to their manager; another pushes that same person toward a job search. A company that offers perks like free food generates gratitude in one culture and a subtle trap in another. Culture either keeps people grounded in shared goals or lets misalignment fester.
Why a systems engagement fell apart
Callahan recounts an engagement from 2021 where his firm was asked to plan, design, and build a design system alongside the MVP of a new product. On paper, the work was ideal. In practice, it became a year-long struggle that ended with his team walking away from the client—not over budgets or technical obstacles, but due to what Callahan labels "cultural incompatibility." It was the first time in nearly two decades of running his business that he had pulled out of a client relationship, and the experience sent him down a year of research into organizational culture.
A working model of culture
Callahan draws on business theorist Edgar Schein, whose model breaks culture into three layers.
Artifacts
The top layer is what most people point to when they describe a culture: the visible perks and symbols. Free donuts, a foosball table, team lunches, company swag, peer-recognition channels in Slack, and the annual retreat all count as artifacts. They are the surface, not the substance.
Espoused values and beliefs
Just below the surface lies what people say they believe: the stated values, mission statement, vision, and everything promised on the website and during interviews. Future employees hear these claims and reasonably expect them to guide day-to-day life.
Basic underlying assumptions
The deepest layer holds what people in the organization actually believe. It is visible in behavior, especially when hard decisions arrive. This is the root of culture. No set of perks or eloquent mission statements can conceal the underlying assumptions for long—eventually they surface, and alignment fails when the top two layers contradict the deepest one.
Strong cultures align the layers
People speak of "strong" and "weak" cultures, and these words track the alignment between Schein’s layers. A strong culture has its artifacts, stated beliefs, and underlying assumptions in sync. Because everyone shares the assumptions, employees can trust one another’s decisions to be consistent with stated values.
A weak culture, by contrast, has lost that organic alignment. Policy documents multiply as a substitute for shared understanding; leadership reacts to bad outcomes rather than formalizing behavior that already works. Policies themselves are not the problem. In a healthy culture, documented expectations codify what has emerged naturally. In a weak one, documentation tries, often unsuccessfully, to prevent the next failure.
Bottom-up culture, not top-down
Employees experience these layers top-down: they see artifacts on day one, hear the espoused beliefs from coworkers, and only later observe how individuals behave under pressure. Unhealthy organizations manufacture culture from the top by adding perks and statements. Healthy ones let the upper layers emerge from the underlying assumptions alive at the grassroots.
The disconnect between stated values and real ones is tangible. It shows up as the "family first" company that demands nonstop travel with no regard for employees’ actual families. People rarely struggle to articulate the mismatch, but they feel it strongly—and that feeling is what eventually sinks a design system initiative that depends on voluntary, sustained adoption across teams.
Maturing systems beyond the excerpt
Callahan’s book continues from this cultural foundation into the anatomy of design systems, the specific stages of maturity, and the habitual pitfalls of each: building version one, growing adoption, managing "the teenage years," and evolving into a stable program that carries real organizational influence.
- Context — where design systems live in an organization, what feeds them, and whether you should build one.
- Design System Culture — a deeper look at culture, why systems teams must understand it, and how it unlocks value delivery.
- The Anatomy of a Design System — the layers and parts of a system, distilled from years of evaluating hundreds of them.
- Maturity — the maturity model, including four stages, origin stories, and frameworks for healthy maturation and stability.
- Stage 1, Building Version One — mental models that keep early-stage work focused.
- Stage 2, Growing Adoption — broadening adoption strategies, understanding the adoption curve, and creating sustainable buy-in.
- Stage 3, Surviving the Teenage Years — handling the nuanced challenges of a maturing system.
- Stage 4, Evolving a Healthy Program — operating as an influential leader once the system carries organizational weight.
Maturing Design Systems is expected soon from Smashing Press. Announcements for order availability come through the Smashing newsletter.
