Design systems that survive the move into production

A design system often looks most complete just before it meets real content. Production introduces long names, permissions, loading states, browser constraints and campaign exceptions. Durability comes from designing how the system reasons, not only how its components look.

Encode intent

Tokens should describe roles—surface, emphasis, success, danger—not isolated colours. Components should explain hierarchy, states and content constraints. That lets future teams extend the system without imitating screenshots.

• Test components with real and adversarial content.
• Define empty, loading, error and permission states.
• Review implementation at working breakpoints, not only static handoff.
• Treat documentation as a decision record, not a museum.

A system survives when the next designer and engineer can make a new decision that still feels inevitable.

The handoff is therefore not a moment. It is a sequence of shared reviews in which design and engineering own the final experience together.