Chuck Rice

Some great insights here, thank for writing—my main takeaway is that sharing and informing the team how well adopted the design system is, and the direction to head is a powerfully motivating tool.

On the one hand a suite of products and teams of varying codebase quality can be challenging to assess, but you could use it to pit teams against each other. Imagine awards for "biggest improvement" or a leaderboard of token adoption!

Love the "orphan explorer"—I haven't used it myself, but I've seen Figma's organisation plan gives you metrics where designers have "detached instance" and how often. That can be helpful for assessing (non) adoption on the design side, and where to probe.

Another great article I can recommend for readers: where you might place your efforts, changes depending which stage of "design system maturity" you're at: https://medium.com/design-systems-for-figma/creating-components-for-mature-design-systems-f31ecc85627a

--

--

Great lessons on building Design Systems, thanks for sharing! My favourite is the "relying too heavily on a third-party plugin". When making engineering decisions the best leaders choose projects that are well supported and updated routinely for this very reason. Choosing a poorly maintained project, or in our case a poorly maintained plugin, can spell disaster and headache unfortunately.

--

--

I’m delighted you want to submit to North West UX!

The process

  1. Make sure you have a draft, or published piece, on Medium
  2. Send a link to chuck@chuckwired.com
  3. I’ll review as soon as I can, and accept it if it’s all good!

Afterwards I’ll add you as an Author to the publication, so you can “Add to publication” directly from your Medium editor.

Hope to see your recaps soon!

—Chuck

--

--

Chuck Rice

Chuck Rice

Lead UX Designer @residently. Community Advocate @figma. Certified Design Sprint facilitator. https://chuckwired.com