This question is all over the internet, and there are maybe hundreds of definitions. Mentioning a few:
Well, you’ve got the idea probably. There is a lot of definitions of what design system is (and what it isn’t).
However, I found a new “definition” this week, which I like a lot. I have a small talk in Bratislava next week where I plan to use this one:
This definition is from the short talk by Nathan Curtis about a complexity of buttons, team structures, and importance of good craftsmanship.
One small confession here – whenever I work on some presentation where I need to include one slide with the explanation of what design system is, I just pick one that serves the best the goal and audience of my presentation.
I like having our local UX community on Slack, there is one issue though – as UXCZ Slack isn't paid, a lot of interesting resources gets lost. The topic mentioned in the headline was discussed last week, and I decided to put some interesting links also here, for future references:
What surprised me last week was that several people reacted positively to my side project principles. If you missed my last weeknotes, check them there.
After that definition, I made a list of all my side projects and activities, and I questioned them with defined principles. I am happy to announce that Czech Design Systems Meetups survived strong. However, a lot of other projects didn’t – Design Systems Jobs repository included. It was a pleasant experience, and it gave me an excellent overview of what is happening in the job field, but it just wasn’t giving me back what I expected.
The new projects await though. And I am very much looking into the 4-day course on Machine Learning for Creatives that I signed up for.
And to smoothly follow up on machine learning topic, I want to share one great talk I saw last week. It's called "A.I. is your New Design Material", it's from Josh Clark and besides it's pretty inspirational and very much on point, plus it has a lot of great examples inside from product we daily use.
"For the last decade, a lot of the focus was on mobile. There is a shift now to what can we do with data and machine learning." – Josh Clark
A small tip: watch it till the end, the discussion after the talk is also great.
Some of my notes from this talk:
Tools & libraries to explore closer:
Questions to ask myself occasionally:
There is also one more thing why I find this talk important. Josh mentions "Sprinkle a little machine learning on it," or "It doesn't need to be a big deal, it can be part of everyday things we design.".
To me, this is basically why I believe that if we're building products, we should know the principles and basics of machine learning and algorithms. Because if we know them, we are open to the world of a lot of new (and can design for) possibilities.
If you read through all to the end of these weeknotes, you may be interested in my new feature on this blog. I added a sign-up form for my new articles, so if you subscribe, you’ll receive a notification to your e-mail when I publish something.