3 ms·
Design Systems are much like Frameworks you can either formalize and document the process or not but all this type of information has to live somewhere and be c
by mikeryan 7y ago
Design Systems are much like Frameworks you can either formalize and document the process or not but all this type of information has to live somewhere and be communicated.
The hard part here is that now with the rise of alternative tooling like Sketch, Zeplin, Figma and technologies like styled components, SASS, post css etc - there's a pretty broad range of ways to pull all this together so some of the implementation is going to be organization specific.
In general though we've found that developing design systems can greatly increase our throughput on new initiatives without having to reinvent the wheel on a lot of basics. There's some overhead but at least it makes for a transparent way to manage communication of a design.
Of note there's a great site https://designsystemsrepo.com/ https://designsystemsrepo.com/ that is a repo of a bunch of design systems. Great place to peruse.
- tenaciousDaniel 7y agoWhen I look at design systems, it definitely seems like a good idea. But then when I take a step back and ask myself "what problem are we trying to solve?" my answer is: we need to communicate the intent, behavior, and visual attributes of an application to (a) stakeholders for approval, and (b) developers for implementation. This communication is expected to update over time and potentially to several teams, though not all teams at once since they need to update their own designs in response. When I think about ^THAT problem, I ask myself "is what I'm seeing in a design system the thing that Once And For All solves that problem?", the answer is no. There's something that doesn't feel sustainable to me.