My first deadly sin of startup design systems?
Comparing my system to giants like Material Design, IBM Carbon, and Adobe Spectrum and expecting the same level of detail.
Their DS teams are bigger than my whole company!
Great resources, but terrible comparisons.
@itspatmorgan
Comparisons are generally terrible to begin with.
You’re making something for your orgaization’s and product’s needs; so unless you’re making the exact same thing as them in exactly the same way, it’s going to be unique.
Other systems are good for learning, but foolish to copy
@itspatmorgan
Comparison is the thief of joy.
I’ve been digging deep into different startup design systems from some customers and: 1) I’m genuinely impressed they’re actually working this way (still not as common as we may believe); 2) just a little standardization would, in my opinion, go a…
@_allen_smith
Yep, startup design systems need to be much more pragmatic. In large part, they should be curating the best elements of major systems, remixing them slightly, and combining them with whatever limited custom stuff they need for their scenario.
@itspatmorgan
Very true. Our Design System was based on Material Design so we benefited greatly from Google’s efforts and large team. But even they made mistakes (emphasizing the FAB and burger menus for desktop apps in the early days). We still needed to define our unique needs.
@amproehl
100%. For me, it was about curating the specific subset of elements from a mega-system like Material that would help my scenario, remixing them slightly, and supplementing with custom stuff needed for our unique environment.
@itspatmorgan
I’m preparing an article where I talk about the size of DS and I included a similar point as a disclaimer. Comparing and expecting the same results as a team of 40 members with only 5 can really hurt the team and its goals.
A roadmap can help managing these expectations.