Technical tools are secondary to building a successful design system. The primary barrier is a lack of shared vision. Success requires designers to think about engineering constraints and engineers to understand UX intent, creating an empathetic, symbiotic relationship that underpins the entire system.
Related Insights
At Perplexity, the design system lives in the codebase, not Figma. Designers contribute directly to the frontend, creating a single source of truth that eliminates drift between design files and production code, forcing a highly practical and collaborative process.
Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.
The idea that design systems stifle creativity stems from the high cost of re-coding components after a design change. In a world with a single source of truth, where design changes automatically update the code, this cost disappears, allowing systems to be radically changed without engineering overhead.
Instead of siloing roles, encourage engineers to design and designers to code. This cross-functional approach breaks down artificial barriers and helps the entire team think more holistically about the end-to-end user experience, as a real user does not see these internal divisions.
For individuals who both design and code, finishing a visual design isn't a moment of triumph but one of dread, as they know the lengthy process of coding it from scratch has just begun. This specific emotional pain point is a core motivator for building next-generation tools that eliminate this redundant step.
Inspired by architect Christopher Alexander, a designer's role shifts from building the final "house" to creating the "pattern language." This means designing a system of reusable patterns and principles that empowers users to construct their own solutions tailored to their unique needs.
The current model of separate design files and codebases is inefficient. Future tools will enable designers to directly manipulate production code through a visual canvas, eliminating the handoff process and creating a single, shared source of truth for the entire team.
The true power of UX research is aligning the entire product team with a common understanding of the user. This shared language prevents working at cross-purposes and building a disjointed product that users can feel.
AI tools are collapsing the traditional moats around design, engineering, and product. As PMs and engineers gain design capabilities, designers must reciprocate by learning to code and, more importantly, taking on strategic business responsibilities to maintain their value and influence.
Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.
