I love that this title directly goes against the Figma post from 23 days ago.
I commented in that thread:
I think it's interesting that you understand design systems to be something that automates a designers job. I've felt lately that a design system is something that helps a design team focus on more important things. If we have a system that makes the UI component of our job faster, and more efficient, we can focus on a lot more than just skinning new UI.
Imagine smaller teams being able to focus on truly testing usability, prototyping crazy new ideas and creating new functionality that they just didn't have time to conceive in the past because they were too busy pushing pixels.
I think Design Systems will help designers have much more impact on business, and when that happens, designers could become even more of an asset.
I was happy to see your article - and I agree with what you've written.
Thank you Rhys, this is really great to hear!
I've always saw design systems as a way to create consistency and limit the amount of duplicate work that needs to be done. The part of my life it makes easier is the part where I think "OK, this screen is going to need form fields and buttons." A design system doesn't magically throw it together in the exact order it should be laid out.
I don't exactly understand the notion that design systems will completely automate design.
I think you are completely right! One of the main roles of a design system is to allow designers to focus on the user experience and the visual composition of an interface without stressing out on consistency details. :)
I believe the title of this article was just to look at both sides of the an argument. Equally they have one that says "No, design systems will not replace design jobs".
I like this article.
The designer job is here to stay. Although design systems make a designer’s job much more efficient, they cannot be put in the pilot’s seat when it comes to creating an authentic design process.
Yep. And, efficiency gains are easily spent on higher expectations.
To think design systems will replace our jobs is just silly in the first place.
Design Systems do, and will replace design jobs not through automation but through efficiency.
I'm not too sure why this is a point of contention. A good design system decreases the number of designers required to design, maintain or scale a product.
As a result, if your design team went from 10 - 5 then your design system replaced 5 jobs. This is the point.
In fact, if you design a system that doesn't replace design jobs, then you haven't really designed a very good system in the first place.
If you can be replaced by a design system - you're not offering much value to a design team to begin with.
Well unfortunately I think that can be the case, but it's not a reflection of the designer but rather the company you're working for (sometimes).
The designer job is here to stay. Although design systems make a designer’s job much more efficient
You said it yourself. Efficiency = less people are needed to achieve the same results.
While in the past a 'UI Designer' was needed to make wireframes come to life and look good, today a UI designer without product thinking skills is not a very important asset inside a team that uses a design system. New opportunities were opened as well - Illustrators, 3d artists are in a higher demand, and i believe there are more jobs for most types of designers and thinkers.
I love your Website. Really slick! :-)
Thank you, Etienne! I'm really glad you like it!
Silly, non-premise to argue in the first place.
Pretty much this. Completely made up issues so people can drive traffic to their company blogs.
Design systems realize their benefit for teams over a certain scale (lets say 5-6+ full time designers). At that point maintaining a design system across an organization IS a full-time job. Smaller teams don't usually have the time to focus on a system they aren't going to get that much value out of.
I'd be truly surprised if this is becomes a common problem in the industry.
I remember when we used to call them "style guides".
People forget that to get a system running, you need people to first build it, and then continuing maintaining it. If anything, it creates more work rather than less, at least this holds true for bigger organisation.
Tackling changes and updates from multiple teams, along with communication, documentation, and releases, heck it's a teams worth of work on it's own. Smaller teams can afford to skip some steps, but the true worth is about efficiency, so designers can focus on other parts that attention is sorely needed. At some point, you'll have to split you attention and get back into greasing the system's gear.
Lol, Obviously. It will never replace design jobs. Design system is to help the designer to speed up work and as Marc Edwards mentioned a term 'efficiency' :)