Won’t it depend on how fast the system’s users wants the ui component to build the feature and the use-cases of it?

Gary has an extensive wardrobe of dresses. They come different colors, outfits, shapes and sizes.

If a DS team haven’t agreed with a user on adopting their upcoming feature, then that feature is likely to be used in the near future. When many such features with broken-promises are released, the system usually ends up with a lot of not-used features.

That’s the bloat.

Design systems are about making sure stickers are given to every people using it.

Can a design system manager also get in the starter park? : )

Component. The sodium and chloride of the salt are the tokens.

Both are kind of the same . I mix stuff to create stuff! : )

It could be then called like a shared metric where the feature teams are also responsible.

Yea. One way to measure it is see how many features are released in a period of time and is that number increasing. It’s not easy to measure because there are many factors in feature development and not just Design and UI.

Updated. Its Delivery hero

Isn’t it something for the product who is adopting the system?

A system can influence and support the adoption but if the system is not adopting itself, why should it have that as metric?

I maybe wrong here.