Exploring Design Systems

Adilah Anuar
Aug 25, 2017 · 1 min read

When I used to work for a smaller company, my team leader/developer had ever introduced to me this idea of *Design Systems*. Back then I thought it was a cool idea but I never did anything about it. Partly because we got busy with other projects and I thought since I was the main and more often the only designer in our small team, we don’t really need it.

Fast forward to 2017, and here I am reading up about it now and realizing how truly useful and beneficial it would be.

Thankfully I found this article written by Wen Wang as a great brief introduction. And since I have experience doing front-end, I thought it would be a good idea to put what I’ve learnt into practice.

However, I don’t see my current team implementing this anytime soon. Perhaps we do, but from my understanding there is no official comprehensive guideline that we truly follow. So most probably I would attempt it on a smaller scale as a side project to know how it feels creating one.

Then when the time comes perhaps I could suggest it to the team and convince them to make it part of our workflow. :)

)
Adilah Anuar

Written by

A designer who designs + codes | Currently documenting on Medium as I self-learn UX and UI/Product design + other creative pursuits

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade