• Simone Simone , over 1 year ago

    Let me expand of this.

    "Do you feel the need to create one?"

    · Designing systematically is a good habit of any mature designer. So yes, you'd want to be doing that. That being said, its the propagation behind designing systematically that turns those rules into a formal "design system" as most of us know it. The degree of rules and documentation that you need is highly variable depending on the work you do and how you intend to divulge this information internally (e.g. Zeplin's style guide covers color and type quite well on its own right)

    "Where do you start from?"

    · You'll start from content. Whatever is the most important piece of data your work revolves around, you'll start by designing it and defining rules around that. Then you'll try those rules against other components. If they work great, if not: can you find a single value which works in all (or most) cases? · Once you've gone through this exercise, you'll realized that there's only a limited sets of values that works (note how many design systems are based off a 4px grid? Well, that's not a coincidence!)

    "But they take a long time?"

    · Also this is fairly relative. If you're planning to do a lot of documentation, a living style guide, then yes - that can be a lot of work. If you're planning to have a system driven by your work files, then you're just investing some set up time in favor of facilitating future work.

    The bottom line: you probably don't need a public facing design system (e.g. Salesforce Lightning, Material, etc), but you want your design team and eng to all agree on the basic design rules across your designs (type ramp, , colors, grid and layouts, spacing system). That'll shorten the handoff and QA time and make your life overall much more enjoyable :)

    1 point