Completely agree! I would love this to be released as a "mode" or "theme" that users opt into, not have to opt out.

It's the Lego Icon Kingfisher set, highly recommended: www.lego.com/en-us/produc...

Yes please do and I'll do the same! I have an old ass car that only plays the radio or CDs so KMHD + XRAY are my go-tos.

Exactly, my manager oversees infrastructure, DX, platform, and other core engineering teams whereas my designer counterparts are under the Head of Design.

Fortunately we have full agency at the team level to dictate our roadmap since historically we prioritize work that fits into the company's larger goals.

We have one shared DS roadmap that we share with the rest of the product org that includes any cross-team initiatives that would require support from feature teams.

We have two designers and two engineers that make up a dedicated Design Systems team. We all sit in our respective orgs and have different managers. We find this helps increase our reach and impact vs being in a silo. Next step is to hire a Product Manager to complete the "3-legged stool".

Wonderful, we are currently in discussions on how to improve our current accessibility annotations. Would love to check it out!

I love Porkbun! Maybe it's time to treat myself to a couple new domains and finally update my handle on here.

Thank you for sharing Dave! That's similar to how we've been operating and agreed, it's a lot of work. Also while hitching a DS initiative to a feature build helps get it prioritized, you can start to lose control over the end result 😅 It makes a lot of sense tho!

Completely agree on being informed and I love the team structure. We're working towards having more advocacy at the feature team level but our small but mighty team spends a lot of time supporting and educating.

I agree, I think the opportunity with experimentation is around testing new variants and validating existing decisions. We've had feature teams create clones of DS components to test but without DS ownership, there may be a lack of follow through and can result in redundant code/increased tech debt.

This is currently our workflow as well: A new component will be created for a feature, it's tested behind an experiment, validated, and then becomes a candidate for the Design System. At that point it's a decision around reusability and scalability.

Oh neat! Our research team conducts user tests so it would be interesting to see if we could incorporate our component testing as part of that. Thanks for sharing!

Cool! I'm a subscriber, I'll definitely check this out.

This is awesome Katie, thank you for sharing!