Related Posts
Additional Posts in Designers
anyone know who created Palantir's website?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
anyone know who created Palantir's website?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site
Send download link to your phone
OR
Scan your QR code to download
Fishbowl app on your mobile
Mentor
Design systems should help designers, especially when it comes to oft repeated patterns ("why do I need to design a confirmation dialog... again!?"). If the needs of the user and the needs of the design are not covered by the design system designers should be allowed to put aside or expand the system as needed. They should confirm a change is needed, but never feel constrained.
I worked at one company whose design system was mandated with an iron fist, even though it was incomplete, had poor usability (IMHO), had poor functionality, and only really worked for a fairly narrow range of use cases. Changes to the system required months of approval and POC before they'd be accepted. The entire design team chafed under this mandate. DO NOT DO THIS!
Mentor
I think you have the right attitude.
Design systems should be flexible and grow with the product over time. They should (at least initially) focus on the frequently used components and grow from there. Every designer on the team can be a contributor this way they aren’t feeling confined because they know they too can add to the system.
The files are open to all designers but there are discrete sections for components that are both “in spec” and “for consideration”.
There is a “council” for lack of a better word that reviews suggestions as frequently as they are made. The ultimate goal is to have folks dedicated to the job of design systems in the long term to maintain and review suggestions so that they remain on spec.