2 ms·

I have some experience in the space as a developer, and it’s challenging mainly because design systems and component libraries are an abstraction, and frankly,

by gedy 3y ago

I have some experience in the space as a developer, and it’s challenging mainly because design systems and component libraries are an abstraction, and frankly, most people aren’t great at generalizing. Designers especially are rarely ever taught how to think reusable patterns and components, but they are frequently the ones “put in charge of“ this type of work. It's closely related to this quote: > A lack of ... alignment within teams and leadership around what a design system is, what problems it solves, and how it will provide value. I like working with UX and designers, but more often than not, "we need a new design system" basically means "we want a cool, new theme"

qkeast 3y ago
Yep! This often happens when design systems are thought of in narrow terms of design tooling—component libraries and such in apps like Figma, without a connection to the implementation. Edit—Responding to an edit in the OP: >I like working with UX and designers, but more often than not, "we need a new design system" basically means "we want a cool, new theme" This isn't so much an issue with UX and designers as a discipline, but rather points at larger issues in the organization around process, culture, expectations, and strategy, the perceived role of design in that organizational context, and the specific folks you've worked with.