Modular Systems: Scaling Design Without Drift

A design system is a promise your team keeps, not a folder of components. This session looks at the operating model behind the parts: how you name, version, and retire tokens and components without losing the trust of the people who consume them.

We open with a live taxonomy exercise. Using real pattern libraries, we will sort components into primitives, composites, and page-level blocks, then debate where the line between “reusable” and “just a component” actually sits. From there we move to versioning and deprecation — the unglamorous work that decides whether a system ages gracefully or rots quietly.

The session closes with governance patterns you can adopt on Monday: decision logs, ownership rituals, and a release cadence that keeps the system boring and dependable, the way Swiss infrastructure should be.

Key Takeaways

• A naming and taxonomy model for components and tokens
• Versioning and deprecation workflows that don’t stall teams
• Governance rituals — decision logs, ownership, and release cadence
• How to measure drift before it becomes a refactor